Skip to contentSkip to conversation

Draft agenda for the kernel summit

Ksummit-discuss Theodore Ts'o 2 participants 4 messages Aug 11, 2014 – Aug 16, 2014 1 message not in the archive

lore
Share & tools
lore
#0 lore raw

Hi,

Enclosed please find the draft agenda for the kernel summit next week. Some of the talks haven't been confirmed yet, and there is still one, maybe two TBD slots.

If you have any thoughts or comments about topics that you think that we should absolutely cover, either from discussions on the ksummit-discuss list (Paul McKenney put together a very nice summary here
https://www.kernel.org/pub/linux/kernel/people/paulmck/LKS/LKS2014Topics.html)
or which have come up more recently, please make any suggestions here on this e-mail thread.

I'm also looking for feedback about whether there is anything left but tattered horse hide from the "encouraging more reviewers" discussion. As a program committee member observed to me privately, the problem is still real, but it's not clear how much more we would get out of having a face to face discussion that wasn't covered in the e-mail.

Thanks,

- Ted

Kernel Summit Agenda
August 18-20, 2014
DRAFT

Sunday
======

VIP Reception:
Buses Leave at 6:15pm from the hotel
Dinner at 6:30pm, at Bellwether (302 E. Illinois St, walking distance)

Monday (core day)
======

8:00 - Breakfast
9:00 - Welcome, Agenda Bashing
9:30 - IOMMU's and device drivers: error handling / reporting / isolation (David Woodhouse)
10:00 - Stable trees/workflow (Li Zefan, Greg K-H)
10:30 - Break
11:00 - Linux-next tree (Stephen Rothwell)
11:30 - Kernel tinification: shrinking the kernel and avoiding size
regressions (Josh Triplett)

12:00   - What makes Linus happy/unhappy regarding kernel development?
12:30   - Lunch
1:30    - Application Performance Regressions (Chris Mason)
2:00    - Kselftest
2:30    - Lightning Talks
3:00    - Break
3:30    - Reviewing new API/ABI (Andy Lutomirski, Michael Kerrisk)
4:00    - Encouraging more reviewers (*** anything left besides

badly flogged horseskin?)
4:30 - TBD
5:00 - Kernel Summit Core Day -- What went well, what can we do better?
(Theodore Ts'o)
5:45pm - Group Photograph (for core day attendees) 6:00pm - Dinner

Dinner at 6:00pm, Howell and Hood (435 North Michigan, walking distance)

Tuesday
=======

Workshops and Breakout sessions

Wireless: http://goo.gl/btbKL6
Networking: http://goo.gl/Uyp4jL
Energy Aware Scheduling: http://goo.gl/rksyCj
Unconference track: http://goo.gl/xmeoSd

Possible unconference topics culled from discuss list

* Driver model/resources, ACPI/DT, etc. sigh
* PM dependencies
* Metadata addendum to git commit
* printk softlockups

8:00    - Breakfast
10:30   - Break
12:30   - Lunch
3:00    - Break
4:45    - Group photograph
5:00    - LCNA First Timers Reception (all kernel developers are

cordially invited)

Wednesday (open day / technical sessions)
=========

9:00    - LCNA Keynote: State of Linux (Jim Zemlin)
9:45    - LCNA Keynote: Linux kernel panel
10:30   - Break
11:15	- Common trends and bug patterns from static tools (Dave Jones,
		Dan Carpenter, Julia Lawall)
12:15   - Introduction to Smatch / Coccenille (Dan Carpenter / Julia Lawall)
1:05    - Lunch
2:30    - 2 factor authentication, Kernel.org update/discussion (Konstantin Ryabitsev)
3:30	- Runtime kernel checking: kmemleak, minimal lockdep, and others
	  	  (Caitlin Marinas, Li Zefan)
4:20    - Break
4:50    - Workshop report-outs (networking, wireless, energy-aware scheduling)
6:05    - Program end
6:30    - Buses depart for Evening Event

Dinner event (shared with LinuxConf NA)
Museum of Science and Industry, 7:00pm to 10:00pm

A message that is not in the archive (sent off-list or not yet received): alpine.DEB.2.10.1408152014100.2503@hadrien

#2 lore raw
Quoted 7 lines · Julia Lawall
Quoted 3 lines

VIP Reception:
Buses Leave at 6:15pm from the hotel
Dinner at 6:30pm, at Bellwether (302 E. Illinois St, walking distance)

I'm not sure to understand this. It looks like one block on the map. Have I misunderstood something? The conference hotel is the one at 301 E North Water St, Chicago, IL 60611?

Sorry, that's my mistake. There is no bus, since the conference hotel is the one at 301 E. North Water St, and it's only a 3 minute walk to the restaurant:

https://www.google.com/maps/dir/Sheraton+Chicago+Hotel+and+Towers,+301+E+North+Water+St,+Chicago,+IL+60611/Bellwether+Meeting+House+%26+Eatery,+302+E+Illinois+St,+Chicago,+IL+60611/@41.8904195,-87.6198161,17z/am=t/data=!3m1!4b1!4m16!4m15!1m5!1m1!1s0x880e2ca9ef45c823:0xba6bddb06ea558a1!2m2!1d-87.619314!2d41.889062!1m5!1m1!1s0x880e2caa3e3c6c55:0x9adfacec660b9a67!2m2!1d-87.619924!2d41.89113!2m1!6e4!3e2

I'll fix the agenda, thanks for pointing the bug!

- Ted

#3 lore raw
In reply to Theodore Ts'o

On Mon, 2014-08-11 at 18:45 -0400, Theodore Ts'o wrote:

OK, so my first time attending, hopefully this is the sort of feedback you're looking for Ted:

Quoted 5 lines

Unconference track: http://goo.gl/xmeoSd

Possible unconference topics culled from discuss list

* Driver model/resources, ACPI/DT, etc. sigh

We had a good initial discussion on this. Since then, the ACPI 5.1 specification has been published, including the addition of the Device Specific Properties mechanism (_DSD). An initial patch series in support of this and the device_properties abstraction should hit the lists prior (just barely) to kernel summit.

Beyond this specific patch series, there are some related SoC configuration and enabling topics which came up that we could cover:
kernel and userspace pinconf control and SSDT overlays, for example.

I would very much like to see a slot in the unconference to discuss this with the group. But failing that, perhaps this can serve as a starting point for a hallway conversation.

Thanks,

Darren Hart

#4 lore raw
Quoted 3 lines · Darren Vincent Hart

I would very much like to see a slot in the unconference to discuss this with the group. But failing that, perhaps this can serve as a starting point for a hallway conversation.

So the way to schedule a slot in the unconference track is to make a comment in the Google doc spreadsheet suggesting a time, and starting a thread on the ksummit-discuss list. :-)

If we start running low on slots we may need to apply some additional criteria such as seeing sufficient interest on the mailing list of people who would be interested in attending that session. Right now, though the criteria is fairly relaxed since we're not seeing a huge rush of people wanting to propose topics --- although I suspect there will be many more ideas for potential unconference sessions coming out of the woodwork by Monday, during the core day, if not before.

Cheers,

- Ted