[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RFC PATCH v3 3/5] KVM: x86: Add notifications for Heki policy configuration and violation
- To: Mickaël Salaün <mic@xxxxxxxxxxx>
- From: Nicolas Saenz Julienne <nsaenz@xxxxxxxxxx>
- Date: Thu, 16 May 2024 14:02:09 +0000
- Cc: Sean Christopherson <seanjc@xxxxxxxxxx>, Borislav Petkov <bp@xxxxxxxxx>, Dave Hansen <dave.hansen@xxxxxxxxxxxxxxx>, "H . Peter Anvin" <hpa@xxxxxxxxx>, Ingo Molnar <mingo@xxxxxxxxxx>, Kees Cook <keescook@xxxxxxxxxxxx>, "Paolo Bonzini" <pbonzini@xxxxxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, "Vitaly Kuznetsov" <vkuznets@xxxxxxxxxx>, Wanpeng Li <wanpengli@xxxxxxxxxxx>, "Rick P Edgecombe" <rick.p.edgecombe@xxxxxxxxx>, Alexander Graf <graf@xxxxxxxxxx>, Angelina Vu <angelinavu@xxxxxxxxxxxxxxxxxxx>, Anna Trikalinou <atrikalinou@xxxxxxxxxxxxx>, Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>, "Forrest Yuan Yu" <yuanyu@xxxxxxxxxx>, James Gowans <jgowans@xxxxxxxxxx>, James Morris <jamorris@xxxxxxxxxxxxxxxxxxx>, John Andersen <john.s.andersen@xxxxxxxxx>, "Madhavan T . Venkataraman" <madvenka@xxxxxxxxxxxxxxxxxxx>, Marian Rotariu <marian.c.rotariu@xxxxxxxxx>, Mihai Donțu <mdontu@xxxxxxxxxxxxxxx>, Nicușor Cîțu <nicu.citu@xxxxxxxxxx>, Thara Gopinath <tgopinath@xxxxxxxxxxxxx>, "Trilok Soni" <quic_tsoni@xxxxxxxxxxx>, Wei Liu <wei.liu@xxxxxxxxxx>, Will Deacon <will@xxxxxxxxxx>, Yu Zhang <yu.c.zhang@xxxxxxxxxxxxxxx>, Ștefan Șicleru <ssicleru@xxxxxxxxxxxxxxx>, <dev@xxxxxxxxxxxxxxxxxxxxxxxxx>, <kvm@xxxxxxxxxxxxxxx>, <linux-hardening@xxxxxxxxxxxxxxx>, <linux-hyperv@xxxxxxxxxxxxxxx>, <linux-kernel@xxxxxxxxxxxxxxx>, <linux-security-module@xxxxxxxxxxxxxxx>, <qemu-devel@xxxxxxxxxx>, <virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx>, <x86@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxxx>
- Delivery-date: Thu, 16 May 2024 14:02:38 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
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
|
