[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH for-4.13] docs/xl: Document pci-assignable state
> -----Original Message----- > From: Ian Jackson <ian.jackson@xxxxxxxxxx> > Sent: 26 November 2019 15:06 > To: George Dunlap <george.dunlap@xxxxxxxxxx>; xen- > devel@xxxxxxxxxxxxxxxxxxxx; Wei Liu <wl@xxxxxxx>; Jan Beulich > <jbeulich@xxxxxxxx>; Durrant, Paul <pdurrant@xxxxxxxxxx>; Juergen Gross > <jgross@xxxxxxxx> > Subject: Re: [PATCH for-4.13] docs/xl: Document pci-assignable state > > Ian Jackson writes ("Re: [PATCH for-4.13] docs/xl: Document pci-assignable > state"): > > George Dunlap writes ("Re: [PATCH for-4.13] docs/xl: Document pci- > assignable state"): > > > I kind of feel like the discussion of the security risks inherent in > pci > > > passthrough belong in a separate document, but perhaps a brief mention > > > here would be helpful. Perhaps the following? > > > > > > "As always, this should only be done if you trust the guest, or are > > > confident that the particular device you're re-assigning to dom0 will > > > cancel all in-flight DMA on FLR." > > > > SGTM. > > > > I like "as always" which clearly signals that this is a more general > > problem without requiring us to actually write that other > > comprehensive document... > The text sounds fine in general but the 'as always' does rather imply 'hey, we never said PCI pass-through was safe, did we?' Paul _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |