From: Hanjun Guo <guohanjun@huawei.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>, <linux-pci@vger.kernel.org>,
"Alex Williamson" <alex.williamson@redhat.com>,
Donald Dutile <ddutile@redhat.com>
Subject: Re: [PATCH] PCI: Put the IVRS table in AMD ACS quirk handler
Date: Thu, 30 Jul 2020 14:14:43 +0800 [thread overview]
Message-ID: <74348feb-5646-6d33-1a84-532f9179df78@huawei.com> (raw)
In-Reply-To: <20200729230242.GA1974304@bjorn-Precision-5520>
On 2020/7/30 7:02, Bjorn Helgaas wrote:
> [+cc Alex, Don]
>
> On Wed, Jul 22, 2020 at 05:44:28PM +0800, Hanjun Guo wrote:
>> The acpi_get_table() should be coupled with acpi_put_table() if
>> the mapped table is not used at runtime to release the table
>> mapping.
>>
>> In pci_quirk_amd_sb_acs(), IVRS table is just used for checking
>> AMD IOMMU is supported, not used at runtime, put the table after
>> using it.
>>
>> Signed-off-by: Hanjun Guo <guohanjun@huawei.com>
>
> Applied to pci/virtualization for v5.9, thanks!
>
> I added this:
>
> Fixes: 15b100dfd1c9 ("PCI: Claim ACS support for AMD southbridge devices")
>
> but I didn't add a stable tag. Does this cause any issue that would
> warrant a stable tag?
We don't have one when I was sending same function patch for ACPI
subsystem, so I think it's OK to without a stable tag for this
patch as well.
Thanks
Hanjun
next prev parent reply other threads:[~2020-07-30 6:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 9:44 [PATCH] PCI: Put the IVRS table in AMD ACS quirk handler Hanjun Guo
2020-07-29 23:02 ` Bjorn Helgaas
2020-07-30 6:14 ` Hanjun Guo [this message]
2020-07-30 16:30 ` Don Dutile
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=74348feb-5646-6d33-1a84-532f9179df78@huawei.com \
--to=guohanjun@huawei.com \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=ddutile@redhat.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@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;
as well as URLs for NNTP newsgroup(s).