From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.8 required=3.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,HTTPS_HTTP_MISMATCH, INCLUDES_CR_TRAILER,INCLUDES_PATCH,MAILING_LIST_MULTI,MIME_HTML_MOSTLY, NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3CA5AC433B4 for ; Tue, 11 May 2021 14:07:48 +0000 (UTC) Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id DE60E61155 for ; Tue, 11 May 2021 14:07:47 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org DE60E61155 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=amd-gfx-bounces@lists.freedesktop.org Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 958456EA44; Tue, 11 May 2021 14:07:47 +0000 (UTC) Received: from mail-ed1-x52b.google.com (mail-ed1-x52b.google.com [IPv6:2a00:1450:4864:20::52b]) by gabe.freedesktop.org (Postfix) with ESMTPS id 0D9FC6EA44 for ; Tue, 11 May 2021 14:07:47 +0000 (UTC) Received: by mail-ed1-x52b.google.com with SMTP id c22so23020114edn.7 for ; Tue, 11 May 2021 07:07:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=zUJ6yE6ygdDPHSMfeuNBl/3AQieYn03TkTI2omxlHHM=; b=r9mH7MWNMRrMQqHpZksKaEwHLuKpTSHXvx6Hpb8QoP/GXQS24moqFzXHQ6+rkuUs2F 9SS4RmL7hdhVcq6X9sGZ/MQ0oGsmw4pwvsiZ8CbxETdhJJEtyli7ru1GY8+0H+60Er0p tdM/E0RkNcTgd+GLwVd6kbx+A8v2szJHSwYkC4lSrSUnYdRqekgD+PfT6sxFMS8BcPDY VoGLEO1Nlv3IlVmrQ85+mRe0nuJ4Tbquy+C16muSZvRcroCQK2opQ55vV3TsjVdmPmSr 8+zqbfur6jfr6h9h5pHKBoxO18XE9LuuVLJrLTTcr5glB/FZlccXB8ZXIJC5fKxprzA9 puvg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=zUJ6yE6ygdDPHSMfeuNBl/3AQieYn03TkTI2omxlHHM=; b=YjaEGygT2djOUj47fZTHrwSCeKMBXBASmR4UJXhHDAcIJVUl6LlUZdrl98vBYljfX8 ZCB/x97V9Yg+usAXNvP/2ZwphxQTZfj+djw+XH0lFCXNH+Ry7uNJn7EkKYw7oDDyDMce VftSvHsLxCROEzGGdgF04Aj3vvSBDyK1PRHU4xGTfHMmJ+WhBFri+doZofF7hVv9wf84 CgEnxH1DKHtBuhVh/GD50+dos3+kHHzRvjwF7LBWIxFVEiGrLzFhSfCD2BCHV+bZdD2s MUqJU4xwQ5mwrTtFUzAsNajdYNEhisBfWesbMcPtPUaDAu68H/uFkHDl6ivmjQHu8v+n 86UQ== X-Gm-Message-State: AOAM533wDQVlVTAJN8DQrIgddBnbz3T834ECsqVCfHOjQ8JIZcf6Awg4 zqyRW7MoWsnG5CS/rMHnHEg= X-Google-Smtp-Source: ABdhPJwW4UgJqbJbzx7CbiBN2FDPxIM9aSMfVrrhjXHdzVthCCAp+hHH3s60yx81ZjmTZGrvIK7tKg== X-Received: by 2002:a05:6402:51c9:: with SMTP id r9mr32555480edd.94.1620742065694; Tue, 11 May 2021 07:07:45 -0700 (PDT) Received: from ?IPv6:2a02:908:1252:fb60:5935:8b67:3cdd:7cc1? ([2a02:908:1252:fb60:5935:8b67:3cdd:7cc1]) by smtp.gmail.com with ESMTPSA id k26sm11757220eje.67.2021.05.11.07.07.44 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 11 May 2021 07:07:45 -0700 (PDT) Subject: Re: [PATCH] drm/amdgpu: Align serial size in drm_amdgpu_info_vbios To: "Deucher, Alexander" , =?UTF-8?B?TWFyZWsgT2zFocOhaw==?= References: <20210508064740.7705-1-Jiawei.Gu@amd.com> <447046CE-6FB4-49D7-A74A-2188654F5D5C@amd.com> <88e868eb-347b-611b-8d88-ba8d9d61c23b@gmail.com> From: =?UTF-8?Q?Christian_K=c3=b6nig?= Message-ID: <454dbf38-3337-de8b-6a29-30f417475121@gmail.com> Date: Tue, 11 May 2021 16:07:42 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US X-BeenThere: amd-gfx@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion list for AMD gfx List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Kees Cook , "Gu, JiaWei \(Will\)" , amd-gfx list , "Deng, Emily" , Alex Deucher , "Nieto, David M" Content-Type: multipart/mixed; boundary="===============1580216111==" Errors-To: amd-gfx-bounces@lists.freedesktop.org Sender: "amd-gfx" This is a multi-part message in MIME format. --===============1580216111== Content-Type: multipart/alternative; boundary="------------4C193A0472876E4D7FD1A496" Content-Language: en-US This is a multi-part message in MIME format. --------------4C193A0472876E4D7FD1A496 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Yeah, but umr is making strong use of sysfs as well. The only justification of this interface would be if we want to use it in Mesa. And I agree with Marek that looks redundant with the device structure to me as well. Christian. Am 11.05.21 um 16:04 schrieb Deucher, Alexander: > > [AMD Public Use] > > > It's being used by umr and some other smi tools to provide vbios > information for debugging. > > Alex > > ------------------------------------------------------------------------ > *From:* amd-gfx on behalf of > Marek Olšák > *Sent:* Tuesday, May 11, 2021 4:18 AM > *To:* Christian König > *Cc:* Kees Cook ; Gu, JiaWei (Will) > ; amd-gfx list ; > Deng, Emily ; Alex Deucher > ; Nieto, David M > *Subject:* Re: [PATCH] drm/amdgpu: Align serial size in > drm_amdgpu_info_vbios > Mesa doesn't use sysfs. > > Note that this is a uapi, meaning that once it's in the kernel, it > can't be changed like that. > > What's the use case for this new interface? Isn't it partially > redundant with the current device info structure, which seems to have > the equivalent of dev_id and rev_id? > > Marek > > On Tue, May 11, 2021 at 3:51 AM Christian König > > wrote: > > Marek and other userspace folks need to decide that. > > Basic question here is if Mesa is already accessing sysfs nodes > for OpenGL or RADV. If that is the case then we should probably > expose the information there as well. > > If that isn't the case (which I think it is) then we should > implement it as IOCTL. > > Regards, > Christian. > > Am 10.05.21 um 22:19 schrieb Nieto, David M: >> >> One of the primary usecases is to add this information to the >> renderer string, I am not sure if there are other cases of UMD >> drivers accessing sysfs nodes, but I think if we think >> permissions, if a client is authenticated and opens the render >> device then it can use the IOCTL, it is unclear to me we can make >> a such an assumption for sysfs nodes… >> >> I think there is value in having both tbh. >> >> Regards, >> >> David >> >> *From: *Christian König >> >> *Date: *Monday, May 10, 2021 at 6:48 AM >> *To: *"Nieto, David M" >> , "Gu, JiaWei (Will)" >> >> *Cc: *Alex Deucher >> , "Deng, Emily" >> , Kees Cook >> , amd-gfx >> list >> >> *Subject: *Re: [PATCH] drm/amdgpu: Align serial size in >> drm_amdgpu_info_vbios >> >> Well we could add both as sysfs file(s). >> >> Question here is rather what is the primary use case of this and >> if the application has the necessary access permissions to the >> sysfs files? >> >> Regards, >> Christian. >> >> Am 10.05.21 um 15:42 schrieb Nieto, David M: >> >> Then the application would need to issue the ioctl and then >> open a sysfs file to get all the information it needs. It >> makes little sense from a programming perspective to add an >> incomplete interface in my opinion >> >> ------------------------------------------------------------------------ >> >> *From:*Gu, JiaWei (Will) >> >> *Sent:* Monday, May 10, 2021 12:13:07 AM >> *To:* Nieto, David M >> >> *Cc:* Alex Deucher >> ; amd-gfx list >> >> ; Kees Cook >> ; Deng, >> Emily >> *Subject:* RE: [PATCH] drm/amdgpu: Align serial size in >> drm_amdgpu_info_vbios >> >> [AMD Official Use Only - Internal Distribution Only] >> >> Hi David, >> >> What I meant is to ONLY delete the serial[16] from >> drm_amdgpu_info_vbios, not the whole struct. >> >> struct drm_amdgpu_info_vbios { >>         __u8 name[64]; >>         __u32 dbdf; >>         __u8 vbios_pn[64]; >>         __u32 version; >>         __u8 date[32]; >>         __u8 serial[16]; // jiawei: shall we delete this >>         __u32 dev_id; >>         __u32 rev_id; >>         __u32 sub_dev_id; >>         __u32 sub_ved_id; >> }; >> >> serial[16] in drm_amdgpu_info_vbios  copied from >> adev->serial, but there's already a sysfs named >> serial_number, which exposes it already. >> >> static ssize_t amdgpu_device_get_serial_number(struct device >> *dev, >>                 struct device_attribute *attr, char *buf) >> { >>         struct drm_device *ddev = dev_get_drvdata(dev); >>         struct amdgpu_device *adev = ddev->dev_private; >> >>         return snprintf(buf, PAGE_SIZE, "%s\n", adev->serial); >> } >> >> Thanks, >> Jiawei >> >> >> -----Original Message----- >> From: Nieto, David M >> >> Sent: Monday, May 10, 2021 2:53 PM >> To: Gu, JiaWei (Will) >> >> Cc: Alex Deucher >> ; amd-gfx list >> >> ; Kees Cook >> ; Deng, >> Emily >> Subject: Re: [PATCH] drm/amdgpu: Align serial size in >> drm_amdgpu_info_vbios >> >> No, this structure contains all the details of the vbios: >> date, serial number, name, etc. >> >> The sysfs node only contains the vbios name string >> >> > On May 9, 2021, at 23:33, Gu, JiaWei (Will) >> wrote: >> > >> > [AMD Official Use Only - Internal Distribution Only] >> > >> > With a second thought, >> > __u8 serial[16] in drm_amdgpu_info_vbios is a bit >> redundant, sysfs serial_number already exposes it. >> > >> > Is it fine to abandon it from drm_amdgpu_info_vbios struct? >> @Alex >> > Deucher @Nieto, David M >> > >> > Best regards, >> > Jiawei >> > >> > -----Original Message----- >> > From: Alex Deucher >> >> > Sent: Sunday, May 9, 2021 11:59 PM >> > To: Gu, JiaWei (Will) >> >> > Cc: amd-gfx list >> ; Kees Cook >> > >> > Subject: Re: [PATCH] drm/amdgpu: Align serial size in >> > drm_amdgpu_info_vbios >> > >> >> On Sat, May 8, 2021 at 2:48 AM Jiawei Gu >> wrote: >> >> >> >> 20 should be serial char size now instead of 16. >> >> >> >> Signed-off-by: Jiawei Gu >> >> > >> > Please make sure this keeps proper 64 bit alignment in the >> structure. >> > >> > Alex >> > >> > >> >> --- >> >> include/uapi/drm/amdgpu_drm.h | 2 +- >> >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> >> >> diff --git a/include/uapi/drm/amdgpu_drm.h >> >> b/include/uapi/drm/amdgpu_drm.h index >> 2b487a8d2727..1c20721f90da >> >> 100644 >> >> --- a/include/uapi/drm/amdgpu_drm.h >> >> +++ b/include/uapi/drm/amdgpu_drm.h >> >> @@ -957,7 +957,7 @@ struct drm_amdgpu_info_vbios { >> >>        __u8 vbios_pn[64]; >> >>        __u32 version; >> >>        __u8 date[32]; >> >> -       __u8 serial[16]; >> >> +       __u8 serial[20]; >> >>        __u32 dev_id; >> >>        __u32 rev_id; >> >>        __u32 sub_dev_id; >> >> -- >> >> 2.17.1 >> >> >> >> _______________________________________________ >> >> amd-gfx mailing list >> >> amd-gfx@lists.freedesktop.org >> >> >> >> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flis >> >> >> t >> >> s.freedesktop.org >> %2Fmailman%2Flistinfo%2Famd-gfx&data=04%7C01%7CJ >> >> i >> >> awei.Gu%40amd.com >> %7Ccea31833184c41e8574508d9130360cc%7C3dd8961fe4884e >> >> 6 >> >> >> 08e11a82d994e183d%7C0%7C0%7C637561727523880356%7CUnknown%7CTWFpbGZsb3 >> >> d >> >> >> 8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7 >> >> C >> >> >> 1000&sdata=kAJiC6WoJUTeExwk6ftrLfMoY2OTAwg9X7mGgJT3kLk%3D&res >> >> e >> >> rved=0 >> >> >> >> _______________________________________________ >> >> amd-gfx mailing list >> >> amd-gfx@lists.freedesktop.org >> >> https://lists.freedesktop.org/mailman/listinfo/amd-gfx >> >> >> > > _______________________________________________ > amd-gfx mailing list > amd-gfx@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/amd-gfx > > --------------4C193A0472876E4D7FD1A496 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 8bit Yeah, but umr is making strong use of sysfs as well.

The only justification of this interface would be if we want to use it in Mesa.

And I agree with Marek that looks redundant with the device structure to me as well.

Christian.

Am 11.05.21 um 16:04 schrieb Deucher, Alexander:

[AMD Public Use]


It's being used by umr and some other smi tools to provide vbios information for debugging.

Alex


From: amd-gfx <amd-gfx-bounces@lists.freedesktop.org> on behalf of Marek Olšák <maraeo@gmail.com>
Sent: Tuesday, May 11, 2021 4:18 AM
To: Christian König <ckoenig.leichtzumerken@gmail.com>
Cc: Kees Cook <keescook@chromium.org>; Gu, JiaWei (Will) <JiaWei.Gu@amd.com>; amd-gfx list <amd-gfx@lists.freedesktop.org>; Deng, Emily <Emily.Deng@amd.com>; Alex Deucher <alexdeucher@gmail.com>; Nieto, David M <David.Nieto@amd.com>
Subject: Re: [PATCH] drm/amdgpu: Align serial size in drm_amdgpu_info_vbios
 
Mesa doesn't use sysfs.

Note that this is a uapi, meaning that once it's in the kernel, it can't be changed like that.

What's the use case for this new interface? Isn't it partially redundant with the current device info structure, which seems to have the equivalent of dev_id and rev_id?

Marek

On Tue, May 11, 2021 at 3:51 AM Christian König <ckoenig.leichtzumerken@gmail.com> wrote:
Marek and other userspace folks need to decide that.

Basic question here is if Mesa is already accessing sysfs nodes for OpenGL or RADV. If that is the case then we should probably expose the information there as well.

If that isn't the case (which I think it is) then we should implement it as IOCTL.

Regards,
Christian.

Am 10.05.21 um 22:19 schrieb Nieto, David M:

One of the primary usecases is to add this information to the renderer string, I am not sure if there are other cases of UMD drivers accessing sysfs nodes, but I think if we think permissions, if a client is authenticated and opens the render device then it can use the IOCTL, it is unclear to me we can make a such an assumption for sysfs nodes…

 

I think there is value in having both tbh.

 

Regards,

David

 

From: Christian König <ckoenig.leichtzumerken@gmail.com>
Date: Monday, May 10, 2021 at 6:48 AM
To: "Nieto, David M" <David.Nieto@amd.com>, "Gu, JiaWei (Will)" <JiaWei.Gu@amd.com>
Cc: Alex Deucher <alexdeucher@gmail.com>, "Deng, Emily" <Emily.Deng@amd.com>, Kees Cook <keescook@chromium.org>, amd-gfx list <amd-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/amdgpu: Align serial size in drm_amdgpu_info_vbios

 

Well we could add both as sysfs file(s).

Question here is rather what is the primary use case of this and if the application has the necessary access permissions to the sysfs files?

Regards,
Christian.

Am 10.05.21 um 15:42 schrieb Nieto, David M:

Then the application would need to issue the ioctl and then open a sysfs file to get all the information it needs. It makes little sense from a programming perspective to add an incomplete interface in my opinion 

 


From: Gu, JiaWei (Will) <JiaWei.Gu@amd.com>
Sent: Monday, May 10, 2021 12:13:07 AM
To: Nieto, David M <David.Nieto@amd.com>
Cc: Alex Deucher <alexdeucher@gmail.com>; amd-gfx list <amd-gfx@lists.freedesktop.org>; Kees Cook <keescook@chromium.org>; Deng, Emily <Emily.Deng@amd.com>
Subject: RE: [PATCH] drm/amdgpu: Align serial size in drm_amdgpu_info_vbios

 

[AMD Official Use Only - Internal Distribution Only]

Hi David,

What I meant is to ONLY delete the serial[16] from drm_amdgpu_info_vbios, not the whole struct.

struct drm_amdgpu_info_vbios {
        __u8 name[64];
        __u32 dbdf;
        __u8 vbios_pn[64];
        __u32 version;
        __u8 date[32];
        __u8 serial[16]; // jiawei: shall we delete this
        __u32 dev_id;
        __u32 rev_id;
        __u32 sub_dev_id;
        __u32 sub_ved_id;
};

serial[16] in drm_amdgpu_info_vbios  copied from adev->serial, but there's already a sysfs named serial_number, which exposes it already.

static ssize_t amdgpu_device_get_serial_number(struct device *dev,
                struct device_attribute *attr, char *buf)
{
        struct drm_device *ddev = dev_get_drvdata(dev);
        struct amdgpu_device *adev = ddev->dev_private;

        return snprintf(buf, PAGE_SIZE, "%s\n", adev->serial);
}

Thanks,
Jiawei


-----Original Message-----
From: Nieto, David M <David.Nieto@amd.com>
Sent: Monday, May 10, 2021 2:53 PM
To: Gu, JiaWei (Will) <JiaWei.Gu@amd.com>
Cc: Alex Deucher <alexdeucher@gmail.com>; amd-gfx list <amd-gfx@lists.freedesktop.org>; Kees Cook <keescook@chromium.org>; Deng, Emily <Emily.Deng@amd.com>
Subject: Re: [PATCH] drm/amdgpu: Align serial size in drm_amdgpu_info_vbios

No, this structure contains all the details of the vbios: date, serial number, name, etc.

The sysfs node only contains the vbios name string

> On May 9, 2021, at 23:33, Gu, JiaWei (Will) <JiaWei.Gu@amd.com> wrote:
>
> [AMD Official Use Only - Internal Distribution Only]
>
> With a second thought,
> __u8 serial[16] in drm_amdgpu_info_vbios is a bit redundant, sysfs serial_number already exposes it.
>
> Is it fine to abandon it from drm_amdgpu_info_vbios struct? @Alex
> Deucher @Nieto, David M
>
> Best regards,
> Jiawei
>
> -----Original Message-----
> From: Alex Deucher <alexdeucher@gmail.com>
> Sent: Sunday, May 9, 2021 11:59 PM
> To: Gu, JiaWei (Will) <JiaWei.Gu@amd.com>
> Cc: amd-gfx list <amd-gfx@lists.freedesktop.org>; Kees Cook
> <keescook@chromium.org>
> Subject: Re: [PATCH] drm/amdgpu: Align serial size in
> drm_amdgpu_info_vbios
>
>> On Sat, May 8, 2021 at 2:48 AM Jiawei Gu <Jiawei.Gu@amd.com> wrote:
>>
>> 20 should be serial char size now instead of 16.
>>
>> Signed-off-by: Jiawei Gu <Jiawei.Gu@amd.com>
>
> Please make sure this keeps proper 64 bit alignment in the structure.
>
> Alex
>
>
>> ---
>> include/uapi/drm/amdgpu_drm.h | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/include/uapi/drm/amdgpu_drm.h
>> b/include/uapi/drm/amdgpu_drm.h index 2b487a8d2727..1c20721f90da
>> 100644
>> --- a/include/uapi/drm/amdgpu_drm.h
>> +++ b/include/uapi/drm/amdgpu_drm.h
>> @@ -957,7 +957,7 @@ struct drm_amdgpu_info_vbios {
>>        __u8 vbios_pn[64];
>>        __u32 version;
>>        __u8 date[32];
>> -       __u8 serial[16];
>> +       __u8 serial[20];
>>        __u32 dev_id;
>>        __u32 rev_id;
>>        __u32 sub_dev_id;
>> --
>> 2.17.1
>>
>> _______________________________________________
>> amd-gfx mailing list
>> amd-gfx@lists.freedesktop.org
>> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flis
>> t
>> s.freedesktop.org%2Fmailman%2Flistinfo%2Famd-gfx&amp;data=04%7C01%7CJ
>> i
>> awei.Gu%40amd.com%7Ccea31833184c41e8574508d9130360cc%7C3dd8961fe4884e
>> 6
>> 08e11a82d994e183d%7C0%7C0%7C637561727523880356%7CUnknown%7CTWFpbGZsb3
>> d
>> 8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7
>> C
>> 1000&amp;sdata=kAJiC6WoJUTeExwk6ftrLfMoY2OTAwg9X7mGgJT3kLk%3D&amp;res
>> e
>> rved=0



_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx




_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

--------------4C193A0472876E4D7FD1A496-- --===============1580216111== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx --===============1580216111==--