<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">
<blockquote type="cite">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Please
give me some detail approach on dma_fence, thanks !<o:p></o:p></span></p>
<span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p></o:p></span></blockquote>
I think the idea of using the fence_context is even better than
using the fence_status. It is already present for a while and
filtering the jobs/entities by it needs something like 10 lines of
code.<br>
<br>
The fence status is new and only available on newer kernels (we
would need to rebase to amd-staging-4.11).<br>
<br>
I will try to dig up later today the how the Intel guys solved
that problem.<br>
<br>
Christian.<br>
<br>
Am 03.05.2017 um 11:14 schrieb Liu, Monk:<br>
</div>
<blockquote
cite="mid:DM5PR12MB1610875E9D1BC9E967BE119A84160@DM5PR12MB1610.namprd12.prod.outlook.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
p.emailquote, li.emailquote, div.emailquote
{mso-style-name:emailquote;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:1.0pt;
border:none;
padding:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I
thought of that for the first place as well, that keep an ID
and parsing the ID with every job not signaled to see if the
job
<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Belongs
to something guilty , But keep ctx alive is more simple so I
choose this way.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">But
I admit it is doable as well, and I want to compare this
method and the dma_fence status filed you mentioned,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Please
give me some detail approach on dma_fence, thanks !<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">BR
Monk<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">
Christian König [<a class="moz-txt-link-freetext" href="mailto:deathsimple@vodafone.de">mailto:deathsimple@vodafone.de</a>]
<br>
<b>Sent:</b> Wednesday, May 03, 2017 5:12 PM<br>
<b>To:</b> Zhou, David(ChunMing)
<a class="moz-txt-link-rfc2396E" href="mailto:David1.Zhou@amd.com"><David1.Zhou@amd.com></a>; Liu, Monk
<a class="moz-txt-link-rfc2396E" href="mailto:Monk.Liu@amd.com"><Monk.Liu@amd.com></a>; <a class="moz-txt-link-abbreviated" href="mailto:amd-gfx@lists.freedesktop.org">amd-gfx@lists.freedesktop.org</a><br>
<b>Subject:</b> Re: [PATCH 1/5] drm/amdgpu:keep ctx
alive till all job finished<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-size:10.0pt">>
1) fence_context have chance to incorrectly represent
the context behind it, because the number can be used
up and will wrapped around from beginning
<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt">No,
fence_context is unique in global in kernel.</span><o:p></o:p></p>
</blockquote>
<p class="MsoNormal">Yeah, I would go with that as well.<br>
<br>
You note the fence_context of the job which caused the
trouble.<br>
<br>
Then take a look at all jobs on the recovery list and remove
the ones with the same fence_context number.<br>
<br>
Then take a look at all entities on the runlist and remove
the one with the same fence_context number. If it is already
freed you won't find any, but that shouldn't be a problem.<br>
<br>
This way you effectively can prevent other jobs from the
same context from running and the context query can simply
check if the entity is still on the runlist to figure out if
it was guilty or not.<br>
<br>
Regards,<br>
Christian.<br>
<br>
Am 03.05.2017 um 09:23 schrieb zhoucm1:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 2017<span style="font-family:SimSun"
lang="ZH-CN">年</span>05<span style="font-family:SimSun"
lang="ZH-CN">月</span>03<span style="font-family:SimSun"
lang="ZH-CN">日</span> 14:02, Liu, Monk wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-size:10.0pt">You
can add ctx as filed of job, but not get reference of
it, when you try to use ctx, just check if ctx ==
NULL.<br>
> that doesn't work at all... job->ctx will
always be non-NULL after it is initialized, you just
refer to a wild pointer after CTX released
<o:p></o:p></span></p>
</div>
</blockquote>
<p class="MsoNormal"><span style="font-size:10.0pt">job->ctx
is a **ctx, which could resolve your this concern.<br>
<br>
<br>
</span><o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-size:10.0pt"><br>
Another stupid method:<br>
Use idr_for_each_entry(..job->vm->ctx_mgr...)
and compare the job->fence->fence_context with
ctx->ring[].entity->fence_context. if not found,
then ctx is freed, otherwise you can do your things
for this ctx.<br>
> 1) fence_context have chance to incorrectly
represent the context behind it, because the number
can be used up and will wrapped around from beginning
<o:p></o:p></span></p>
</div>
</blockquote>
<p class="MsoNormal"><span style="font-size:10.0pt">No,
fence_context is unique in global in kernel.<br>
<br>
Regards,<br>
David Zhou<br>
<br>
</span><o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-size:10.0pt"> 2)
why not just keep CTX alive, which is much simple than
this method
<br>
<br>
BR<br>
<br>
-----Original Message-----<br>
From: Zhou, David(ChunMing) <br>
Sent: Wednesday, May 03, 2017 12:54 PM<br>
To: Liu, Monk <a moz-do-not-send="true"
href="mailto:Monk.Liu@amd.com"><Monk.Liu@amd.com></a>;
Liu, Monk
<a moz-do-not-send="true"
href="mailto:Monk.Liu@amd.com"><Monk.Liu@amd.com></a>;
Christian König <a moz-do-not-send="true"
href="mailto:deathsimple@vodafone.de">
<deathsimple@vodafone.de></a>; <a
moz-do-not-send="true"
href="mailto:amd-gfx@lists.freedesktop.org">amd-gfx@lists.freedesktop.org</a><br>
Subject: RE: [PATCH 1/5] drm/amdgpu:keep ctx alive
till all job finished<br>
<br>
You can add ctx as filed of job, but not get reference
of it, when you try to use ctx, just check if ctx ==
NULL.
<br>
<br>
Another stupid method:<br>
Use idr_for_each_entry(..job->vm->ctx_mgr...)
and compare the job->fence->fence_context with
ctx->ring[].entity->fence_context. if not found,
then ctx is freed, otherwise you can do your things
for this ctx.<br>
<br>
Regards,<br>
David Zhou<br>
<br>
-----Original Message-----<br>
From: amd-gfx [<a moz-do-not-send="true"
href="mailto:amd-gfx-bounces@lists.freedesktop.org">mailto:amd-gfx-bounces@lists.freedesktop.org</a>]
On Behalf Of Liu, Monk<br>
Sent: Wednesday, May 03, 2017 11:57 AM<br>
To: Liu, Monk <a moz-do-not-send="true"
href="mailto:Monk.Liu@amd.com"><Monk.Liu@amd.com></a>;
Christian König
<a moz-do-not-send="true"
href="mailto:deathsimple@vodafone.de"><deathsimple@vodafone.de></a>;
<a moz-do-not-send="true"
href="mailto:amd-gfx@lists.freedesktop.org">
amd-gfx@lists.freedesktop.org</a><br>
Subject: RE: [PATCH 1/5] drm/amdgpu:keep ctx alive
till all job finished<br>
<br>
@Christian,<br>
<br>
The thing is I need mark all entities behind this
timeout job as guilty, so I use a member in entity
named "ptr_guilty", to point to The member in
amdgpu_ctx named "guilty", that way read
*entity->ptr_guilty can get you if this entity is
"invalid", and set *entity->ptr_guilty Can let you
set all entities belongs to the context as "invalid".<br>
<br>
Above logic is to guarantee we can kick out all guilty
entities in entity kfifo, and also block all IOCTL
with a ctx handle point to this guilty context, And we
only recovery other jobs/entities/context after
scheduler unparked
<br>
<br>
If you reject the patch to keep ctx alive till all
jobs signaled, please give me a solution to satisfy
above logic
<br>
<br>
BR Monk<br>
<br>
-----Original Message-----<br>
From: amd-gfx [<a moz-do-not-send="true"
href="mailto:amd-gfx-bounces@lists.freedesktop.org">mailto:amd-gfx-bounces@lists.freedesktop.org</a>]
On Behalf Of Liu, Monk<br>
Sent: Wednesday, May 03, 2017 11:31 AM<br>
To: Christian König <a moz-do-not-send="true"
href="mailto:deathsimple@vodafone.de"><deathsimple@vodafone.de></a>;
<a moz-do-not-send="true"
href="mailto:amd-gfx@lists.freedesktop.org">amd-gfx@lists.freedesktop.org</a><br>
Subject: RE: [PATCH 1/5] drm/amdgpu:keep ctx alive
till all job finished<br>
<br>
1, This is necessary otherwise how can I access entity
pointer after a job timedout , and why it is dangerous
?<br>
2, what's the status field in the fences you were
referring to ? I need to judge if it could satisfy my
requirement
<br>
<br>
<br>
<br>
-----Original Message-----<br>
From: Christian König [<a moz-do-not-send="true"
href="mailto:deathsimple@vodafone.de">mailto:deathsimple@vodafone.de</a>]<br>
Sent: Monday, May 01, 2017 10:48 PM<br>
To: Liu, Monk <a moz-do-not-send="true"
href="mailto:Monk.Liu@amd.com"><Monk.Liu@amd.com></a>;
<a moz-do-not-send="true"
href="mailto:amd-gfx@lists.freedesktop.org">
amd-gfx@lists.freedesktop.org</a><br>
Subject: Re: [PATCH 1/5] drm/amdgpu:keep ctx alive
till all job finished<br>
<br>
Am 01.05.2017 um 09:22 schrieb Monk Liu:<br>
> for TDR guilty context feature, we need access
ctx/s_entity field <br>
> member through sched job pointer,so ctx must keep
alive till all job <br>
> from it signaled.<br>
<br>
NAK, that is unnecessary and quite dangerous.<br>
<br>
Instead we have the designed status field in the
fences which should be checked for that.<br>
<br>
Regards,<br>
Christian.<br>
<br>
><br>
> Change-Id:
Ib87e9502f7a5c8c054c7e56956d7f7ad75998e43<br>
> Signed-off-by: Monk Liu <a
moz-do-not-send="true"
href="mailto:Monk.Liu@amd.com"><Monk.Liu@amd.com></a><br>
> ---<br>
> drivers/gpu/drm/amd/amdgpu/amdgpu.h |
6 +++++-<br>
> drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c |
2 +-<br>
> drivers/gpu/drm/amd/amdgpu/amdgpu_ctx.c |
9 +++++++++<br>
> drivers/gpu/drm/amd/amdgpu/amdgpu_job.c |
9 +++++++--<br>
> drivers/gpu/drm/amd/scheduler/gpu_scheduler.c |
6 ------<br>
> drivers/gpu/drm/amd/scheduler/gpu_scheduler.h |
1 +<br>
> 6 files changed, 23 insertions(+), 10
deletions(-)<br>
><br>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu.h<br>
> b/drivers/gpu/drm/amd/amdgpu/amdgpu.h<br>
> index e330009..8e031d6 100644<br>
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu.h<br>
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu.h<br>
> @@ -760,10 +760,12 @@ struct amdgpu_ib {<br>
> uint32_t flags;<br>
> };<br>
> <br>
> +struct amdgpu_ctx;<br>
> +<br>
> extern const struct amd_sched_backend_ops
amdgpu_sched_ops;<br>
> <br>
> int amdgpu_job_alloc(struct amdgpu_device
*adev, unsigned num_ibs,<br>
> - struct amdgpu_job **job,
struct amdgpu_vm *vm);<br>
> + struct amdgpu_job **job,
struct amdgpu_vm *vm, struct <br>
> +amdgpu_ctx *ctx);<br>
> int amdgpu_job_alloc_with_ib(struct
amdgpu_device *adev, unsigned size,<br>
> struct amdgpu_job
**job);<br>
> <br>
> @@ -802,6 +804,7 @@ struct amdgpu_ctx_mgr {<br>
> <br>
> struct amdgpu_ctx *amdgpu_ctx_get(struct
amdgpu_fpriv *fpriv, uint32_t id);<br>
> int amdgpu_ctx_put(struct amdgpu_ctx *ctx);<br>
> +struct amdgpu_ctx *amdgpu_ctx_kref_get(struct
amdgpu_ctx *ctx);<br>
> <br>
> uint64_t amdgpu_ctx_add_fence(struct amdgpu_ctx
*ctx, struct amdgpu_ring *ring,<br>
> struct fence
*fence);<br>
> @@ -1129,6 +1132,7 @@ struct amdgpu_job {<br>
> struct amdgpu_sync sync;<br>
> struct amdgpu_ib *ibs;<br>
> struct fence *fence; /* the hw
fence */<br>
> + struct amdgpu_ctx *ctx;<br>
> uint32_t preamble_status;<br>
> uint32_t num_ibs;<br>
> void *owner;<br>
> diff --git
a/drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c<br>
> b/drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c<br>
> index 699f5fe..267fb65 100644<br>
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c<br>
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c<br>
> @@ -234,7 +234,7 @@ int
amdgpu_cs_parser_init(struct amdgpu_cs_parser *p, void
*data)<br>
> }<br>
> }<br>
> <br>
> - ret = amdgpu_job_alloc(p->adev, num_ibs,
&p->job, vm);<br>
> + ret = amdgpu_job_alloc(p->adev, num_ibs,
&p->job, vm, p->ctx);<br>
> if (ret)<br>
> goto free_all_kdata;<br>
> <br>
> diff --git
a/drivers/gpu/drm/amd/amdgpu/amdgpu_ctx.c<br>
> b/drivers/gpu/drm/amd/amdgpu/amdgpu_ctx.c<br>
> index b4bbbb3..81438af 100644<br>
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_ctx.c<br>
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_ctx.c<br>
> @@ -25,6 +25,13 @@<br>
> #include <drm/drmP.h><br>
> #include "amdgpu.h"<br>
> <br>
> +struct amdgpu_ctx *amdgpu_ctx_kref_get(struct
amdgpu_ctx *ctx) {<br>
> + if (ctx)<br>
> + kref_get(&ctx->refcount);<br>
> + return ctx;<br>
> +}<br>
> +<br>
> static int amdgpu_ctx_init(struct amdgpu_device
*adev, struct amdgpu_ctx *ctx)<br>
> {<br>
> unsigned i, j;<br>
> @@ -56,6 +63,8 @@ static int
amdgpu_ctx_init(struct amdgpu_device *adev, struct
amdgpu_ctx *ctx)<br>
> rq,
amdgpu_sched_jobs);<br>
> if (r)<br>
> goto failed;<br>
> +<br>
> + ctx->rings[i].entity.ptr_guilty
= &ctx->guilty; /* kernel entity <br>
> +doesn't have ptr_guilty */<br>
> }<br>
> <br>
> return 0;<br>
> diff --git
a/drivers/gpu/drm/amd/amdgpu/amdgpu_job.c<br>
> b/drivers/gpu/drm/amd/amdgpu/amdgpu_job.c<br>
> index 690ef3d..208da11 100644<br>
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_job.c<br>
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_job.c<br>
> @@ -40,7 +40,7 @@ static void
amdgpu_job_timedout(struct amd_sched_job *s_job)<br>
> }<br>
> <br>
> int amdgpu_job_alloc(struct amdgpu_device
*adev, unsigned num_ibs,<br>
> - struct amdgpu_job **job,
struct amdgpu_vm *vm)<br>
> + struct amdgpu_job **job,
struct amdgpu_vm *vm, struct <br>
> +amdgpu_ctx *ctx)<br>
> {<br>
> size_t size = sizeof(struct amdgpu_job);<br>
> <br>
> @@ -57,6 +57,7 @@ int amdgpu_job_alloc(struct
amdgpu_device *adev, unsigned num_ibs,<br>
> (*job)->vm = vm;<br>
> (*job)->ibs = (void *)&(*job)[1];<br>
> (*job)->num_ibs = num_ibs;<br>
> + (*job)->ctx = amdgpu_ctx_kref_get(ctx);<br>
> <br>
> amdgpu_sync_create(&(*job)->sync);<br>
> <br>
> @@ -68,7 +69,7 @@ int
amdgpu_job_alloc_with_ib(struct amdgpu_device *adev,
unsigned size,<br>
> {<br>
> int r;<br>
> <br>
> - r = amdgpu_job_alloc(adev, 1, job, NULL);<br>
> + r = amdgpu_job_alloc(adev, 1, job, NULL,
NULL);<br>
> if (r)<br>
> return r;<br>
> <br>
> @@ -94,6 +95,10 @@ void
amdgpu_job_free_resources(struct amdgpu_job *job)<br>
> static void amdgpu_job_free_cb(struct
amd_sched_job *s_job)<br>
> {<br>
> struct amdgpu_job *job =
container_of(s_job, struct amdgpu_job, <br>
> base);<br>
> + struct amdgpu_ctx *ctx = job->ctx;<br>
> +<br>
> + if (ctx)<br>
> + amdgpu_ctx_put(ctx);<br>
> <br>
> fence_put(job->fence);<br>
> amdgpu_sync_free(&job->sync);<br>
> diff --git
a/drivers/gpu/drm/amd/scheduler/gpu_scheduler.c<br>
> b/drivers/gpu/drm/amd/scheduler/gpu_scheduler.c<br>
> index 6f4e31f..9100ca8 100644<br>
> ---
a/drivers/gpu/drm/amd/scheduler/gpu_scheduler.c<br>
> +++
b/drivers/gpu/drm/amd/scheduler/gpu_scheduler.c<br>
> @@ -208,12 +208,6 @@ void
amd_sched_entity_fini(struct amd_gpu_scheduler *sched,<br>
> if
(!amd_sched_entity_is_initialized(sched, entity))<br>
> return;<br>
> <br>
> - /**<br>
> - * The client will not queue more IBs
during this fini, consume existing<br>
> - * queued IBs<br>
> - */<br>
> - wait_event(sched->job_scheduled,
amd_sched_entity_is_idle(entity));<br>
> -<br>
> amd_sched_rq_remove_entity(rq, entity);<br>
> kfifo_free(&entity->job_queue);<br>
> }<br>
> diff --git
a/drivers/gpu/drm/amd/scheduler/gpu_scheduler.h<br>
> b/drivers/gpu/drm/amd/scheduler/gpu_scheduler.h<br>
> index 8cb41d3..ccbbcb0 100644<br>
> ---
a/drivers/gpu/drm/amd/scheduler/gpu_scheduler.h<br>
> +++
b/drivers/gpu/drm/amd/scheduler/gpu_scheduler.h<br>
> @@ -49,6 +49,7 @@ struct amd_sched_entity {<br>
> <br>
> struct fence
*dependency;<br>
> struct fence_cb cb;<br>
> + bool *ptr_guilty;<br>
> };<br>
> <br>
> /**<br>
<br>
<br>
_______________________________________________<br>
amd-gfx mailing list<br>
<a moz-do-not-send="true"
href="mailto:amd-gfx@lists.freedesktop.org">amd-gfx@lists.freedesktop.org</a><br>
<a moz-do-not-send="true"
href="https://lists.freedesktop.org/mailman/listinfo/amd-gfx">https://lists.freedesktop.org/mailman/listinfo/amd-gfx</a><br>
_______________________________________________<br>
amd-gfx mailing list<br>
<a moz-do-not-send="true"
href="mailto:amd-gfx@lists.freedesktop.org">amd-gfx@lists.freedesktop.org</a><br>
<a moz-do-not-send="true"
href="https://lists.freedesktop.org/mailman/listinfo/amd-gfx">https://lists.freedesktop.org/mailman/listinfo/amd-gfx</a><o:p></o:p></span></p>
</div>
</blockquote>
<p class="MsoNormal"><o:p> </o:p></p>
</blockquote>
<p><o:p> </o:p></p>
</div>
</blockquote>
<p><br>
</p>
</body>
</html>