Messages in this thread | | | Date | Wed, 8 Feb 2023 08:00:05 -0500 | From | "Michael S. Tsirkin" <> | Subject | Re: Linux guest kernel threat model for Confidential Computing |
| |
On Wed, Feb 08, 2023 at 10:44:25AM +0000, Reshetova, Elena wrote: > Because for the > drivers that CoCo guest happens to need, there is no way to fix this problem by > either of these mechanisms (we cannot disable the code that we need), unless somebody > writes a totally new set of coco specific drivers (who needs another set of > CoCo specific virtio drivers in the kernel?).
I think it's more about pci and all that jazz, no? As a virtio maintainer I applied patches adding validation and intend to do so in the future simply because for virtio specifically people build all kind of weird setups out of software and so validating everything is a good idea.
-- MST
| |