From: Baolu Lu <baolu.lu@linux.intel.com>
To: iommu@lists.linux.dev
Cc: baolu.lu@linux.intel.com, Joerg Roedel <joro@8bytes.org>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Kevin Tian <kevin.tian@intel.com>,
raghunathan.srinivasan@intel.com, yi.l.liu@intel.com,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 1/1] iommu/vt-d: Correctly calculate sagaw value of IOMMU
Date: Tue, 23 Aug 2022 14:25:09 +0800 [thread overview]
Message-ID: <8702c6eb-bfd6-49d1-f96e-e9ae08cd87b0@linux.intel.com> (raw)
In-Reply-To: <20220817023558.3253263-1-baolu.lu@linux.intel.com>
On 2022/8/17 10:35, Lu Baolu wrote:
> The Intel IOMMU driver possibly selects between the first-level and the
> second-level translation tables for DMA address translation. However,
> the levels of page-table walks for the 4KB base page size are calculated
> from the SAGAW field of the capability register, which is only valid for
> the second-level page table. This causes the IOMMU driver to stop working
> if the hardware (or the emulated IOMMU) advertises only first-level
> translation capability and reports the SAGAW field as 0.
>
> This solves the above problem by considering both the first level and the
> second level when calculating the supported page table levels.
>
> Fixes: b802d070a52a1 ("iommu/vt-d: Use iova over first level")
> Cc:stable@vger.kernel.org
> Signed-off-by: Lu Baolu<baolu.lu@linux.intel.com>
This patch has been queued:
https://lore.kernel.org/linux-iommu/20220823061557.1631056-1-baolu.lu@linux.intel.com/
Best regards,
baolu
prev parent reply other threads:[~2022-08-23 6:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 2:35 [PATCH 1/1] iommu/vt-d: Correctly calculate sagaw value of IOMMU Lu Baolu
2022-08-23 6:25 ` Baolu Lu [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=8702c6eb-bfd6-49d1-f96e-e9ae08cd87b0@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=raghunathan.srinivasan@intel.com \
--cc=robin.murphy@arm.com \
--cc=stable@vger.kernel.org \
--cc=will@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox