Michael S. Tsirkin
2021-Oct-02 11:04 UTC
[PATCH v2 4/6] virtio: Initialize authorized attribute for confidential guest
On Fri, Oct 01, 2021 at 08:49:28AM -0700, Andi Kleen wrote:> > Do you have a list of specific drivers and kernel options that you > > feel you now "trust"? > > For TDX it's currently only virtio net/block/console > > But we expect this list to grow slightly over time, but not at a high rate > (so hopefully <10)Well there are already >10 virtio drivers and I think it's reasonable that all of these will be used with encrypted guests. The list will grow. -- MST
Greg Kroah-Hartman
2021-Oct-02 11:14 UTC
[PATCH v2 4/6] virtio: Initialize authorized attribute for confidential guest
On Sat, Oct 02, 2021 at 07:04:28AM -0400, Michael S. Tsirkin wrote:> On Fri, Oct 01, 2021 at 08:49:28AM -0700, Andi Kleen wrote: > > > Do you have a list of specific drivers and kernel options that you > > > feel you now "trust"? > > > > For TDX it's currently only virtio net/block/console > > > > But we expect this list to grow slightly over time, but not at a high rate > > (so hopefully <10) > > Well there are already >10 virtio drivers and I think it's reasonable > that all of these will be used with encrypted guests. The list will > grow.What is keeping "all" drivers from being on this list? How exactly are you determining what should, and should not, be allowed? How can drivers move on, or off, of it over time? And why not just put all of that into userspace and have it pick and choose? That should be the end-goal here, you don't want to encode policy like this in the kernel, right? thanks, greg k-h