From: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
To: Jeffrey Hugo <quic_jhugo@quicinc.com>,
Tomeu Vizoso <tomeu@tomeuvizoso.net>,
open list <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
David Airlie <airlied@gmail.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Christian Gmeiner <christian.gmeiner@gmail.com>,
Oded Gabbay <ogabbay@kernel.org>, Olof Johansson <olof@lixom.net>,
Lucas Stach <l.stach@pengutronix.de>
Subject: Re: DRM Accel BoF at Linux Plumbers
Date: Thu, 23 May 2024 08:35:56 +0200 [thread overview]
Message-ID: <b19b95ca-c235-4738-a586-bfd1a36183dc@linux.intel.com> (raw)
In-Reply-To: <e22ffdea-3c18-3a23-e526-25809e98fcd9@quicinc.com>
Hi,
On 21.05.2024 17:10, Jeffrey Hugo wrote:
> On 5/21/2024 8:41 AM, Tomeu Vizoso wrote:
>> On Tue, May 21, 2024 at 2:12 PM Daniel Vetter <daniel@ffwll.ch> wrote:
>>>
>>> On Sat, May 18, 2024 at 10:46:01AM +0200, Tomeu Vizoso wrote:
>>>> Hi,
>>>>
>>>> I would like to use the chance at the next Plumbers to discuss the
>>>> present challenges related to ML accelerators in mainline.
>>>>
>>>> I'm myself more oriented towards edge-oriented deployments, and don't
>>>> know enough about how these accelerators are being used in the cloud
>>>> (and maybe desktop?) to tell if there is enough overlap to warrant a
>>>> common BoF.
>>>>
>>>> In any case, these are the topics I would like to discuss, some
>>>> probably more relevant to the edge than to the cloud or desktop:
>>>>
>>>> * What is stopping vendors from mainlining their drivers?
>>>>
>>>> * How could we make it easier for them?
>>>>
>>>> * Userspace API: how close are we from a common API that we can ask
>>>> userspace drivers to implement? What can be done to further this goal?
>>>>
>>>> * Automated testing: DRM CI can be used, but would be good to have a
>>>> common test suite to run there. This is probably dependent on a common
>>>> userspace API.
>>>>
>>>> * Other shared userspace infrastructure (compiler, execution,
>>>> synchronization, virtualization, ...)
>>>>
>>>> * Firmware-mediated IP: what should we do about it, if anything?
>>>>
>>>> * Any standing issues in DRM infra (GEM, gpu scheduler, DMABuf, etc)
>>>> that are hurting accel drivers?
>>>>
>>>> What do people think, should we have a drivers/accel-wide BoF at
>>>> Plumbers? If so, what other topics should we have in the agenda?
>>>
>>> Yeah sounds good, and I'll try to at least attend lpc this year since it's
>>> rather close ... Might be good to explicitly ping teams of merged and
>>> in-flight drivers we have in accel already.
>>
>> Sounds like a good idea to me. Will check if the people that sent the
>> previous aborted attempts are still interested in this
>
> Looks like the Intel VPU folks are missing from this thread.
Hi!
> I like the idea of a BoF. I suspect I will be remote but this list of topics looks good to me. Nothing obvious missing from what I can tell.
I like it too and I will try to attend. I would maybe add to the list GPU/accel interoperability.
Regards,
Jacek
next prev parent reply other threads:[~2024-05-23 6:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-18 8:46 DRM Accel BoF at Linux Plumbers Tomeu Vizoso
2024-05-20 11:49 ` Laurent Pinchart
2024-05-21 12:12 ` Daniel Vetter
2024-05-21 14:41 ` Tomeu Vizoso
2024-05-21 15:10 ` Jeffrey Hugo
2024-05-23 6:35 ` Jacek Lawrynowicz [this message]
2024-05-28 7:09 ` Tomeu Vizoso
2024-05-28 7:13 ` Tomeu Vizoso
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=b19b95ca-c235-4738-a586-bfd1a36183dc@linux.intel.com \
--to=jacek.lawrynowicz@linux.intel.com \
--cc=airlied@gmail.com \
--cc=christian.gmeiner@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=l.stach@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ogabbay@kernel.org \
--cc=olof@lixom.net \
--cc=p.zabel@pengutronix.de \
--cc=quic_jhugo@quicinc.com \
--cc=tomeu@tomeuvizoso.net \
/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