From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: qemu-devel@nongnu.org, xiaoyao.li@intel.com,
chenyi.qiang@intel.com, armbru@redhat.com, pbonzini@redhat.com,
robert.hu@intel.com, Robert Hoo <robert.hu@linux.intel.com>,
rth@twiddle.net
Subject: Re: [PATCH v2 1/2] Introduce (x86) CPU model deprecation API
Date: Thu, 10 Sep 2020 21:42:12 +0200 [thread overview]
Message-ID: <f82bc4a0-58c5-fb2f-6cc1-8776f4772215@redhat.com> (raw)
In-Reply-To: <20200910191251.GN1618070@habkost.net>
On 9/10/20 9:12 PM, Eduardo Habkost wrote:
> On Thu, Sep 10, 2020 at 07:29:03AM +0200, Philippe Mathieu-Daudé wrote:
>> On 9/9/20 8:15 PM, Eduardo Habkost wrote:
>>> Hi,
>>>
>>> Thanks for the patch, and sorry for taking so long to review
>>> this. I'm finally getting to the patches that were postponed to
>>> 5.2.
>>
>> Sorry I missed that patch too.
>>
>> Why restrict this to CPUClass, and not provide this feature to
>> all ObjectClass?
>
> We could do it, but the field would be left unused for anything
> that's not a CPU model or machine type, as there are no other QMP
> interfaces for querying deprecation status yet.
>
> A QMP interface for querying deprecation status of device types
> in general would be useful, though.
OK we can move that later, thanks.
next prev parent reply other threads:[~2020-09-10 19:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 2:47 [PATCH v2 1/2] Introduce (x86) CPU model deprecation API Robert Hoo
2020-06-11 2:47 ` [PATCH v2 2/2] Mark Icelake-Client CPU models deprecated Robert Hoo
2020-06-28 11:30 ` [PATCH v2 1/2] Introduce (x86) CPU model deprecation API Robert Hoo
2020-09-09 18:15 ` Eduardo Habkost
2020-09-10 5:29 ` Philippe Mathieu-Daudé
2020-09-10 19:12 ` Eduardo Habkost
2020-09-10 19:42 ` Philippe Mathieu-Daudé [this message]
2020-09-11 6:22 ` Robert Hoo
2020-09-11 14:00 ` Eduardo Habkost
2020-09-14 10:50 ` Robert Hoo
2020-09-14 13:38 ` Eduardo Habkost
2020-09-15 2:56 ` Robert Hoo
2020-09-15 14:06 ` Eduardo Habkost
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=f82bc4a0-58c5-fb2f-6cc1-8776f4772215@redhat.com \
--to=philmd@redhat.com \
--cc=armbru@redhat.com \
--cc=chenyi.qiang@intel.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=robert.hu@intel.com \
--cc=robert.hu@linux.intel.com \
--cc=rth@twiddle.net \
--cc=xiaoyao.li@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).