From: Cornelia Huck <cohuck@redhat.com>
To: Pierre Morel <pmorel@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, pasic@linux.ibm.com,
borntraeger@de.ibm.com, frankja@linux.ibm.com, mst@redhat.com,
jasowang@redhat.com, kvm@vger.kernel.org,
linux-s390@vger.kernel.org,
virtualization@lists.linux-foundation.org,
thomas.lendacky@amd.com, david@gibson.dropbear.id.au,
linuxram@us.ibm.com, hca@linux.ibm.com, gor@linux.ibm.com
Subject: Re: [PATCH v9 1/2] virtio: let arch advertise guest's memory access restrictions
Date: Fri, 21 Aug 2020 13:59:06 +0200 [thread overview]
Message-ID: <20200821135906.1c6bede3.cohuck@redhat.com> (raw)
In-Reply-To: <1597854198-2871-2-git-send-email-pmorel@linux.ibm.com>
On Wed, 19 Aug 2020 18:23:17 +0200
Pierre Morel <pmorel@linux.ibm.com> wrote:
> An architecture may restrict host access to guest memory.
"e.g. IBM s390 Secure Execution or AMD SEV"
Just to make clearer what you are referring to?
>
> Provide a new Kconfig entry the architecture can select,
> CONFIG_ARCH_HAS_RESTRICTED_VIRTIO_MEMORY_ACCESS, when it provides
> the arch_has_restricted_virtio_memory_access callback to advertise
s/advertise/advertise to/
> VIRTIO common code when the architecture restricts memory access
> from the host.
"The common code can then fail the probe for any device where
VIRTIO_F_IOMMU_PLATFORM is required, but not set."
?
>
> Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
> ---
> drivers/virtio/Kconfig | 6 ++++++
> drivers/virtio/virtio.c | 15 +++++++++++++++
> include/linux/virtio_config.h | 9 +++++++++
> 3 files changed, 30 insertions(+)
>
> diff --git a/drivers/virtio/Kconfig b/drivers/virtio/Kconfig
> index 5809e5f5b157..509f3b4d8ba1 100644
> --- a/drivers/virtio/Kconfig
> +++ b/drivers/virtio/Kconfig
> @@ -6,6 +6,12 @@ config VIRTIO
> bus, such as CONFIG_VIRTIO_PCI, CONFIG_VIRTIO_MMIO, CONFIG_RPMSG
> or CONFIG_S390_GUEST.
>
> +config ARCH_HAS_RESTRICTED_VIRTIO_MEMORY_ACCESS
> + bool
> + help
> + This option is selected by any architecture enforcing
> + VIRTIO_F_IOMMU_PLATFORM
"This option is selected if the architecture may need to enforce
VIRTIO_F_IOMMU_PLATFORM."
?
> +
> menuconfig VIRTIO_MENU
> bool "Virtio drivers"
> default y
(...)
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
next prev parent reply other threads:[~2020-08-21 11:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 16:23 [PATCH v9 0/2] s390: virtio: let arch validate VIRTIO features Pierre Morel
2020-08-19 16:23 ` [PATCH v9 1/2] virtio: let arch advertise guest's memory access restrictions Pierre Morel
2020-08-21 11:59 ` Cornelia Huck [this message]
2020-08-21 13:08 ` Pierre Morel
2020-08-19 16:23 ` [PATCH v9 2/2] s390: virtio: PV needs VIRTIO I/O device protection Pierre Morel
2020-08-21 12:05 ` Cornelia Huck
2020-08-21 13:06 ` 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=20200821135906.1c6bede3.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@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=linuxram@us.ibm.com \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=pmorel@linux.ibm.com \
--cc=thomas.lendacky@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox