From: "Michael S. Tsirkin" <mst@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org,
virtualization@lists.linux-foundation.org
Subject: [PATCH v2 0/2] vfio: blacklist legacy virtio devices
Date: Tue, 30 Aug 2016 05:27:07 +0300 [thread overview]
Message-ID: <1472523968-9540-1-git-send-email-mst@redhat.com> (raw)
Legacy virtio devices always bypassed an IOMMU, so using them with vfio was
never safe. This adds a quirk detecting these and disabling VFIO unless the
noiommu mode is used. At the moment, this only applies to virtio-pci devices.
The patch might make sense on stable as well.
Michael S. Tsirkin (2):
vfio: report group noiommu status
vfio: add virtio pci quirk
drivers/vfio/pci/vfio_pci_private.h | 1 +
include/linux/vfio.h | 2 +
drivers/vfio/pci/vfio_pci.c | 14 ++++
drivers/vfio/pci/vfio_pci_virtio.c | 140 ++++++++++++++++++++++++++++++++++++
drivers/vfio/vfio.c | 12 ++++
drivers/vfio/pci/Makefile | 1 +
6 files changed, 170 insertions(+)
create mode 100644 drivers/vfio/pci/vfio_pci_virtio.c
--
MST
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Jason Wang <jasowang@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
virtualization@lists.linux-foundation.org, qemu-devel@nongnu.org,
kvm@vger.kernel.org
Subject: [PATCH v2 0/2] vfio: blacklist legacy virtio devices
Date: Tue, 30 Aug 2016 05:27:07 +0300 [thread overview]
Message-ID: <1472523968-9540-1-git-send-email-mst@redhat.com> (raw)
Legacy virtio devices always bypassed an IOMMU, so using them with vfio was
never safe. This adds a quirk detecting these and disabling VFIO unless the
noiommu mode is used. At the moment, this only applies to virtio-pci devices.
The patch might make sense on stable as well.
Michael S. Tsirkin (2):
vfio: report group noiommu status
vfio: add virtio pci quirk
drivers/vfio/pci/vfio_pci_private.h | 1 +
include/linux/vfio.h | 2 +
drivers/vfio/pci/vfio_pci.c | 14 ++++
drivers/vfio/pci/vfio_pci_virtio.c | 140 ++++++++++++++++++++++++++++++++++++
drivers/vfio/vfio.c | 12 ++++
drivers/vfio/pci/Makefile | 1 +
6 files changed, 170 insertions(+)
create mode 100644 drivers/vfio/pci/vfio_pci_virtio.c
--
MST
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Jason Wang <jasowang@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
virtualization@lists.linux-foundation.org, qemu-devel@nongnu.org,
kvm@vger.kernel.org
Subject: [Qemu-devel] [PATCH v2 0/2] vfio: blacklist legacy virtio devices
Date: Tue, 30 Aug 2016 05:27:07 +0300 [thread overview]
Message-ID: <1472523968-9540-1-git-send-email-mst@redhat.com> (raw)
Legacy virtio devices always bypassed an IOMMU, so using them with vfio was
never safe. This adds a quirk detecting these and disabling VFIO unless the
noiommu mode is used. At the moment, this only applies to virtio-pci devices.
The patch might make sense on stable as well.
Michael S. Tsirkin (2):
vfio: report group noiommu status
vfio: add virtio pci quirk
drivers/vfio/pci/vfio_pci_private.h | 1 +
include/linux/vfio.h | 2 +
drivers/vfio/pci/vfio_pci.c | 14 ++++
drivers/vfio/pci/vfio_pci_virtio.c | 140 ++++++++++++++++++++++++++++++++++++
drivers/vfio/vfio.c | 12 ++++
drivers/vfio/pci/Makefile | 1 +
6 files changed, 170 insertions(+)
create mode 100644 drivers/vfio/pci/vfio_pci_virtio.c
--
MST
next reply other threads:[~2016-08-30 2:27 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 2:27 Michael S. Tsirkin [this message]
2016-08-30 2:27 ` [Qemu-devel] [PATCH v2 0/2] vfio: blacklist legacy virtio devices Michael S. Tsirkin
2016-08-30 2:27 ` Michael S. Tsirkin
2016-08-30 2:27 ` [PATCH v2 1/2] vfio: report group noiommu status Michael S. Tsirkin
2016-08-30 2:27 ` [Qemu-devel] " Michael S. Tsirkin
2016-08-30 2:27 ` Michael S. Tsirkin
2016-08-30 2:27 ` [PATCH v2 2/2] vfio: add virtio pci quirk Michael S. Tsirkin
2016-08-30 2:27 ` [Qemu-devel] " Michael S. Tsirkin
2016-08-30 2:27 ` Michael S. Tsirkin
2016-08-30 3:23 ` Alex Williamson
2016-08-30 3:23 ` [Qemu-devel] " Alex Williamson
2016-08-30 3:23 ` Alex Williamson
2016-08-30 3:48 ` Michael S. Tsirkin
2016-08-30 3:48 ` [Qemu-devel] " Michael S. Tsirkin
2016-08-30 3:48 ` Michael S. Tsirkin
2016-08-30 3:52 ` Alex Williamson
2016-08-30 3:52 ` [Qemu-devel] " Alex Williamson
2016-08-30 3:57 ` Michael S. Tsirkin
2016-08-30 3:57 ` [Qemu-devel] " Michael S. Tsirkin
2016-08-30 3:57 ` Michael S. Tsirkin
2016-08-30 4:53 ` Alex Williamson
2016-08-30 4:53 ` [Qemu-devel] " Alex Williamson
2016-08-30 4:53 ` Alex Williamson
2016-08-30 5:20 ` Michael S. Tsirkin
2016-08-30 5:20 ` [Qemu-devel] " Michael S. Tsirkin
2016-08-30 5:20 ` Michael S. Tsirkin
2016-08-30 12:46 ` Alex Williamson
2016-08-30 12:46 ` [Qemu-devel] " Alex Williamson
2016-08-30 12:46 ` Alex Williamson
2016-08-30 3:52 ` Alex Williamson
2016-08-30 9:59 ` kbuild test robot
2016-08-30 9:59 ` [Qemu-devel] " kbuild test robot
2016-08-30 9:59 ` kbuild test robot
2016-08-30 3:16 ` [Qemu-devel] [PATCH v2 0/2] vfio: blacklist legacy virtio devices Jason Wang
2016-08-30 3:16 ` Jason Wang
2016-08-30 3:49 ` Michael S. Tsirkin
2016-08-30 3:49 ` Michael S. Tsirkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1472523968-9540-1-git-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.