From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brijesh Singh Subject: Re: [Qemu-devel] [PATCH v6 17/23] qapi: add SEV_MEASUREMENT event Date: Thu, 1 Feb 2018 09:25:59 -0600 Message-ID: <315572b0-2893-2247-c20b-717becd9661c@amd.com> References: <20180129174132.108925-1-brijesh.singh@amd.com> <20180129174132.108925-18-brijesh.singh@amd.com> <87mv0tvs6a.fsf@dusky.pond.sub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: brijesh.singh@amd.com, qemu-devel@nongnu.org, "Edgar E. Iglesias" , Peter Maydell , Eduardo Habkost , kvm@vger.kernel.org, Tom Lendacky , Stefan Hajnoczi , "Michael S. Tsirkin" , Richard Henderson , "Dr. David Alan Gilbert" , Paolo Bonzini To: Markus Armbruster Return-path: Received: from mail-co1nam03on0058.outbound.protection.outlook.com ([104.47.40.58]:18688 "EHLO NAM03-CO1-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751530AbeBAP0I (ORCPT ); Thu, 1 Feb 2018 10:26:08 -0500 In-Reply-To: <87mv0tvs6a.fsf@dusky.pond.sub.org> Content-Language: en-US Sender: kvm-owner@vger.kernel.org List-ID: On 01/31/2018 11:45 AM, Markus Armbruster wrote: > Brijesh Singh writes: > >> Add SEV_MEASUREMENT event which can be used by libvirt to get the >> measurement of the memory regions encrypted through the SEV launch >> flow. The measurement value is base64 encoded. >> >> Cc: Daniel P. Berrange >> Cc: Eric Blake >> Cc: Markus Armbruster >> Signed-off-by: Brijesh Singh >> --- >> qapi-schema.json | 13 +++++++++++++ >> 1 file changed, 13 insertions(+) >> >> diff --git a/qapi-schema.json b/qapi-schema.json >> index 2046c96669bf..e1f5d14e2e3f 100644 >> --- a/qapi-schema.json >> +++ b/qapi-schema.json >> @@ -3192,3 +3192,16 @@ >> # Since: 2.11 >> ## >> { 'command': 'watchdog-set-action', 'data' : {'action': 'WatchdogAction'} } >> + >> +## >> +# @SEV_MEASUREMENT: >> +# >> +# Emitted when measurement is available for the SEV guest. >> +# >> +# @value: measurement value encoded in base64 >> +# >> +# Since: 2.12 >> +# >> +## >> +{ 'event' : 'SEV_MEASUREMENT', >> + 'data' : { 'value' : 'str' } } > > New event -> automatic question: do we need a way to poll for this > information? Say when an event could get lost during a libvirt restart. > In our initial SEV patches for libvirt we ran into similar cases where the event was dropped on restart, and now leaning towards dropping this event patch and add a new QMP command which can be used by libvirt to retrieve the measurement.