From: James Morris <jamorris@linux.microsoft.com>
To: kvm@vger.kernel.org
Cc: pbonzini@redhat.com,
Thara Gopinath <tgopinath@linux.microsoft.com>,
mic@digikod.net
Subject: 2024 HEKI discussion: LPC microconf / KVM Forum?
Date: Wed, 1 May 2024 10:30:02 -0700 (PDT) [thread overview]
Message-ID: <3564836-aa87-76d5-88d5-50269137f1@linux.microsoft.com> (raw)
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. 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.
As a reference, here are the LPC sessions from 2023:
- KVM microconf: https://lpc.events/event/17/contributions/1486/
- Main track overview: https://lpc.events/event/17/contributions/1515/
--
James Morris
<jamorris@linux.microsoft.com>
next reply other threads:[~2024-05-01 17:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 17:30 James Morris [this message]
2024-05-03 23:35 ` 2024 HEKI discussion: LPC microconf / KVM Forum? Sean Christopherson
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=3564836-aa87-76d5-88d5-50269137f1@linux.microsoft.com \
--to=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).