[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20191120151946.2a94c1ee@jacob-builder>
Date: Wed, 20 Nov 2019 15:19:46 -0800
From: Jacob Pan <jacob.jun.pan@...ux.intel.com>
To: Auger Eric <eric.auger@...hat.com>
Cc: iommu@...ts.linux-foundation.org,
LKML <linux-kernel@...r.kernel.org>,
Joerg Roedel <joro@...tes.org>,
Lu Baolu <baolu.lu@...ux.intel.com>,
David Woodhouse <dwmw2@...radead.org>,
"Tian, Kevin" <kevin.tian@...el.com>,
Raj Ashok <ashok.raj@...el.com>, Yi Liu <yi.l.liu@...el.com>,
"Mehta, Sohil" <sohil.mehta@...el.com>,
jacob.jun.pan@...ux.intel.com
Subject: Re: [PATCH v3 6/8] iommu/vt-d: Replace Intel specific PASID
allocator with IOASID
On Wed, 20 Nov 2019 22:06:24 +0100
Auger Eric <eric.auger@...hat.com> wrote:
> Hi Jacob,
>
> On 11/19/19 6:56 PM, 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.
> no more as this is handled in 5/8
oops, forgot that. will remove this comment.
Thanks!
> [...]
> Besides
> Reviewed-by: Eric Auger <eric.auger@...hat.com>
>
> Thanks
>
> Eric
>
[Jacob Pan]
Powered by blists - more mailing lists