From: Hanjun Guo <guohanjun@huawei.com>
To: "Felix Kuehling" <felix.kuehling@amd.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"David Airlie" <airlied@linux.ie>,
"Daniel Vetter" <daniel@ffwll.ch>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/amdkfd: Put ACPI table after using it
Date: Fri, 31 Jul 2020 14:15:14 +0800 [thread overview]
Message-ID: <4d220f68-e259-ee4d-127d-7f9056aa7aa6@huawei.com> (raw)
In-Reply-To: <443ace32-0860-f823-bc3f-3faafd5da54e@amd.com>
On 2020/7/31 10:41, Felix Kuehling wrote:
> Hi Hanjun,
>
> Sorry for the late reply.
>
> Thank you for the patch and the explanation. This seems to have been
> broken since the first version of KFD in 2014. See one suggestion inline.
>
> Am 2020-07-22 um 5:48 a.m. schrieb Hanjun Guo:
>> 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 kfd_create_crat_image_acpi(), crat_table is copied to pcrat_image,
>> and in kfd_create_vcrat_image_cpu(), the acpi_table is only used to
>> get the OEM info, so those table mappings need to be release after
>> using it.
>>
>> Signed-off-by: Hanjun Guo <guohanjun@huawei.com>
>> ---
>> drivers/gpu/drm/amd/amdkfd/kfd_crat.c | 16 +++++++++++-----
>> 1 file changed, 11 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_crat.c b/drivers/gpu/drm/amd/amdkfd/kfd_crat.c
>> index 1009a3b..d378e61 100644
>> --- a/drivers/gpu/drm/amd/amdkfd/kfd_crat.c
>> +++ b/drivers/gpu/drm/amd/amdkfd/kfd_crat.c
>> @@ -756,6 +756,7 @@ int kfd_create_crat_image_acpi(void **crat_image, size_t *size)
>> struct acpi_table_header *crat_table;
>> acpi_status status;
>> void *pcrat_image;
>> + int rc = 0;
>>
>> if (!crat_image)
>> return -EINVAL;
>> @@ -776,17 +777,21 @@ int kfd_create_crat_image_acpi(void **crat_image, size_t *size)
>>
>> if (ignore_crat) {
>> pr_info("CRAT table disabled by module option\n");
>
> We should probably move this check to before we get the CRAT table.
> There is not point getting and putting it if we're going to ignore it
> anyway.
>
> Do you want to send an updated patch with that change? Or maybe do it as
> a 2-patch series?
I will do it as 2-patch series and send a updated patch set.
Thanks
Hanjun
next prev parent reply other threads:[~2020-07-31 6:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 9:48 Hanjun Guo
2020-07-31 2:41 ` Felix Kuehling
2020-07-31 6:15 ` Hanjun Guo [this message]
2020-07-23 5:19 Markus Elfring
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=4d220f68-e259-ee4d-127d-7f9056aa7aa6@huawei.com \
--to=guohanjun@huawei.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=felix.kuehling@amd.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®