Re: [PATCH v3 0/3] virtio DMA API core stuff

Path	csiph.com!news.mixmin.net!eternal-september.org!feeder.eternal-september.org!aioe.org!bofh.it!news.nic.it!robomod
From	Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
Newsgroups	linux.kernel
Subject	Re: [PATCH v3 0/3] virtio DMA API core stuff
Date	Sun, 22 Nov 2015 14:10:01 +0100
Message-ID	<qxCyZ-4di-7@gated-at.bofh.it> (permalink)
References	<qoz7k-3cS-9@gated-at.bofh.it> <qozAo-3CV-63@gated-at.bofh.it> <qozK3-3GM-73@gated-at.bofh.it> <qozTK-3KE-51@gated-at.bofh.it> <qoA3o-3Pi-21@gated-at.bofh.it> <qoBC9-4V4-17@gated-at.bofh.it> <qoHRg-lq-9@gated-at.bofh.it> <qoRnA-6GK-9@gated-at.bofh.it> <qoY5J-2tW-27@gated-at.bofh.it> <qsvy9-7nD-15@gated-at.bofh.it> <qswNA-86y-21@gated-at.bofh.it>
X-Original-To	Joerg Roedel <jroedel@suse.de>, "Michael S. Tsirkin" <mst@redhat.com>
Dkim-Signature	v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=reply-to:subject:references:to:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=+I4c5v/g9aKZL9vPEy4xwlndh9mxqVFlwHD33R//GLc=; b=fNTNU25SE16T1MIPrQIHO0Cw4iLvqi9zEPcjFQe3/vB5yZZ+rfhRD3XGoAY5eKp0Co m2R/dBCN4sKiJq4ZQZkWFZcC9+gPRGMGukvA7nu6Dmfw7XYz9I0AFWHu01Km1AIU03Pm Zi+1eKR/lH0mok3GGBAx5ItY2hH3tdJj/ICMlHhuJHrqL5HqsCR3suH42DLyeusHKgIv VMVPNIcl7smYHMbT2fic4vZ4Kh31bTXkMGKZ+WU1n94Xo4QTMSQnioXsobQ/3kycMStY TYMETpWs4xm+v+IXTddRdAMEZxgsgwLaAksyfv1a/66ur7BLp5qyeBq4P92g58ZvDl03 Ol+Q==
X-Received	by 10.28.24.199 with SMTP id 190mr14043332wmy.101.1448197571821; Sun, 22 Nov 2015 05:06:11 -0800 (PST)
Reply-To	marcel@redhat.com
User-Agent	Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version	1.0
Content-Type	text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding	7bit
Sender	robomod@news.nic.it
List-ID	<linux-kernel.vger.kernel.org>
X-Mailing-List	linux-kernel@vger.kernel.org
Approved	robomod@news.nic.it
Lines	43
Organization	linux.* mail to news gateway
X-Original-Cc	linux-s390 <linux-s390@vger.kernel.org>, KVM <kvm@vger.kernel.org>, Benjamin Herrenschmidt <benh@kernel.crashing.org>, Sebastian Ott <sebott@linux.vnet.ibm.com>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, Andy Lutomirski <luto@amacapital.net>, Christian Borntraeger <borntraeger@de.ibm.com>, Andy Lutomirski <luto@kernel.org>, Paolo Bonzini <pbonzini@redhat.com>, Linux Virtualization <virtualization@lists.linux-foundation.org>, David Woodhouse <dwmw2@infradead.org>, Christoph Hellwig <hch@lst.de>, Martin Schwidefsky <schwidefsky@de.ibm.com>
X-Original-Date	Sun, 22 Nov 2015 15:06:08 +0200
X-Original-Message-ID	<5651BDC0.2040206@gmail.com>
X-Original-References	<1446039327.3405.216.camel@infradead.org> <20151028155105-mutt-send-email-mst@redhat.com> <1446041609.3405.228.camel@infradead.org> <20151028161424-mutt-send-email-mst@redhat.com> <1446042754.3405.237.camel@infradead.org> <20151028175136-mutt-send-email-mst@redhat.com> <CALCETrWd7mK5bW2p_dvvjDRnqE31=ueAz5SAYKwY-PD5uZp76A@mail.gmail.com> <20151029104301-mutt-send-email-mst@redhat.com> <1446135536.3405.279.camel@infradead.org> <20151108120627-mutt-send-email-mst@redhat.com> <20151108114946.GG2255@suse.de>
X-Original-Sender	linux-kernel-owner@vger.kernel.org
Xref	csiph.com linux.kernel:1274862

Show key headers only | View raw

On 11/08/2015 01:49 PM, Joerg Roedel wrote:
> On Sun, Nov 08, 2015 at 12:37:47PM +0200, Michael S. Tsirkin wrote:
>> I have no problem with that. For example, can we teach
>> the DMA API on intel x86 to use PT for virtio by default?
>> That would allow merging Andy's patches with
>> full compatibility with old guests and hosts.
>
> Well, the only incompatibility comes from an experimental qemu feature,
> more explicitly from a bug in that features implementation. So why
> should we work around that in the kernel? I think it is not too hard to
> fix qemu to generate a correct DMAR table which excludes the virtio
> devices from iommu translation.

Hi,

I tried to generate a DMAR table that excludes some devices from
IOMMU translation, however it does not help.

The reason is, as far as I understand, that Linux kernel does
not allow any device being outside an IOMMU scope if the
iommu kernel option is activated.

Does anybody know if it is "by design" or is simply an uncommon configuration?
(some devices in an IOMMU scope, while others outside *any* IOMMU scope)

Thanks,
Marcel

>
>
> 	Joerg
>
> _______________________________________________
> Virtualization mailing list
> Virtualization@lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/virtualization
>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Re: [PATCH v3 0/3] virtio DMA API core stuff Marcel Apfelbaum <marcel.apfelbaum@gmail.com> - 2015-11-22 14:10 +0100
  Re: [PATCH v3 0/3] virtio DMA API core stuff David Woodhouse <dwmw2@infradead.org> - 2015-11-22 17:00 +0100
    Re: [PATCH v3 0/3] virtio DMA API core stuff Marcel Apfelbaum <marcel@redhat.com> - 2015-11-22 18:10 +0100
    Re: [PATCH v3 0/3] virtio DMA API core stuff "Michael S. Tsirkin" <mst@redhat.com> - 2015-11-22 23:20 +0100

csiph-web