Profile cover photo
Profile photo
Viller Hsiao
94 followers
94 followers
About
Posts

Post has shared content

Post has shared content
I had this same type of conversation with at least 3 different groups of kernel developers in person this week:
"That's something that we should just turn an intern loose on."

Unfortunately, I don't have an intern...

So, let's try an experiment.

Wanted: semi-newbie kernel developer to do basic kernel development tasks.
Requirements: Willing to be given a stackdump and a reproducer or other type of description and can produce a working kernel patch and submit it upstream to the correct maintainers and mailing lists.
Location: Anywhere in the world, you work from home.
Time needed: whatever you can put into it.
Pay: none, but I will buy you all the free drinks of your choice at any conference where we both end up at. Odds are you can get a conference presentation talk and trip out of this as well, but I can't guarantee that.
Duration: How ever long you want, ideally at least a few months to get the hang of things.

Application process: Email me with a short description of your kernel experience, why you would be great at this, and why you want to do it.
Application deadline: May 31, 2018

And yes, this sounds a lot like "Do it for the exposure!" type of plea. You are correct, that is what it really is, but the thing is that these are tasks that wouldn't really get done otherwise as no company is putting people on them. So it's for the betterment of Linux here, which is a shared good. Also, these are not things you can just throw over the wall on a simple "here is a list of tasks to do." They require some basic hand-holding by an experienced developer to review and complete, so work on my side is going to going to be required.

Comments are locked here, email please.
Add a comment...

Post has shared content
Add a comment...

Post has shared content
Happy belated birthday Ftrace. You are now 10 years old. Wow how you've grown.

https://marc.info/?l=linux-kernel&m=120262847415382&w=2
Add a comment...

Post has shared content
Linux Plumbers Conference Linux Kernel Memory Model Workshop approved and announced! https://linuxplumbersconf.org/2017/ocw/events/LPC2017/tracks/632

The topic is a tool that analyzes (small!) C code fragments for concurrency problems.
Add a comment...

Post has shared content

Post has shared content
#Linux #kernel 3.18 is maintained again: "[…] Wait, what? 3.18? Wasn't that kernel dead and forgotten and left to rot on the side of the road? Yes, it was, but unfortunately, there's a few million or so devices out there in the wild that still rely on this kernel. […] Because of this strange situation, and thanks to some vendors backing the effort[1], I'll keep 3.18-stable alive in a semi-active mode, doing releases every once in a while to keep it up to date and working well based on what is happening in other more well-maintained stable kernels (hint, use 4.4 or 4.9 or newer PLEASE, if your vendor refuses to do so, switch vendors, it's the only way they will learn...) I don't know how long I'll keep doing this, so if you care about 3.18, please contact me to let me know the expected lifespan of your device. […]" https://mail-archive.com/linux-kernel@vger.kernel.org/msg1378272.html
Photo
Add a comment...

Post has shared content
https://suchakra.wordpress.com/2017/03/31/analyzing-kvm-hypercalls-with-ebpf-tracing/ "[…] Abder steered one recent discussion towards internals of KVM and wanted to know the latency caused by a hypercall he was introducing for his experiments […]. His analysis usecase was quite specific – he wanted to trace the kvm_exit -> kvm_hypercall -> kvm_entry sequence to know the exact latency he was causing for a given duration. […] here is a small demo of eBPF/BCC script that allows us to hook onto the 3 aforementioned tracepoints in the Linux kernel and conditionally record the trace events […]"
Photo
Add a comment...

Post has shared content
Yet more evidence that the Linux-kernel RCU specification is not mathematical, but rather empirical: https://lwn.net/Articles/716148/
Add a comment...

Post has shared content
New term for project forks and vendor kernels: alternative upstream
Add a comment...
Wait while more posts are being loaded