From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: pair@us.ibm.com, "Daniel P. Berrangé" <berrange@redhat.com>,
aik@ozlabs.ru, groug@kaod.org, qemu-devel@nongnu.org,
paulus@samba.org, clg@kaod.org, mdroth@us.ibm.com,
qemu-ppc@nongnu.org
Subject: Re: Upstream QEMU guest support policy ? Re: [PATCH v3 0/2] spapr: Use vIOMMU translation for virtio by default
Date: Wed, 11 Mar 2020 03:33:59 -0400 [thread overview]
Message-ID: <20200311031202-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20200311011247.GT660117@umbus.fritz.box>
On Wed, Mar 11, 2020 at 12:12:47PM +1100, David Gibson wrote:
> I am wondering if we have to introduce an "svm=on" flag anyway. It's
> pretty ugly, since all it would be doing is changing defaults here and
> there for compatibilty with a possible future SVM transition, but
> maybe it's the best we can do :/.
Frankly I'm surprised there's no way for the hypervisor to block VM
transition to secure mode. To me an inability to disable DRM looks like
a security problem. Does not the ultravisor somehow allow
enabling/disabling this functionality from the hypervisor? It would be
even better if the hypervisor could block the guest from poking at the
ultravisor completely but I guess that would be too much to hope for.
next prev parent reply other threads:[~2020-03-11 7:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 4:30 [PATCH v3 0/2] spapr: Use vIOMMU translation for virtio by default David Gibson
2020-03-05 4:30 ` [PATCH v3 1/2] spapr: Disable legacy virtio devices for pseries-5.0 and later David Gibson
2020-03-05 10:31 ` Greg Kurz
2020-03-10 9:43 ` Greg Kurz
2020-03-10 9:57 ` Michael S. Tsirkin
2020-03-10 11:03 ` Michael S. Tsirkin
2020-03-10 12:24 ` Greg Kurz
2020-03-10 11:56 ` Daniel P. Berrangé
2020-03-11 0:58 ` David Gibson
2020-03-11 7:11 ` Michael S. Tsirkin
2020-03-12 1:14 ` David Gibson
2020-03-12 6:41 ` Michael S. Tsirkin
2020-03-05 4:30 ` [PATCH v3 2/2] spapr: Enable virtio iommu_platform=on by default David Gibson
2020-03-05 11:59 ` Greg Kurz
2020-03-10 10:43 ` Greg Kurz
2020-03-12 4:14 ` Alexey Kardashevskiy
2020-03-12 8:02 ` Greg Kurz
2020-03-10 11:43 ` Upstream QEMU guest support policy ? Re: [PATCH v3 0/2] spapr: Use vIOMMU translation for virtio " Daniel P. Berrangé
2020-03-11 1:12 ` David Gibson
2020-03-11 7:33 ` Michael S. Tsirkin [this message]
2020-03-12 1:10 ` David Gibson
2020-03-12 6:32 ` Michael S. Tsirkin
2020-03-16 3:06 ` David Gibson
2020-03-11 10:01 ` Daniel P. Berrangé
2020-03-11 11:48 ` Michael S. Tsirkin
2020-03-12 1:09 ` David Gibson
2020-03-12 1:08 ` David Gibson
2020-03-12 9:47 ` Daniel P. Berrangé
2020-03-11 17:19 ` Greg Kurz
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=20200311031202-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=aik@ozlabs.ru \
--cc=berrange@redhat.com \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=mdroth@us.ibm.com \
--cc=pair@us.ibm.com \
--cc=paulus@samba.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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.