ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Christian Brauner <christian.brauner@ubuntu.com>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] DRAFT Kernel Summit Track schedule
Date: Wed, 28 Aug 2019 21:23:08 +0200	[thread overview]
Message-ID: <20190828192307.yvf372vnnx7f4iib@wittgenstein> (raw)
In-Reply-To: <20190826212548.GA15967@mit.edu>

On Mon, Aug 26, 2019 at 05:25:48PM -0400, Theodore Ts'o wrote:
> This is a draft kernel summit track schedule.  Please let me know of
> any potential conflicts or schedule changes that you might like to
> make.

Hey Ted,

Could we grab a slot for
https://lists.linuxfoundation.org/pipermail/ksummit-discuss/2019-July/006699.html
please? It doesn't seem to appear in the list yet.

Thanks!
Christian

> 
> The Open Slots will be available for last minute scheduling requests,
> unconference style.
> 
> Thanks!
> 
> 					- 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

  reply	other threads:[~2019-08-28 19:23 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 [this message]
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
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=20190828192307.yvf372vnnx7f4iib@wittgenstein \
    --to=christian.brauner@ubuntu.com \
    --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).