From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: Auger Eric <eric.auger@redhat.com>
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
Raj Ashok <ashok.raj@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
iommu@lists.linux-foundation.org,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH v3 6/8] iommu/vt-d: Replace Intel specific PASID allocator with IOASID
Date: Wed, 20 Nov 2019 15:19:46 -0800 [thread overview]
Message-ID: <20191120151946.2a94c1ee@jacob-builder> (raw)
In-Reply-To: <5ead3e84-d6b6-8f97-c83b-236bbe53be86@redhat.com>
On Wed, 20 Nov 2019 22:06:24 +0100
Auger Eric <eric.auger@redhat.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@redhat.com>
>
> Thanks
>
> Eric
>
[Jacob Pan]
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2019-11-20 23:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1574186193-30457-1-git-send-email-jacob.jun.pan@linux.intel.com>
[not found] ` <1574186193-30457-2-git-send-email-jacob.jun.pan@linux.intel.com>
2019-11-20 20:59 ` [PATCH v3 1/8] iommu/vt-d: Fix CPU and IOMMU SVM feature matching checks Auger Eric
[not found] ` <1574186193-30457-4-git-send-email-jacob.jun.pan@linux.intel.com>
2019-11-20 20:59 ` [PATCH v3 3/8] iommu/vt-d: Reject SVM bind for failed capability check Auger Eric
[not found] ` <1574186193-30457-5-git-send-email-jacob.jun.pan@linux.intel.com>
2019-11-20 21:01 ` [PATCH v3 4/8] iommu/vt-d: Avoid duplicated code for PASID setup Auger Eric
[not found] ` <1574186193-30457-6-git-send-email-jacob.jun.pan@linux.intel.com>
2019-11-20 21:02 ` [PATCH v3 5/8] iommu/vt-d: Fix off-by-one in PASID allocation Auger Eric
[not found] ` <1574186193-30457-7-git-send-email-jacob.jun.pan@linux.intel.com>
2019-11-20 21:06 ` [PATCH v3 6/8] iommu/vt-d: Replace Intel specific PASID allocator with IOASID Auger Eric
2019-11-20 23:19 ` Jacob Pan [this message]
[not found] ` <1574186193-30457-8-git-send-email-jacob.jun.pan@linux.intel.com>
2019-11-20 21:07 ` [PATCH v3 7/8] iommu/vt-d: Avoid sending invalid page response Auger Eric
[not found] ` <1574186193-30457-3-git-send-email-jacob.jun.pan@linux.intel.com>
2019-11-20 21:08 ` [PATCH v3 2/8] iommu/vt-d: Match CPU and IOMMU paging mode Auger Eric
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191120151946.2a94c1ee@jacob-builder \
--to=jacob.jun.pan@linux.intel.com \
--cc=ashok.raj@intel.com \
--cc=dwmw2@infradead.org \
--cc=eric.auger@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox