From: Igor Mammedov <imammedo@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>,
ehabkost@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1/5] target-i386: print deprecated warning if xlevel < 0x80000000
Date: Mon, 21 Jan 2013 13:14:49 +0100 [thread overview]
Message-ID: <20130121131449.73883a82@nial.usersys.redhat.com> (raw)
In-Reply-To: <50FCFEAB.5000600@suse.de>
On Mon, 21 Jan 2013 09:39:07 +0100
Andreas Färber <afaerber@suse.de> wrote:
> Am 17.01.2013 16:16, schrieb Igor Mammedov:
> > Signed-off-by: Igor Mammedov <imammedo@redhat.com>
> > Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>
> > ---
> > target-i386/cpu.c | 2 ++
> > 1 files changed, 2 insertions(+), 0 deletions(-)
> >
> > diff --git a/target-i386/cpu.c b/target-i386/cpu.c
> > index 333745b..ce914da 100644
> > --- a/target-i386/cpu.c
> > +++ b/target-i386/cpu.c
> > @@ -1399,6 +1399,8 @@ static int cpu_x86_parse_featurestr(x86_def_t
> > *x86_cpu_def, char *features) goto error;
> > }
> > if (numvalue < 0x800000 00) {
> > + fprintf(stderr, "xlevel value shall always be >=
> > 0x80000000"
> > + ", fixup will be deprecated in future
> > versions\n"); numvalue += 0x80000000;
> > }
> > x86_cpu_def->xlevel = numvalue;
>
> This has been reviewed without objections so far, so I would apply it
> for 1.4. Either way you should document this intent for users already:
> http://wiki.qemu.org/ChangeLog/1.4
Would be something like this suitable:
xlevel argument for -cpu option, currently fix-ups it's value if it's less
than 0x80000000. Fix-up will be removed in QEMU 1.6 release and users are
expected to provide valid xlevel value or qemu will fail to start.
>
> We had such discussions before, around removing cpudef support.
>
> When do you plan to remove this, and being deprecated, shouldn't it
> rather read "fixup will be removed in future versions"? ;)
> If it fits within 80 chars I can edit it myself.
No need for it, I'll fix it and respin series.
>
> Cheers,
> Andreas
>
Thanks,
Igor
next prev parent reply other threads:[~2013-01-21 12:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 15:16 [Qemu-devel] [PATCH qom-cpu 0/5] x86 CPU cleanup, part 4 Igor Mammedov
2013-01-17 15:16 ` [Qemu-devel] [PATCH 1/5] target-i386: print deprecated warning if xlevel < 0x80000000 Igor Mammedov
2013-01-21 8:39 ` Andreas Färber
2013-01-21 12:14 ` Igor Mammedov [this message]
2013-01-17 15:16 ` [Qemu-devel] [PATCH 2/5] target-i386: replace uint32_t vendor fields by vendor string in x86_def_t Igor Mammedov
2013-01-17 15:29 ` Eduardo Habkost
2013-01-18 7:12 ` li guang
2013-01-18 13:40 ` Igor Mammedov
2013-01-21 3:16 ` li guang
2013-01-21 8:18 ` Andreas Färber
2013-01-17 15:16 ` [Qemu-devel] [PATCH 3/5] target-i386: remove vendor_override field from CPUX86State Igor Mammedov
2013-01-17 15:30 ` Eduardo Habkost
2013-01-17 15:16 ` [Qemu-devel] [PATCH 4/5] target-i386: set custom features/properties without intermediate x86_def_t Igor Mammedov
2013-01-17 17:44 ` Eduardo Habkost
2013-01-18 14:49 ` Igor Mammedov
2013-01-17 15:16 ` [Qemu-devel] [PATCH 5/5] target-i386: remove setting tsc-frequency from x86_def_t Igor Mammedov
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=20130121131449.73883a82@nial.usersys.redhat.com \
--to=imammedo@redhat.com \
--cc=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=ehabkost@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).