Build on top of Marcel's -device for IOMMUs patches, add a device property. Sorry, no reference at hand.
Jan Mit TouchDown von meinem Android-Telefon gesendet (www.symantec.com) -----Original Message----- From: Aviv B.D. [bd.a...@gmail.com] Received: Samstag, 28 Mai 2016, 18:12 To: Kiszka, Jan (CT RDA ITP SES-DE) [jan.kis...@siemens.com]; Jason Wang [jasow...@redhat.com]; qemu-devel@nongnu.org [qemu-devel@nongnu.org] CC: Alex Williamson [alex.william...@redhat.com]; Peter Xu [pet...@redhat.com]; Michael S. Tsirkin [m...@redhat.com] Subject: Re: [Qemu-devel] [PATCH v3 1/3] IOMMU: add VTD_CAP_CM to vIOMMU capability exposed to guest What is the best way to add this configuration option? Aviv. On Tue, May 24, 2016 at 12:25 PM Jan Kiszka <jan.kis...@siemens.com<mailto:jan.kis...@siemens.com>> wrote: On 2016-05-24 10:14, Jason Wang wrote: > On 2016年05月22日 00:19, Aviv B.D wrote: >> From: "Aviv Ben-David" <bd.a...@gmail.com<mailto:bd.a...@gmail.com>> >> >> This flag tells the guest to invalidate tlb cache also after unmap >> operations. >> >> Signed-off-by: Aviv Ben-David <bd.a...@gmail.com<mailto:bd.a...@gmail.com>> >> --- > > Is this a guest visible behavior? If yes, shouldn't we cache > translation fault conditions in IOTLB? It is guest visible, and this first of all means, besides requiring to be optional, that it definitely needs to be off for compat systems. Or it stays off by default. Jan -- Siemens AG, Corporate Technology, CT RDA ITP SES-DE Corporate Competence Center Embedded Linux
