From: Pierre Morel <pmorel@linux.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: pasic@linux.ibm.com, borntraeger@de.ibm.com,
frankja@linux.ibm.com, mst@redhat.com, jasowang@redhat.com,
cohuck@redhat.com, kvm@vger.kernel.org,
linux-s390@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: [PATCH v2 0/1] s390: virtio: let's arch choose to accept devices without IOMMU feature
Date: Mon, 15 Jun 2020 14:39:23 +0200 [thread overview]
Message-ID: <1592224764-1258-1-git-send-email-pmorel@linux.ibm.com> (raw)
An architecture protecting the guest memory against unauthorized host
access may want to enforce VIRTIO I/O device protection through the
use of VIRTIO_F_IOMMU_PLATFORM.
Let's give a chance to the architecture to accept or not devices
without VIRTIO_F_IOMMU_PLATFORM.
Pierre Morel (1):
s390: virtio: let arch accept devices without IOMMU feature
arch/s390/mm/init.c | 6 ++++++
drivers/virtio/virtio.c | 9 +++++++++
include/linux/virtio.h | 2 ++
3 files changed, 17 insertions(+)
--
2.25.1
Changelog to v2:
- put the test in virtio_finalize_features()
(Connie)
- put the test inside VIRTIO core
(Jason)
- pass a virtio device as parameter
(Halil)
next reply other threads:[~2020-06-15 12:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 12:39 Pierre Morel [this message]
2020-06-15 12:39 ` [PATCH v2 1/1] s390: virtio: let arch accept devices without IOMMU feature Pierre Morel
2020-06-15 12:39 ` Pierre Morel
2020-06-16 6:22 ` Jason Wang
2020-06-16 7:33 ` Pierre Morel
2020-06-16 6:55 ` Christian Borntraeger
2020-06-16 6:55 ` Christian Borntraeger
2020-06-16 7:35 ` Pierre Morel
2020-06-16 12:21 ` Cornelia Huck
2020-06-16 9:52 ` Halil Pasic
2020-06-16 9:52 ` Halil Pasic
2020-06-16 10:52 ` Pierre Morel
2020-06-16 10:52 ` Pierre Morel
2020-06-16 11:57 ` Halil Pasic
2020-06-16 12:17 ` Cornelia Huck
2020-06-16 13:41 ` Pierre Morel
2020-06-16 13:50 ` Cornelia Huck
2020-06-16 12:20 ` Cornelia Huck
2020-06-16 13:36 ` Pierre Morel
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=1592224764-1258-1-git-send-email-pmorel@linux.ibm.com \
--to=pmorel@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--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.