From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API Date: Wed, 03 Sep 2014 18:05:36 +1000 Message-ID: <1409731536.30640.95.camel@pasglop> References: <1409609814.30640.11.camel@pasglop> <1409691213.30640.37.camel@pasglop> <1409695810.30640.57.camel@pasglop> <1409700010.30640.67.camel@pasglop> <1409703942.30640.71.camel@pasglop> <5406C77B.1000809@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5406C77B.1000809@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.linux-foundation.org Errors-To: virtualization-bounces@lists.linux-foundation.org List-Archive: List-Post: To: Paolo Bonzini Cc: "linux-s390@vger.kernel.org" , Konrad Rzeszutek Wilk , "Michael S. Tsirkin" , Andy Lutomirski , Christian Borntraeger , "linux390@de.ibm.com" , Linux Virtualization List-ID: On Wed, 2014-09-03 at 09:47 +0200, Paolo Bonzini wrote: > > IOMMU support for x86 is going to go in this week. But won't that break virtio on x86 ? Or will virtio continue bypassing it ? IE, the guest side virtio doesn't expect an IOMMU and doesn't call the dma mappings ops. > However, it is and likely will remain niche enough that I don't really > care about performance loss from IOMMU support. If you enable it, you > want it. > > So from the QEMU point of view we can simply add the direct-ram-access > property, and have the pseries machine turn it on by default (while > other machines can leave it off by default---they have no IOMMU and > thus no performance cost). Well, it's only for virtio and should be on by default on x86 as well if an iommu is installed no ? Cheers, Ben.