From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
Lu Baolu <baolu.lu@linux.intel.com>,
Joerg Roedel <joro@8bytes.org>,
David Woodhouse <dwmw2@infradead.org>,
"Raj, Ashok" <ashok.raj@intel.com>,
"Liu, Yi L" <yi.l.liu@intel.com>,
"Ghorai, Sukumar" <sukumar.ghorai@intel.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
"Kumar, Sanjay K" <sanjay.k.kumar@intel.com>,
jacob.jun.pan@linux.intel.com
Subject: Re: [PATCH v2] iommu/vt-d: Avoid superfluous IOTLB tracking in lazy mode
Date: Thu, 9 Feb 2023 09:43:30 -0800 [thread overview]
Message-ID: <20230209094330.12a94139@jacob-builder> (raw)
In-Reply-To: <BN9PR11MB5276A911FAAE4C2F6B670E638CD99@BN9PR11MB5276.namprd11.prod.outlook.com>
Hi Kevin,
On Thu, 9 Feb 2023 02:09:47 +0000, "Tian, Kevin" <kevin.tian@intel.com>
wrote:
> > From: Jacob Pan <jacob.jun.pan@linux.intel.com>
> > Sent: Thursday, February 9, 2023 2:19 AM
> >
> > - iommu_iotlb_gather_add_page(domain, gather, iova, size);
> > + /*
> > + * We do not use page-selective IOTLB invalidation in flush
> > queue,
> > + * There is no need to track page and sync iotlb.
> > Domain-selective or
>
> "in flush queue, so there is ..."
>
> > + * PASID-selective validation are used in the flush queue.
>
> the last sentence can be removed. same meaning as the first one.
>
sounds good.
> > + */
> > + if (!iommu_iotlb_gather_queued(gather))
> > + iommu_iotlb_gather_add_page(domain, gather, iova,
> > size);
>
> Reviewed-by: Kevin Tian <kevin.tian@intel.com>
>
Thanks,
Jacob
prev parent reply other threads:[~2023-02-09 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 18:18 [PATCH v2] iommu/vt-d: Avoid superfluous IOTLB tracking in lazy mode Jacob Pan
2023-02-09 2:09 ` Tian, Kevin
2023-02-09 17:43 ` Jacob Pan [this message]
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=20230209094330.12a94139@jacob-builder \
--to=jacob.jun.pan@linux.intel.com \
--cc=ashok.raj@intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=sanjay.k.kumar@intel.com \
--cc=stable@vger.kernel.org \
--cc=sukumar.ghorai@intel.com \
--cc=yi.l.liu@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.