From: "Michael S. Tsirkin" <mst@redhat.com>
To: ksummit-discuss@lists.linuxfoundation.org
Cc: pbonzini@redhat.com
Subject: [Ksummit-discuss] late self-nomination
Date: Tue, 2 Aug 2016 20:23:26 +0300 [thread overview]
Message-ID: <20160802172326.GA25195@redhat.com> (raw)
Hi folks!
Likely too late, but oh well.
I would like to self-nominate for kernel summit this year.
I am the maintainer of the virtio subsystem, and within KVM, of the PC
and PCI subsystems. Intelnally within Red Hat I'm a tech lead for the
team handling the networking for VMs.
I would like to participate in self-hardening to see whether
hypervisor extensions (like e.g. kernel guard technology)
can benefit that project, in the memory model discussions
as virtio is a heavy user of memory barriers and could benefit
a lot e.g. from faster mb implementations. I would
also like to learn more about group maintainership
as we are seeing issues scaling co-maintainership with
our current structure with virtio.
Cheers,
--
MST
next reply other threads:[~2016-08-02 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 17:23 Michael S. Tsirkin [this message]
2016-08-02 17:28 ` Andy Lutomirski
2016-08-02 17:37 ` Michael S. Tsirkin
2016-08-02 19:00 ` Paolo Bonzini
2016-08-02 22:44 ` Michael S. Tsirkin
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=20160802172326.GA25195@redhat.com \
--to=mst@redhat.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=pbonzini@redhat.com \
/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