From: Sean Christopherson <seanjc@google.com>
To: James Morris <jamorris@linux.microsoft.com>
Cc: kvm@vger.kernel.org, pbonzini@redhat.com,
Thara Gopinath <tgopinath@linux.microsoft.com>,
mic@digikod.net
Subject: Re: 2024 HEKI discussion: LPC microconf / KVM Forum?
Date: Fri, 3 May 2024 16:35:25 -0700 [thread overview]
Message-ID: <ZjV0vXZJJ2_2p8gz@google.com> (raw)
In-Reply-To: <3564836-aa87-76d5-88d5-50269137f1@linux.microsoft.com>
On Wed, May 01, 2024, James Morris wrote:
> Hi Folks,
>
> We are planning our travel & conference submissions and I'm wondering if
> there is likely to be an LPC KVM microconf again this year.
There is, thanks for the reminder to send out an announcement[1]! :-)
> And if so, what would be the best option for proposing an update on the HEKI
> (hypervisor enforced kernel integrity) project?
>
> We'd like to demonstrate where we're at with the project and discuss next
> steps with the community, in terms of both core kernel changes and the
> KVM-specific project work.
Proposals/abstracts can be submitted via the web portal. Though to be perfectly
honest, for where HEKI is at from an upstream KVM perspective, and especially if
you want to provide an update, then I think KVM Forum[2] would be a better fit.
(I haven't seen an official announcment/CFP for KVM Forum, but the web site is
live, so I assume it's a done deal).
The most contentious aspects of HEKI are the guest changes, not the KVM changes.
The KVM uAPI and guest ABI will require some discussion, but I don't anticipate
those being truly hard problems to solve. And if you really want to get HEKI
moving, I would advise you not wait until September to hash out the KVM side of
things, e.g. I'd be more than happy to talk about HEKI in a PUCK[3] session.
[1] https://lore.kernel.org/all/20240503231845.1287764-1-seanjc@google.com
[2] https://kvm-forum.qemu.org
[3] https://lore.kernel.org/all/20230512231026.799267-1-seanjc@google.com
next prev parent reply other threads:[~2024-05-03 23:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 17:30 2024 HEKI discussion: LPC microconf / KVM Forum? James Morris
2024-05-03 23:35 ` Sean Christopherson [this message]
2024-05-04 1:10 ` Paolo Bonzini
2024-05-06 18:26 ` Mickaël Salaün
2024-05-07 0:02 ` Sean Christopherson
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=ZjV0vXZJJ2_2p8gz@google.com \
--to=seanjc@google.com \
--cc=jamorris@linux.microsoft.com \
--cc=kvm@vger.kernel.org \
--cc=mic@digikod.net \
--cc=pbonzini@redhat.com \
--cc=tgopinath@linux.microsoft.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).