From: Greg KH <gregkh@linuxfoundation.org>
To: Lu Baolu <baolu.lu@linux.intel.com>
Cc: sashal@kernel.org, ashok.raj@intel.com, jroedel@suse.de,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [REWORKED PATCH 1/1] iommu/vt-d: Preset Access/Dirty bits for IOVA over FL
Date: Mon, 17 May 2021 09:07:55 +0200 [thread overview]
Message-ID: <YKIWS0lFKTcZ9094@kroah.com> (raw)
In-Reply-To: <20210517034913.3432-1-baolu.lu@linux.intel.com>
On Mon, May 17, 2021 at 11:49:13AM +0800, Lu Baolu wrote:
> [ Upstream commit a8ce9ebbecdfda3322bbcece6b3b25888217f8e3 ]
>
> The Access/Dirty bits in the first level page table entry will be set
> whenever a page table entry was used for address translation or write
> permission was successfully translated. This is always true when using
> the first-level page table for kernel IOVA. Instead of wasting hardware
> cycles to update the certain bits, it's better to set them up at the
> beginning.
>
> Suggested-by: Ashok Raj <ashok.raj@intel.com>
> Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
> Link: https://lore.kernel.org/r/20210115004202.953965-1-baolu.lu@linux.intel.com
> Signed-off-by: Joerg Roedel <jroedel@suse.de>
> Signed-off-by: Sasha Levin <sashal@kernel.org>
> ---
> drivers/iommu/intel/iommu.c | 14 ++++++++++++--
> include/linux/intel-iommu.h | 2 ++
> 2 files changed, 14 insertions(+), 2 deletions(-)
>
> [Note:
> - This is a reworked patch of
> https://lore.kernel.org/stable/20210512144819.664462530@linuxfoundation.org/T/#m65267f0a0091c2fcbde097cea91089775908faad.
> - It aims to fix a reported issue of
> https://bugzilla.kernel.org/show_bug.cgi?id=213077.
> - Please help to review and test.]
What stable tree(s) is this supposed to be for?
thanks,
greg k-h
next prev parent reply other threads:[~2021-05-17 7:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 3:49 [REWORKED PATCH 1/1] iommu/vt-d: Preset Access/Dirty bits for IOVA over FL Lu Baolu
2021-05-17 7:07 ` Greg KH [this message]
2021-05-17 7:17 ` Lu Baolu
2021-05-17 7:27 ` Greg KH
2021-05-17 7:51 ` Lu Baolu
2021-05-17 10:01 ` Greg KH
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=YKIWS0lFKTcZ9094@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ashok.raj@intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).