On 07/04/2022 8:55, Markus Armbruster wrote:
> Cole Robinson writes:
>
>> On 2/28/22 4:39 AM, Dov Murik wrote:
>>>
>>>
>>> On 28/02/2022 11:31, Daniel P. Berrangé wrote:
On Mon, Feb 28, 2022 at 09:30:14AM +, Dov Murik wrote:
> Add a new field 'cpu0-id' to the response of query-sev
Cole Robinson writes:
> On 2/28/22 4:39 AM, Dov Murik wrote:
>>
>>
>> On 28/02/2022 11:31, Daniel P. Berrangé wrote:
>>> On Mon, Feb 28, 2022 at 09:30:14AM +, Dov Murik wrote:
Add a new field 'cpu0-id' to the response of query-sev-capabilities QMP
command. The value of the field
On 2/28/22 4:39 AM, Dov Murik wrote:
>
>
> On 28/02/2022 11:31, Daniel P. Berrangé wrote:
>> On Mon, Feb 28, 2022 at 09:30:14AM +, Dov Murik wrote:
>>> Add a new field 'cpu0-id' to the response of query-sev-capabilities QMP
>>> command. The value of the field is the base64-encoded unique ID
Queued, thanks.
Paolo
On 28/02/2022 11:31, Daniel P. Berrangé wrote:
> On Mon, Feb 28, 2022 at 09:30:14AM +, Dov Murik wrote:
>> Add a new field 'cpu0-id' to the response of query-sev-capabilities QMP
>> command. The value of the field is the base64-encoded unique ID of CPU0
>> (socket 0), which can be used to r
On Mon, Feb 28, 2022 at 09:30:14AM +, Dov Murik wrote:
> Add a new field 'cpu0-id' to the response of query-sev-capabilities QMP
> command. The value of the field is the base64-encoded unique ID of CPU0
> (socket 0), which can be used to retrieve the signed CEK of the CPU from
> AMD's Key Dist
Add a new field 'cpu0-id' to the response of query-sev-capabilities QMP
command. The value of the field is the base64-encoded unique ID of CPU0
(socket 0), which can be used to retrieve the signed CEK of the CPU from
AMD's Key Distribution Service (KDS).
Signed-off-by: Dov Murik
---
v3:
- dyna
