From: Sean Christopherson <seanjc@google.com>
To: "Mickaël Salaün" <mic@digikod.net>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
James Morris <jamorris@linux.microsoft.com>,
kvm@vger.kernel.org,
Thara Gopinath <tgopinath@linux.microsoft.com>,
"Madhavan T. Venkataraman" <madvenka@linux.microsoft.com>
Subject: Re: 2024 HEKI discussion: LPC microconf / KVM Forum?
Date: Mon, 6 May 2024 17:02:34 -0700 [thread overview]
Message-ID: <Zjlvmkw8gvOgH-ss@google.com> (raw)
In-Reply-To: <20240506.eBegohcheM0a@digikod.net>
On Mon, May 06, 2024, Mickaël Salaün wrote:
> On Sat, May 04, 2024 at 03:10:33AM GMT, Paolo Bonzini wrote:
> >
> >
> > Il 4 maggio 2024 01:35:25 CEST, Sean Christopherson <seanjc@google.com> ha scritto:
> > >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.
> >
> > I am not sure I agree... The problem with HEKI as of last November was that
> > it's not clear what it protects against. What's the attack and how it's
> > prevented.
Hmm, I'm probably getting my streams crossed and/or misremembering entirely.
prev parent reply other threads:[~2024-05-07 0:02 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
2024-05-04 1:10 ` Paolo Bonzini
2024-05-06 18:26 ` Mickaël Salaün
2024-05-07 0:02 ` Sean Christopherson [this message]
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=Zjlvmkw8gvOgH-ss@google.com \
--to=seanjc@google.com \
--cc=jamorris@linux.microsoft.com \
--cc=kvm@vger.kernel.org \
--cc=madvenka@linux.microsoft.com \
--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).