The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Alejandro Jimenez <alejandro.j.jimenez@oracle.com>
Cc: iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
	suravee.suthikulpanit@amd.com, vasant.hegde@amd.com,
	will@kernel.org, jgg@nvidia.com, joao.m.martins@oracle.com,
	boris.ostrovsky@oracle.com
Subject: Re: [PATCH 1/1] iommu/amd: Preserve default DTE fields when updating Host Page Table Root
Date: Fri, 28 Feb 2025 12:18:19 +0100	[thread overview]
Message-ID: <Z8Gbe6InZ862dn6E@8bytes.org> (raw)
In-Reply-To: <20250106191413.3107140-1-alejandro.j.jimenez@oracle.com>

On Mon, Jan 06, 2025 at 07:14:13PM +0000, Alejandro Jimenez wrote:
> When updating the page table root field on the DTE, avoid overwriting any
> bits that are already set. The earlier call to make_clear_dte() writes
> default values that all DTEs must have set (currently DTE[V]), and those
> must be preserved.
> 
> Currently this doesn't cause problems since the page table root update is
> the first field that is set after make_clear_dte() is called, and
> DTE_FLAG_V is set again later along with the permission bits (IR/IW).
> Remove this redundant assignment too.
> 
> Fixes: fd5dff9de4be ("iommu/amd: Modify set_dte_entry() to use 256-bit DTE helpers")
> Signed-off-by: Alejandro Jimenez <alejandro.j.jimenez@oracle.com>
> ---
>  drivers/iommu/amd/iommu.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

Applied, thanks.

      parent reply	other threads:[~2025-02-28 11:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-06 19:14 [PATCH 1/1] iommu/amd: Preserve default DTE fields when updating Host Page Table Root Alejandro Jimenez
2025-01-07  8:50 ` Srivastava, Dheeraj Kumar
2025-01-07 12:15 ` Vasant Hegde
2025-01-07 13:36   ` Arun Kodilkar, Sairaj
2025-01-07 18:01   ` Jason Gunthorpe
2025-02-26 16:19     ` Alejandro Jimenez
2025-02-26 16:35       ` Jason Gunthorpe
2025-02-28  9:54       ` Vasant Hegde
2025-02-28 11:18 ` Joerg Roedel [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=Z8Gbe6InZ862dn6E@8bytes.org \
    --to=joro@8bytes.org \
    --cc=alejandro.j.jimenez@oracle.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@nvidia.com \
    --cc=joao.m.martins@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=vasant.hegde@amd.com \
    --cc=will@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