[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RFC PATCH v1 0/9] Hypervisor-Enforced Kernel Integrity
|
From: |
Sean Christopherson |
|
Subject: |
Re: [RFC PATCH v1 0/9] Hypervisor-Enforced Kernel Integrity |
|
Date: |
Thu, 25 May 2023 09:07:00 -0700 |
On Thu, May 25, 2023, Rick P Edgecombe wrote:
> I wonder if it might be a good idea to POC the guest side before
> settling on the KVM interface. Then you can also look at the whole
> thing and judge how much usage it would get for the different options
> of restrictions.
As I said earlier[*], IMO the control plane logic needs to live in host
userspace.
I think any attempt to have KVM providen anything but the low level plumbing
will
suffer the same fate as CR4 pinning and XO memory. Iterating on an imperfect
solution to incremently improve security is far, far easier to do in userspace,
and far more likely to get merged.
[*] ZFUyhPuhtMbYdJ76@google.com">https://lore.kernel.org/all/ZFUyhPuhtMbYdJ76@google.com
- [PATCH v1 9/9] virt: Add Heki KUnit tests, (continued)
- Re: [RFC PATCH v1 0/9] Hypervisor-Enforced Kernel Integrity, Edgecombe, Rick P, 2023/05/24
- Re: [RFC PATCH v1 0/9] Hypervisor-Enforced Kernel Integrity, Mickaël Salaün, 2023/05/26
- Re: [RFC PATCH v1 0/9] Hypervisor-Enforced Kernel Integrity, Edgecombe, Rick P, 2023/05/30
- Re: [RFC PATCH v1 0/9] Hypervisor-Enforced Kernel Integrity, Sean Christopherson, 2023/05/31
Re: [RFC PATCH v1 0/9] Hypervisor-Enforced Kernel Integrity, James Morris, 2023/05/26