From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Tomeu Vizoso <tomeu@tomeuvizoso.net>
Cc: 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>,
Jeffrey Hugo <quic_jhugo@quicinc.com>
Subject: Re: DRM Accel BoF at Linux Plumbers
Date: Mon, 20 May 2024 14:49:07 +0300 [thread overview]
Message-ID: <20240520114907.GA6275@pendragon.ideasonboard.com> (raw)
In-Reply-To: <CAAObsKAw174AhGaA13Hyw0ANW=TxJHpK10+OwQGNMVca85Urdg@mail.gmail.com>
Hi Tomeu,
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?
I'm interested in attending, even if so far I have limited involvement
in that area. Looking forward we're considering usage of ML accelerators
in libcamera for various purposes, so an open ecosystem will be crucial
for us.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2024-05-20 11:49 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 [this message]
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
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=20240520114907.GA6275@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.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