[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20191118105008.02140761@jacob-builder>
Date: Mon, 18 Nov 2019 10:50:08 -0800
From: Jacob Pan <jacob.jun.pan@...ux.intel.com>
To: Lu Baolu <baolu.lu@...ux.intel.com>
Cc: iommu@...ts.linux-foundation.org,
LKML <linux-kernel@...r.kernel.org>,
Joerg Roedel <joro@...tes.org>,
David Woodhouse <dwmw2@...radead.org>,
"Tian, Kevin" <kevin.tian@...el.com>,
Raj Ashok <ashok.raj@...el.com>, Yi Liu <yi.l.liu@...el.com>,
Eric Auger <eric.auger@...hat.com>,
jacob.jun.pan@...ux.intel.com
Subject: Re: [PATCH 07/10] iommu/vt-d: Replace Intel specific PASID
allocator with IOASID
On Mon, 18 Nov 2019 09:43:00 +0800
Lu Baolu <baolu.lu@...ux.intel.com> wrote:
> Hi,
>
> On 11/16/19 7:09 AM, Jacob Pan wrote:
> > Make use of generic IOASID code to manage PASID allocation,
> > free, and lookup. Replace Intel specific code.
> > IOASID allocator is inclusive for both start and end of the
> > allocation range. The current code is based on IDR, which is
> > exclusive for the end of the allocation range. This patch fixes the
> > off-by-one error in intel_svm_bind_mm, where pasid_max - 1 is used
> > for the end of allocation range.
> >
> > Signed-off-by: Jacob Pan <jacob.jun.pan@...ux.intel.com>
> > Reviewed-by: Lu Baolu <baolu.lu@...ux.intel.com>
>
> Two nit comments in line. With that fixed,
>
> Acked-by: Lu Baolu <baolu.lu@...ux.intel.com>
>
Thanks, will fix below.
> Best regards,
> baolu
>
> [...]
>
> Nit - short line within 80 characters and align the new line with
> open parenthesis.
>
> [...]
>
> Nit - open parenthesis alignment.
>
> [...]
[Jacob Pan]
Powered by blists - more mailing lists