From: Paolo Bonzini <pbonzini@redhat.com>
To: Eric Blake <eblake@redhat.com>, Yang Zhong <yang.zhong@intel.com>
Cc: philmd@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH 3/6] numa: Add SGXEPCSection list for multiple sections
Date: Tue, 12 Oct 2021 13:01:58 +0200 [thread overview]
Message-ID: <d27b62fe-1660-0d1f-4263-88e181d811bb@redhat.com> (raw)
In-Reply-To: <20211011170324.2f5oacnghualbu45@redhat.com>
On 11/10/21 19:03, Eric Blake wrote:
>> +# @sections: The EPC sections info for guest
>> #
>> # Since: 6.2
> Given this has not yet been in a stable release, we can make this change...
>
>> ##
>> @@ -356,7 +371,7 @@
>> 'sgx1': 'bool',
>> 'sgx2': 'bool',
>> 'flc': 'bool',
>> - 'section-size': 'uint64'},
>> + 'sections': ['SGXEPCSection']},
>> 'if': 'TARGET_I386' }
> ...but are we sure we have the best interface possible if we are still
> expressing uncertainty about the QAPI used to represent it?
Yes, I think it's better to have a more flexible representation.
Paolo
next prev parent reply other threads:[~2021-10-12 11:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 11:15 [PATCH 0/6] SGX NUMA support Yang Zhong
2021-10-11 11:15 ` [PATCH 1/6] numa: Enable numa for SGX EPC sections Yang Zhong
2021-10-11 16:32 ` Eric Blake
2021-10-20 7:02 ` Yang Zhong
2021-10-11 11:15 ` [PATCH 2/6] monitor: Support 'info numa' command Yang Zhong
2021-10-11 11:15 ` [PATCH 3/6] numa: Add SGXEPCSection list for multiple sections Yang Zhong
2021-10-11 17:03 ` Eric Blake
2021-10-12 11:01 ` Paolo Bonzini [this message]
2021-10-20 8:06 ` Yang Zhong
2021-10-12 11:01 ` Paolo Bonzini
2021-10-20 8:08 ` Yang Zhong
2021-10-11 11:15 ` [PATCH 4/6] monitor: numa support for 'info sgx' command Yang Zhong
2021-10-12 10:59 ` Paolo Bonzini
2021-10-20 7:08 ` Yang Zhong
2021-10-11 11:15 ` [PATCH 5/6] numa: Enable numa for libvirt interface Yang Zhong
2021-10-12 10:59 ` Paolo Bonzini
2021-10-11 11:15 ` [PATCH 6/6] doc: Add the SGX numa description Yang Zhong
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=d27b62fe-1660-0d1f-4263-88e181d811bb@redhat.com \
--to=pbonzini@redhat.com \
--cc=eblake@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yang.zhong@intel.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).