From: Steven Price <steven.price@arm.com>
To: Daniel Almeida <daniel.almeida@collabora.com>
Cc: "Rob Herring" <robh@kernel.org>,
"Boris Brezillon" <boris.brezillon@collabora.com>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Danilo Krummrich" <dakr@redhat.com>,
"Lyude Paul" <lyude@redhat.com>,
"Asahi Lina" <lina@asahilina.net>,
"Maíra Canal" <mcanal@igalia.com>,
"David Airlie" <airlied@gmail.com>,
rust-for-linux@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] drm: panthor: add dev_coredumpv support
Date: Wed, 24 Jul 2024 15:35:39 +0100 [thread overview]
Message-ID: <bba61792-a098-4ce0-81c4-e73b7dda3b79@arm.com> (raw)
In-Reply-To: <1CF0978E-344C-4EC9-A221-4F19EBA4B988@collabora.com>
On 24/07/2024 15:27, Daniel Almeida wrote:
> Hi Steven!
>
>> On 24 Jul 2024, at 10:54, Steven Price <steven.price@arm.com> wrote:
>>
>> [1] Although I have to admit for a debugging feature like devcoredump
>> there might well be pressure to implement this in C as well purely so
>> that customer issues can be debugged…
>
> FYI: I picked devcoredump because it was self-contained enough that I
> could make a proof-of-concept and get the discussion started. I think
> that, at least from this point of view, it has been successful, even if we
> decide against a partial Rust driver! :)
Indeed, thanks for posting this! It's provoked a good discussion.
> I was informed early on that delaying a debugging feature until the
> abstractions were merged would be a problem. Don’t worry: I can rewrite
> the kernel part in C, that would indeed be a very small patch.
I'll leave that for you to decide. There's definitely nothing blocking a
patch like this in C, but equally I'm not aware of anyone desperate for
this support yet.
Thanks,
Steve
next prev parent reply other threads:[~2024-07-24 14:35 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 22:50 [RFC PATCH] drm: panthor: add dev_coredumpv support Daniel Almeida
2024-07-11 0:01 ` Danilo Krummrich
2024-07-15 9:03 ` Daniel Vetter
2024-07-15 17:05 ` Daniel Almeida
2024-07-16 9:25 ` Daniel Vetter
2024-07-25 19:35 ` Lyude Paul
2024-07-26 13:40 ` Daniel Vetter
2024-07-29 18:34 ` Lyude Paul
2024-07-30 8:29 ` Daniel Vetter
2024-07-11 16:57 ` Liviu Dudau
2024-07-11 18:40 ` Daniel Almeida
2024-07-12 9:46 ` Steven Price
2024-07-12 14:35 ` Daniel Almeida
2024-07-12 14:53 ` Danilo Krummrich
2024-07-12 15:13 ` Daniel Almeida
2024-07-12 15:32 ` Danilo Krummrich
2024-07-13 0:48 ` Dave Airlie
2024-07-13 1:00 ` Daniel Almeida
2024-07-13 8:17 ` Miguel Ojeda
2024-07-15 9:12 ` Steven Price
2024-07-23 9:44 ` Alice Ryhl
2024-07-23 16:06 ` Boris Brezillon
2024-07-23 17:23 ` Daniel Almeida
2024-07-24 8:59 ` Steven Price
2024-07-24 10:44 ` Boris Brezillon
2024-07-24 12:37 ` Steven Price
2024-07-24 13:15 ` Rob Herring
2024-07-24 13:54 ` Steven Price
2024-07-24 14:27 ` Daniel Almeida
2024-07-24 14:35 ` Steven Price [this message]
2024-07-24 14:38 ` Miguel Ojeda
2024-07-25 11:42 ` Carsten Haitzler
2024-07-25 11:45 ` Carsten Haitzler
2024-07-23 9:53 ` Alice Ryhl
2024-07-23 13:41 ` Daniel Almeida
2024-07-23 13:45 ` Alice Ryhl
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=bba61792-a098-4ce0-81c4-e73b7dda3b79@arm.com \
--to=steven.price@arm.com \
--cc=airlied@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=dakr@redhat.com \
--cc=daniel.almeida@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=lina@asahilina.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=mcanal@igalia.com \
--cc=ojeda@kernel.org \
--cc=robh@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=wedsonaf@gmail.com \
/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).