ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Alex Levin <levinale@google.com>
To: ksummit@lists.linux.dev
Cc: Jesse Barnes <jsbarnes@google.com>
Subject: kSummit proposal - The Linux kernel in ChromeOS
Date: Mon, 23 Aug 2021 18:05:50 -0700	[thread overview]
Message-ID: <CAEeCyJZas4LCnMWYTo9Wh49N9DoBChzG869x41BpUoZ+1JmCGQ@mail.gmail.com> (raw)

Hi Linux friends,

Jesse Barnes, Chrome OS baseOS (Firmware+Kernel) lead, and myself
would like to present the current state of affairs of the Linux kernel
on ChromeOS and the challenges we face, how we solve them and get your
feedback.  We can also talk about how our efforts can help upstream
development, for example by running experiments in the field to
compare approaches to a specific problem or area.

Shipping ChromeOS to millions of users that span across hundreds of
different platforms, multiple active kernel versions and across many
different SoC architectures, introduces interesting challenges:

- Testing the upstream RC on as many platforms as we can as early as we can.
- Updating the Linux kernel on existing platforms (millions of users at a time).
- Managing technical “debt” and keeping the ChromeOS kernel as close
as possible to the upstream kernel.
- Current pain points in dealing with upstream.

We feel 45-60 minutes would be enough and will allow a discussion.

Thanks a lot in advance,

Alex Levin,
ChromeOS platform tech lead.

             reply	other threads:[~2021-08-24  1:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-24  1:05 Alex Levin [this message]
2021-08-26 22:07 ` kSummit proposal - The Linux kernel in ChromeOS Linus Walleij
2021-08-26 22:27   ` Laurent Pinchart
2021-08-27  1:01     ` Alex Levin
2021-08-27 20:22       ` Linus Walleij
2021-08-30 17:25         ` Jonathan Cameron
2021-08-30 15:19       ` Theodore Ts'o
2021-08-30 19:33       ` Theodore Ts'o
     [not found]         ` <CAMJEoco4eHw6A04nBBtnCMOMW7HsE16uKMsNy02hRP1vt1C-AA@mail.gmail.com>
2021-08-30 20:49           ` Davidlohr Bueso
2021-08-30 21:05             ` Daniel Jordan
2021-08-31 19:21               ` Pavel Tatashin
2021-08-27 13:50     ` Serge E. Hallyn

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=CAEeCyJZas4LCnMWYTo9Wh49N9DoBChzG869x41BpUoZ+1JmCGQ@mail.gmail.com \
    --to=levinale@google.com \
    --cc=jsbarnes@google.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 NNTP newsgroup(s).