From: Baolu Lu <baolu.lu@linux.intel.com>
To: Yi Liu <yi.l.liu@intel.com>
Cc: baolu.lu@linux.intel.com, kevin.tian@intel.com,
baolu.lu@intel.com, raghunathan.srinivasan@intel.com,
iommu@lists.linux.dev, joro@8bytes.org, will@kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH 1/2] iommu/vt-d: Check correct capability for sagaw determination
Date: Wed, 21 Sep 2022 14:08:42 +0800 [thread overview]
Message-ID: <de65f9ae-dd74-3f70-35c7-861832a1de7b@linux.intel.com> (raw)
In-Reply-To: <23d38de5-3aab-3fe7-2b17-cbf1ab8d6cab@intel.com>
On 2022/9/21 11:35, Yi Liu wrote:
> On 2022/9/21 10:44, Baolu Lu wrote:
>> On 9/16/22 3:12 PM, Yi Liu wrote:
>>> Check 5-level paging capability for 57 bits address width instead of
>>> checking 1GB large page capability.
>>>
>>> Fixes: 53fc7ad6edf2 ("iommu/vt-d: Correctly calculate sagaw value of
>>> IOMMU")
>>> Cc:stable@vger.kernel.org
>>> Reported-by: Raghunathan Srinivasan<raghunathan.srinivasan@intel.com>
>>> Signed-off-by: Yi Liu<yi.l.liu@intel.com>
>>
>> Queued for v6.0. Thank you very much!
>>
>> https://lore.kernel.org/linux-iommu/20220921024054.3570256-1-baolu.lu@linux.intel.com
>
> grt. btw. how about below? not sure why it didn't show up in this
> series. 🙁
>
> https://lore.kernel.org/linux-iommu/BN9PR11MB5276F062B5C0C08F10EFB49F8C4C9@BN9PR11MB5276.namprd11.prod.outlook.com/
This is not a fix. I will queue it for v6.1-rc1 later.
Best regards,
baolu
prev parent reply other threads:[~2022-09-21 6:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 7:12 [PATCH 0/2] Misc fixes to intel iommu driver Yi Liu
2022-09-16 7:12 ` [PATCH 1/2] iommu/vt-d: Check correct capability for sagaw determination Yi Liu
2022-09-17 2:15 ` Baolu Lu
2022-09-17 16:48 ` Jerry Snitselaar
2022-09-20 7:24 ` Tian, Kevin
2022-09-21 2:44 ` Baolu Lu
2022-09-21 3:35 ` Yi Liu
2022-09-21 6:08 ` 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=de65f9ae-dd74-3f70-35c7-861832a1de7b@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=baolu.lu@intel.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=raghunathan.srinivasan@intel.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;
as well as URLs for NNTP newsgroup(s).