[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6ab2ff76-4518-6fac-071e-5d0d5adc4fcd@igalia.com>
Date: Mon, 1 May 2023 22:26:24 -0300
From: André Almeida <andrealmeid@...lia.com>
To: Alex Deucher <alexdeucher@...il.com>
Cc: dri-devel@...ts.freedesktop.org, amd-gfx@...ts.freedesktop.org,
linux-kernel@...r.kernel.org, pierre-eric.pelloux-prayer@....com,
Marek Olšák <maraeo@...il.com>,
Timur Kristóf <timur.kristof@...il.com>,
michel.daenzer@...lbox.org,
Samuel Pitoiset <samuel.pitoiset@...il.com>,
kernel-dev@...lia.com, Bas Nieuwenhuizen <bas@...nieuwenhuizen.nl>,
alexander.deucher@....com, christian.koenig@....com
Subject: Re: [RFC PATCH 0/1] Add AMDGPU_INFO_GUILTY_APP ioctl
Em 01/05/2023 16:24, Alex Deucher escreveu:
> On Mon, May 1, 2023 at 2:58 PM André Almeida <andrealmeid@...lia.com> wrote:
>>
>> I know that devcoredump is also used for this kind of information, but I believe
>> that using an IOCTL is better for interfacing Mesa + Linux rather than parsing
>> a file that its contents are subjected to be changed.
>
> Can you elaborate a bit on that? Isn't the whole point of devcoredump
> to store this sort of information?
>
I think that devcoredump is something that you could use to submit to a
bug report as it is, and then people can read/parse as they want, not as
an interface to be read by Mesa... I'm not sure that it's something that
I would call an API. But I might be wrong, if you know something that
uses that as an API please share.
Anyway, relying on that for Mesa would mean that we would need to ensure
stability for the file content and format, making it less flexible to
modify in the future and probe to bugs, while the IOCTL is well defined
and extensible. Maybe the dump from Mesa + devcoredump could be
complementary information to a bug report.
Powered by blists - more mailing lists