From: Erik Skultety <eskultet@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Singh, Brijesh" <brijesh.singh@amd.com>,
Laszlo Ersek <lersek@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] target/i386: sev: add 'sev-max-guests' field to 'query-sev-capabilities'
Date: Fri, 12 Apr 2019 11:13:26 +0200 [thread overview]
Message-ID: <20190412091326.GE16137@beluga.usersys.redhat.com> (raw)
In-Reply-To: <77338015-015c-aaef-d522-11cabbba4214@redhat.com>
On Fri, Apr 12, 2019 at 10:26:45AM +0200, Paolo Bonzini wrote:
> On 12/04/19 10:19, Erik Skultety wrote:
> >> Since this field is not specific to guest configuration, I don't think
> >> it belongs in query-sev-capabilities; QEMU does not care about >1 guest.
> > Neither pdh nor cert-chain are specific to the guest config.
>
> Sort of, they are required to start a guest, aren't they? But the
Unless you're interested in the measurement, aka attestation, I don't think
those are required in any way.
Erik
> number of guests is irrelevant.
>
> > I see why this
> > should be better suited for query-sev, the same goes for libvirt - I think we
> > shouldn't have gone with reporting the SEV platform caps in domain capabilities,
> > we should have IMHO report it both in the host capabilities (platform specific
> > stuff) and in domain capabilities to indicate that both libvirt and QEMU
> > support the SEV feature. Having said that, we have a precedent which I think
> > we might be better off with following rather than splitting the information
> > among multiple commands.
>
> For Libvirt, sure. But I think this doesn't belong in QEMU at all.
> Libvirt should just use CPUID.
>
> Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Erik Skultety <eskultet@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Laszlo Ersek <lersek@redhat.com>,
"Singh, Brijesh" <brijesh.singh@amd.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] target/i386: sev: add 'sev-max-guests' field to 'query-sev-capabilities'
Date: Fri, 12 Apr 2019 11:13:26 +0200 [thread overview]
Message-ID: <20190412091326.GE16137@beluga.usersys.redhat.com> (raw)
Message-ID: <20190412091326.2-B2N3gtXFs-3YC3fPLZGdAuUR6eXaTnbeCFvdtvoks@z> (raw)
In-Reply-To: <77338015-015c-aaef-d522-11cabbba4214@redhat.com>
On Fri, Apr 12, 2019 at 10:26:45AM +0200, Paolo Bonzini wrote:
> On 12/04/19 10:19, Erik Skultety wrote:
> >> Since this field is not specific to guest configuration, I don't think
> >> it belongs in query-sev-capabilities; QEMU does not care about >1 guest.
> > Neither pdh nor cert-chain are specific to the guest config.
>
> Sort of, they are required to start a guest, aren't they? But the
Unless you're interested in the measurement, aka attestation, I don't think
those are required in any way.
Erik
> number of guests is irrelevant.
>
> > I see why this
> > should be better suited for query-sev, the same goes for libvirt - I think we
> > shouldn't have gone with reporting the SEV platform caps in domain capabilities,
> > we should have IMHO report it both in the host capabilities (platform specific
> > stuff) and in domain capabilities to indicate that both libvirt and QEMU
> > support the SEV feature. Having said that, we have a precedent which I think
> > we might be better off with following rather than splitting the information
> > among multiple commands.
>
> For Libvirt, sure. But I think this doesn't belong in QEMU at all.
> Libvirt should just use CPUID.
>
> Paolo
next prev parent reply other threads:[~2019-04-12 9:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 17:59 [Qemu-devel] [PATCH] target/i386: sev: add 'sev-max-guests' field to 'query-sev-capabilities' Singh, Brijesh
2019-04-11 17:59 ` Singh, Brijesh
2019-04-11 18:05 ` Daniel P. Berrangé
2019-04-11 18:05 ` Daniel P. Berrangé
2019-04-11 18:18 ` Singh, Brijesh
2019-04-11 18:18 ` Singh, Brijesh
2019-04-11 18:10 ` Laszlo Ersek
2019-04-11 18:10 ` Laszlo Ersek
2019-04-11 19:01 ` Laszlo Ersek
2019-04-11 19:01 ` Laszlo Ersek
2019-04-11 19:02 ` Singh, Brijesh
2019-04-11 19:02 ` Singh, Brijesh
2019-04-12 7:44 ` Laszlo Ersek
2019-04-12 7:44 ` Laszlo Ersek
2019-04-12 7:45 ` Paolo Bonzini
2019-04-12 7:45 ` Paolo Bonzini
2019-04-12 8:19 ` Erik Skultety
2019-04-12 8:19 ` Erik Skultety
2019-04-12 8:26 ` Paolo Bonzini
2019-04-12 8:26 ` Paolo Bonzini
2019-04-12 9:13 ` Erik Skultety [this message]
2019-04-12 9:13 ` Erik Skultety
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=20190412091326.GE16137@beluga.usersys.redhat.com \
--to=eskultet@redhat.com \
--cc=armbru@redhat.com \
--cc=brijesh.singh@amd.com \
--cc=lersek@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@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.