[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <D1B4HKJAJG21.2DH9F3E1Q6J9L@amazon.com>
Date: Thu, 16 May 2024 14:02:09 +0000
From: Nicolas Saenz Julienne <nsaenz@...zon.com>
To: Mickaël Salaün <mic@...ikod.net>
CC: Sean Christopherson <seanjc@...gle.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>, "H . Peter Anvin" <hpa@...or.com>,
Ingo Molnar <mingo@...hat.com>, Kees Cook <keescook@...omium.org>, "Paolo
Bonzini" <pbonzini@...hat.com>, Thomas Gleixner <tglx@...utronix.de>, "Vitaly
Kuznetsov" <vkuznets@...hat.com>, Wanpeng Li <wanpengli@...cent.com>, "Rick P
Edgecombe" <rick.p.edgecombe@...el.com>, Alexander Graf <graf@...zon.com>,
Angelina Vu <angelinavu@...ux.microsoft.com>, Anna Trikalinou
<atrikalinou@...rosoft.com>, Chao Peng <chao.p.peng@...ux.intel.com>,
"Forrest Yuan Yu" <yuanyu@...gle.com>, James Gowans <jgowans@...zon.com>,
James Morris <jamorris@...ux.microsoft.com>, John Andersen
<john.s.andersen@...el.com>, "Madhavan T . Venkataraman"
<madvenka@...ux.microsoft.com>, Marian Rotariu <marian.c.rotariu@...il.com>,
Mihai Donțu <mdontu@...defender.com>,
Nicușor Cîțu <nicu.citu@...oud.com>, Thara
Gopinath <tgopinath@...rosoft.com>, "Trilok Soni" <quic_tsoni@...cinc.com>,
Wei Liu <wei.liu@...nel.org>, Will Deacon <will@...nel.org>, Yu Zhang
<yu.c.zhang@...ux.intel.com>, Ștefan Șicleru
<ssicleru@...defender.com>, <dev@...ts.cloudhypervisor.org>,
<kvm@...r.kernel.org>, <linux-hardening@...r.kernel.org>,
<linux-hyperv@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-security-module@...r.kernel.org>, <qemu-devel@...gnu.org>,
<virtualization@...ts.linux-foundation.org>, <x86@...nel.org>,
<xen-devel@...ts.xenproject.org>
Subject: Re: [RFC PATCH v3 3/5] KVM: x86: Add notifications for Heki policy
configuration and violation
On Tue May 14, 2024 at 12:23 PM UTC, Mickaël Salaün wrote:
> > Development happens
> > https://github.com/vianpl/{linux,qemu,kvm-unit-tests} and the vsm-next
> > branch, but I'd advice against looking into it until we add some order
> > to the rework. Regardless, feel free to get in touch.
>
> Thanks for the update.
>
> Could we schedule a PUCK meeting to synchronize and help each other?
> What about June 12?
Sounds great! June 12th works for me.
Nicolas
Powered by blists - more mailing lists