All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baolu Lu <baolu.lu@linux.intel.com>
To: Tina Zhang <tina.zhang@intel.com>, iommu@lists.linux.dev
Cc: baolu.lu@linux.intel.com
Subject: Re: [PATCH] iommu/vt-d: Set SRE bit when hardware has SRS cap
Date: Mon, 14 Nov 2022 20:00:44 +0800	[thread overview]
Message-ID: <6a34aa78-17d2-bb44-1e50-76239cd1ffbb@linux.intel.com> (raw)
In-Reply-To: <20221114085514.1105039-1-tina.zhang@intel.com>

On 2022/11/14 16:55, Tina Zhang wrote:
> SRS cap is the hardware cap telling if the hardware IOMMU can support
> requests seeking supervisor privilege or not. SRE bit in scalable-mode
> PASID table entry is treated as Reserved(0) for implementation not
> supporting SRS cap.
> 
> Checking SRS cap before setting SRE bit can avoid the non-recoverable
> fault of "Non-zero reserved field set in PASID Table Entry" caused by
> setting SRE bit while there is no SRS cap support.
> 
> Currently, both intel_pasid_setup_first_level() and
> intel_pasid_setup_second_level() implicitly take care about of it. The
> only missing SRS cap checking is in intel_pasid_setup_pass_through().
> 
> Fixes: 6f7db75e1c46 ("iommu/vt-d: Add second level page table interface")
> Signed-off-by: Tina Zhang<tina.zhang@intel.com>

Nice catch! Tina.

Can you please double check  intel_pasid_setup_second_level()? Its seems
that we missed such check there as well.

Best regards,
baolu

  reply	other threads:[~2022-11-14 12:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-14  8:55 [PATCH] iommu/vt-d: Set SRE bit when hardware has SRS cap Tina Zhang
2022-11-14 12:00 ` Baolu Lu [this message]
2022-11-14 23:55   ` tina.zhang
2022-11-15  1:40     ` Baolu Lu
2022-11-15  2:12       ` tina.zhang

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=6a34aa78-17d2-bb44-1e50-76239cd1ffbb@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=tina.zhang@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.