From: Lu Baolu <baolu.lu@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: baolu.lu@linux.intel.com, Joerg Roedel <joro@8bytes.org>,
stable@vger.kernel.org,
Saeed Mirzamohammadi <saeed.mirzamohammadi@oracle.com>,
Ashok Raj <ashok.raj@intel.com>, Camille Lu <camille.lu@hpe.com>
Subject: Re: [PATCH 1/1] iommu/vt-d: Fix agaw for a supported 48 bit guest address width
Date: Mon, 16 Aug 2021 21:15:19 +0800 [thread overview]
Message-ID: <4f7ecd17-0b24-51b9-ea0e-5da90a5e2510@linux.intel.com> (raw)
In-Reply-To: <YRpcIKvXY3LzXaqt@kroah.com>
On 2021/8/16 20:37, Greg Kroah-Hartman wrote:
> On Mon, Aug 16, 2021 at 08:20:31PM +0800, Lu Baolu wrote:
>> Hi Greg,
>>
>> On 2021/8/16 19:48, Greg Kroah-Hartman wrote:
>>> On Mon, Aug 16, 2021 at 07:39:32PM +0800, Lu Baolu wrote:
>>>> From: Saeed Mirzamohammadi <saeed.mirzamohammadi@oracle.com>
>>>>
>>>> [ Upstream commit 327d5b2fee91c404a3956c324193892cf2cc9528 ]
>>>
>>> Also, this really does not look like this commit at all :(
>>>
>>
>> This is not a back port. It's a fix for some stable kernels. Sorry for
>> the confusion.
>>
>> The error happens in a helper function that has been deprecated in the
>> upstream kernel by above commit. I added below explanation in the commit
>> message:
>>
>> "
>> This issue happens on the code path of getting a private domain for a
>> device. A private domain was needed when the domain of an iommu group
>> couldn't meet the requirement of a device. The IOMMU core has been
>> evolved to eliminate the need for private domain, hence this code path
>> has already been removed from the upstream since commit 327d5b2fee91c
>> ("iommu/vt-d: Allow 32bit devices to uses DMA domain"). Instead of back
>> porting all patches that are required for removing the private domain,
>> this simply fixes it in the affected stable kernel between v4.16 and v5.7.
>> "
>>
>> I'm sorry if this is not the right way to do this.
>
> Ah, sorry, I totally missed that. This is fine, now queued up for
> 4.19.y and 5.4.y.
Thank you! Greg.
Best regards,
baolu
>
> thanks,
>
> greg k-h
>
prev parent reply other threads:[~2021-08-16 13:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 11:39 [PATCH 1/1] iommu/vt-d: Fix agaw for a supported 48 bit guest address width Lu Baolu
2021-08-16 11:47 ` Greg Kroah-Hartman
2021-08-16 11:48 ` Greg Kroah-Hartman
2021-08-16 12:20 ` Lu Baolu
2021-08-16 12:37 ` Greg Kroah-Hartman
2021-08-16 13:15 ` Lu Baolu [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=4f7ecd17-0b24-51b9-ea0e-5da90a5e2510@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=ashok.raj@intel.com \
--cc=camille.lu@hpe.com \
--cc=gregkh@linuxfoundation.org \
--cc=joro@8bytes.org \
--cc=saeed.mirzamohammadi@oracle.com \
--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