From: "Herrenschmidt, Benjamin" <benh@amazon.com>
To: "bartosz.golaszewski@linaro.org" <bartosz.golaszewski@linaro.org>,
"greg@kroah.com" <greg@kroah.com>
Cc: "ksummit@lists.linux.dev" <ksummit@lists.linux.dev>
Subject: Re: [TECH TOPIC] Improving resource ownership and life-time in linux device drivers
Date: Tue, 15 Aug 2023 03:05:29 +0000 [thread overview]
Message-ID: <0ac319f6dfdc1f00f2b1e6007d6ef06f07884128.camel@amazon.com> (raw)
In-Reply-To: <2023081048-skittle-excusable-2c9f@gregkh>
On Thu, 2023-08-10 at 17:47 +0200, Greg KH wrote:
> >
.../...
> > I have since experimented with several approaches and would like to
> > present some updates on this subject. During this talk I plan to jump
> > straight into presenting concrete ideas and timelines for improving
> > the driver model and introducing some unification in the way
> > subsystems handle driver data. While this is a significant effort
> > spanning multiple device subsystems that will need to be carried out
> > in many phases over what will most likely be years, without addressing
> > the problems, we'll be left with many parts of the kernel not being
> > able to correctly handle simple driver unbinds.
>
> I'm all for this, we need some major work in this area.
I've lost track a bit of which summit is which as I'm operating further
away from the kernel than I'd like to these days, but this is
definitely something I would like to see presented to as wide an
audience as possible :)
Cheers,
Ben.
next prev parent reply other threads:[~2023-08-15 3:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 18:04 [TECH TOPIC] Improving resource ownership and life-time in linux device drivers Bartosz Golaszewski
2023-08-09 22:03 ` Linus Walleij
2023-08-09 23:53 ` SeongJae Park
2023-08-10 7:55 ` Bartosz Golaszewski
2023-08-10 15:47 ` Greg KH
2023-08-10 20:47 ` Laurent Pinchart
2023-08-14 9:27 ` Wolfram Sang
2023-08-15 3:05 ` Herrenschmidt, Benjamin [this message]
2023-08-10 19:07 ` Julia Lawall
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=0ac319f6dfdc1f00f2b1e6007d6ef06f07884128.camel@amazon.com \
--to=benh@amazon.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=greg@kroah.com \
--cc=ksummit@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).