qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Tom Lendacky <thomas.lendacky@amd.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH for-6.0] qapi: qom: do not use target-specific conditionals
Date: Fri, 26 Mar 2021 15:50:07 +0100	[thread overview]
Message-ID: <4418ca49-818a-bb5f-b6e8-36dc21b70013@redhat.com> (raw)
In-Reply-To: <87o8f6qew9.fsf@dusky.pond.sub.org>

On 26/03/21 13:27, Markus Armbruster wrote:
> ... until Kevin added some when he QAPIfied.  Looks like this (copied
> from qemu-qmp-ref.7)[*]:
> 
>     SevGuestProperties (Object)
>         Properties for sev-guest objects.
> 
>     Members
>         sev-device: string (optional)
>                SEV device to use (default: "/dev/sev")
> 
>         dh-cert-file: string (optional)
>                guest owners DH certificate (encoded with base64)
> 
>         session-file: string (optional)
>                guest owners session parameters (encoded with base64)
> 
>         policy: int (optional)
>                SEV policy value (default: 0x1)
> 
>         handle: int (optional)
>                SEV firmware handle (default: 0)
> 
>         cbitpos: int (optional)
>                C-bit location in page table entry (default: 0)
> 
>         reduced-phys-bits: int
>                number  of  bits  in  physical addresses that become unavailable
>                when SEV is enabled
> 
>     Since
>         2.12
> 
>     If
>         defined(CONFIG_SEV)
> 
> Your patch drops the last three lines, without a replacement.

Yes, I mean the regression is not from 5.2.

Paolo



  reply	other threads:[~2021-03-26 14:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-26 10:03 [PATCH for-6.0] qapi: qom: do not use target-specific conditionals Paolo Bonzini
2021-03-26 10:57 ` Markus Armbruster
2021-03-26 11:49   ` Paolo Bonzini
2021-03-26 12:27     ` Markus Armbruster
2021-03-26 14:50       ` Paolo Bonzini [this message]
2021-03-26 13:45 ` Tom Lendacky

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=4418ca49-818a-bb5f-b6e8-36dc21b70013@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=armbru@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thomas.lendacky@amd.com \
    /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;
as well as URLs for NNTP newsgroup(s).