From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] DRAFT Kernel Summit Track schedule
Date: Sun, 1 Sep 2019 10:09:30 +0200 [thread overview]
Message-ID: <CAKMK7uEuqMMeZn-bSHoih3FKEspiGmibN=5KAgZtAiAj2Tw-Tw@mail.gmail.com> (raw)
In-Reply-To: <20190830034906.GA5670@mit.edu>
On Fri, Aug 30, 2019 at 5:49 AM Theodore Y. Ts'o <tytso@mit.edu> wrote:
>
> On Thu, Aug 29, 2019 at 06:13:57AM +1000, Dave Airlie wrote:
> >
> > Not sure who is giving the Monday graphics talk at 12:00 could I ask
> > you to push this a bit later. I'm unfortunately arriving in Lisbon on
> > Monday morning and I should be at the venue by 12:00 but it would be
> > good to guarantee I can attend.
>
> It's Daniel Vetter. The full kernel summit agenda on-line can be
> found at:
>
> https://linuxplumbersconf.org/event/4/sessions/40/#all
>
> Hmm... one possibility might be to swap it with the Maple Tree talk at
> 15:00. Let's see if Daniel and Liam are OK with this.
Fine with me, actually a bit better since then it doesn't clash with
the distro kernel MC.
-Daniel
>
> - Ted
>
>
>
> > >
> > > Monday September 9, 2019
> > >
> > > AM MC's: Dist Kernels, Tracing MC, RISC-V
> > > PM MC's PM: IoT, Scheduler, IOMMU
> > >
> > > 10:00 Reworking of KVA allocator in Linux kernel
> > > 10:45 Touch but don’t look: Running the kernel in execute only memory
> > > 11:30 Break
> > > 12:00 Upstream Graphics: Too little, too late
> > > 12:45 The list is our process: An analysis of the kernel's email-based development process
> > > 13:30 Lunch
> > > 15:00 Maple Tree
> > > 15:45 <Open slot>
> > > 16:30 Break
> > > 17:00 Inline Encryption Support
> > > 17:45 <Open Slot>
> > > 18:30 TAB Elections
> > > 19:45 LPC Evening Event
> > >
> > >
> > > Tuesday September 10, 2019
> > >
> > > AM MC's: Open Printing, Toolchains, Testing and Fuzzing
> > > PM MC's: Containers, Android, Power managemnt
> > >
> > > 10:00 Memory management bits in arch/*
> > > 10:45 replacing mmap_sem with finer grained locks
> > > 11:30 Break
> > > 12:00 Killing the mmap_sem's contention
> > > 12:45 <Open Slot>
> > > 13:30 Lunch
> > > 15:00 Tracing Data Access Pattern with Bounded Overhead and Best-effort Accuracy
> > > 15:45 Interrupt Message Store: A scalable interrupt mechanism for the cloud
> > > 16:30 Break
> > > 17:00 Kernel Documentation
> > > 17:45 <Open Slot>
> > >
> > > Wednesday, September 11, 2019
> > >
> > > AM MC's: RDMA, Real Time, Databases
> > > PM MC's: Live patching, BPF, System boot/security
> > >
> > > 10:00 Moving the Linux ABI to userspace
> > > 10:45 KUnit - Unit Testing for the Linux Kernel
> > > 11:30 Break
> > > 12:00 Reflections on kernel quality, development process and testing
> > > 12:45 <Open Slot>
> > > 13:30 Lunch
> > > 15:00 Decoupling ZRAM from a specific backend
> > > 15:45 <Open Slot>
> > > 16:30 <Break>
> > > 17:00 <Open Slot>
> > > 17:45 <Room not available -- reconfiguration for Plenary>
> > > 18:30 Closing Plenary
> > > 20:00 LPC Closing Party
> > > _______________________________________________
> > > Ksummit-discuss mailing list
> > > Ksummit-discuss@lists.linuxfoundation.org
> > > https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2019-09-01 8:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 21:25 [Ksummit-discuss] DRAFT Kernel Summit Track schedule Theodore Y. Ts'o
2019-08-28 19:23 ` Christian Brauner
2019-08-30 3:51 ` Theodore Y. Ts'o
2019-08-30 5:53 ` Kees Cook
2019-09-05 0:12 ` Theodore Y. Ts'o
2019-09-05 19:47 ` Kees Cook
2019-08-28 20:13 ` Dave Airlie
2019-08-30 3:49 ` Theodore Y. Ts'o
2019-09-01 8:09 ` Daniel Vetter [this message]
2019-08-28 20:29 ` Shuah Khan
2019-08-30 3:54 ` Theodore Y. Ts'o
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='CAKMK7uEuqMMeZn-bSHoih3FKEspiGmibN=5KAgZtAiAj2Tw-Tw@mail.gmail.com' \
--to=daniel.vetter@ffwll.ch \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=tytso@mit.edu \
/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).