qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Robert Hoo <robert.hu@linux.intel.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: qemu-devel@nongnu.org, armbru@redhat.com, robert.hu@intel.com,
	pbonzini@redhat.com, rth@twiddle.net
Subject: Re: [PATCH v3 2/2] Mark Icelake-Client CPU models deprecated
Date: Mon, 21 Sep 2020 15:45:12 +0800	[thread overview]
Message-ID: <e1003e56e9b38e257841eb9385f6c00bdaf0d4fa.camel@linux.intel.com> (raw)
In-Reply-To: <20200918042036.GY7594@habkost.net>

On Fri, 2020-09-18 at 00:20 -0400, Eduardo Habkost wrote:
> On Fri, Sep 18, 2020 at 10:18:56AM +0800, Robert Hoo wrote:
> > On Thu, 2020-09-17 at 14:01 -0400, Eduardo Habkost wrote:
> > > On Wed, Sep 16, 2020 at 04:37:14PM +0800, Robert Hoo wrote:
> > > > Going to obsolete Icelake-Client CPU models in the future.
> > > > 
> > > > Signed-off-by: Robert Hoo <robert.hu@linux.intel.com>
> > > > ---
> > > > Change log
> > > > v3:
> > > > Obsolete in v5.2 --> v5.3.
> > > > 
> > > >  target/i386/cpu.c | 10 +++++++++-
> > > >  1 file changed, 9 insertions(+), 1 deletion(-)
> > > > 
> > > > diff --git a/target/i386/cpu.c b/target/i386/cpu.c
> > > > index 9cb82b7..15c1c00 100644
> > > > --- a/target/i386/cpu.c
> > > > +++ b/target/i386/cpu.c
> > > > @@ -3467,7 +3467,12 @@ static X86CPUDefinition
> > > > builtin_x86_defs[] =
> > > > {
> > > >          .xlevel = 0x80000008,
> > > >          .model_id = "Intel Core Processor (Icelake)",
> > > >          .versions = (X86CPUVersionDefinition[]) {
> > > > -            { .version = 1 },
> > > > +            {
> > > > +                .version = 1,
> > > > +                .deprecated = true,
> > > > +                .note = "Deprecated. Will be obsoleted in
> > > > v5.3.
> > > > Please use "
> > > > +                        "'Icelake-Server-v1' CPU model",
> > > 
> > > What's the difference between "deprecated" and "obsoleted"?
> > > 
> > 
> > Forgive my non-native understanding on English word:-D
> 
> No problem!  I'm not a native speaker either.  :-)
> 
> > Here is my understanding:
> > 'Deprecate' is to express strong disapproval on the usage; but, can
> > still be used if user insists.
> > 'Obsolete' means not usable anymore.
> > 
> > You can feel free to reword the note words.
> > Perhaps substitute 'removed' for 'obsolete' will be better.
> 
> "Removed" would be clearer, yes.  It's probably better to not
> mention the exact version, and just say it will be removed in
> the future.

Then I would tend to agree with your suggestion of no specific
'deprecation_note' at all; instead, a general warning message "will be
removed in the future" in machine_run_board_init().
> 
> Or maybe just make the message shorter and set deprecation_note
> to "Please use Icelake-Server instead".  The details can be
> documented in docs/system/deprecated.rst.
> 
Prefer documenting detail and model specific deprecation plan in
docs/system/deprecated.rst.



  reply	other threads:[~2020-09-21  7:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-16  8:37 [PATCH v3 1/2] Introduce (x86) CPU model deprecation API Robert Hoo
2020-09-16  8:37 ` [PATCH v3 2/2] Mark Icelake-Client CPU models deprecated Robert Hoo
2020-09-17 18:01   ` Eduardo Habkost
2020-09-18  2:18     ` Robert Hoo
2020-09-18  4:20       ` Eduardo Habkost
2020-09-21  7:45         ` Robert Hoo [this message]
2020-09-21 15:25           ` Eduardo Habkost
2020-09-17 18:18 ` [PATCH v3 1/2] Introduce (x86) CPU model deprecation API Eduardo Habkost
2020-09-18  5:48   ` Robert Hoo
2020-09-18 16:42     ` Eduardo Habkost
2020-09-19  3:22       ` Robert Hoo
2020-09-21 15:37         ` Eduardo Habkost
2020-09-22  5:07           ` Robert Hoo

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=e1003e56e9b38e257841eb9385f6c00bdaf0d4fa.camel@linux.intel.com \
    --to=robert.hu@linux.intel.com \
    --cc=armbru@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=robert.hu@intel.com \
    --cc=rth@twiddle.net \
    /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).