From: Igor Mammedov <imammedo@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: peter.maydell@linaro.org, Peter Krempa <pkrempa@redhat.com>,
libvir-list@redhat.com, mark.cave-ayland@ilande.co.uk,
qemu-devel@nongnu.org, blauwirbel@gmail.com, qemu-arm@nongnu.org,
pbonzini@redhat.com, Jiri Denemark <jdenemar@redhat.com>,
rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH RFC 4/8] target-i386: cpu: consolidate calls of object_property_parse() in x86_cpu_parse_featurestr
Date: Thu, 2 Jun 2016 18:32:03 +0200 [thread overview]
Message-ID: <20160602183203.4814e984@nial.brq.redhat.com> (raw)
In-Reply-To: <20160602145322.GG19055@thinpad.lan.raisama.net>
On Thu, 2 Jun 2016 11:53:22 -0300
Eduardo Habkost <ehabkost@redhat.com> wrote:
> (CCing libvirt folks)
>
> BTW:
>
> On Thu, Jun 02, 2016 at 02:22:22PM +0200, Igor Mammedov wrote:
> [...]
> > > /* Special cases: */
> > > if (!strcmp(name, "xlevel")) {
> > > numvalue = strtoul(val, &err, 0);
> > > if (!*val || *err) {
> > > error_setg(errp, "bad numerical value %s", val);
> > > return;
> > > }
> > > if (numvalue < 0x80000000) {
> > > error_report("xlevel value shall always be >= 0x80000000"
> > > ", fixup will be removed in future versions");
> > > numvalue += 0x80000000;
> > > snprintf(num, sizeof(num), "%" PRIu32, numvalue);
> > > val = num;
> [...]
> > > } else if (!strcmp(name, "hv-spinlocks")) {
> > > const int min = 0xFFF;
> > >
> > > numvalue = strtoul(val, &err, 0);
> > > if (!*val || *err) {
> > > error_setg(errp, "bad numerical value %s", val);
> > > return;
> > > }
> > > if (numvalue < min) {
> > > error_report("hv-spinlocks value shall always be >= 0x%x"
> > > ", fixup will be removed in future versions",
> > > min);
> > > numvalue = min;
> > > }
>
> Those "fixup will be removed in future versions" warnings are
> present since QEMU 1.7. Assuming that libvirt never allowed those
> invalid values to be used in the configuration (did it?), I
> believe we can safely remove the hv-spinlocks and xlevel fixups
> in QEMU 2.7.
>
> The hv-spinlocks setter already rejects invalid values. We just
> need to make x86_cpu_realizefn() reject invalid xlevel values.
I'll leave axing them to you.
next prev parent reply other threads:[~2016-06-02 16:32 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 16:37 [Qemu-devel] [PATCH RFC 0/8] cpus: make "-cpu cpux, features" global properties Igor Mammedov
2016-06-01 16:37 ` [Qemu-devel] [PATCH RFC 1/8] target-i386: cpu: move features logic that requires CPUState to realize time Igor Mammedov
2016-06-01 17:43 ` Eduardo Habkost
2016-06-02 9:59 ` Igor Mammedov
2016-06-02 14:38 ` Eduardo Habkost
2016-06-02 16:56 ` Igor Mammedov
2016-06-02 17:34 ` Eduardo Habkost
2016-06-02 18:23 ` Igor Mammedov
2016-06-02 18:43 ` Eduardo Habkost
2016-06-03 10:13 ` Igor Mammedov
2016-06-03 19:26 ` Eduardo Habkost
2016-06-04 16:44 ` Igor Mammedov
2016-06-01 16:37 ` [Qemu-devel] [PATCH RFC 2/8] target-i386: cpu: move xcc->kvm_required check to reaize time Igor Mammedov
2016-06-01 17:46 ` Eduardo Habkost
2016-06-02 10:02 ` Igor Mammedov
2016-06-01 16:37 ` [Qemu-devel] [PATCH RFC 3/8] target-i386: cpu: use cpu_generic_init() in cpu_x86_init() Igor Mammedov
2016-06-01 18:08 ` Eduardo Habkost
2016-06-01 16:37 ` [Qemu-devel] [PATCH RFC 4/8] target-i386: cpu: consolidate calls of object_property_parse() in x86_cpu_parse_featurestr Igor Mammedov
2016-06-01 18:46 ` Eduardo Habkost
2016-06-02 12:22 ` Igor Mammedov
2016-06-02 14:42 ` Eduardo Habkost
2016-06-02 14:53 ` Eduardo Habkost
2016-06-02 15:05 ` Peter Krempa
2016-06-02 16:31 ` Igor Mammedov
2016-06-03 7:30 ` Peter Krempa
2016-06-03 9:37 ` Igor Mammedov
2016-06-03 19:36 ` Eduardo Habkost
2016-06-02 16:32 ` Igor Mammedov [this message]
2016-06-02 16:55 ` [Qemu-devel] [PATCH] target-i386: Remove xlevel & hv-spinlocks option fixups Eduardo Habkost
2016-06-02 21:07 ` [Qemu-devel] [libvirt] " Eric Blake
2016-06-01 16:37 ` [Qemu-devel] [PATCH RFC 5/8] target-sparc: cpu: use sparc_cpu_parse_features() directly Igor Mammedov
2016-06-01 16:37 ` [Qemu-devel] [PATCH RFC 6/8] cpu: use CPUClass->parse_features() as convertor to global properties Igor Mammedov
2016-06-01 18:54 ` Eduardo Habkost
2016-06-02 10:06 ` Igor Mammedov
2016-06-02 14:41 ` Eduardo Habkost
2016-06-01 16:37 ` [Qemu-devel] [PATCH RFC 7/8] arm: virt: parse cpu_model only once Igor Mammedov
2016-06-01 16:37 ` [Qemu-devel] [PATCH RFC 8/8] pc: parse cpu features " Igor Mammedov
2016-06-01 18:21 ` [Qemu-devel] [PATCH RFC 0/8] cpus: make "-cpu cpux, features" global properties Peter Maydell
2016-06-01 18:51 ` Eduardo Habkost
2016-06-02 20:44 ` David Hildenbrand
2016-06-03 12:06 ` Jiri Denemark
2016-06-03 12:14 ` David Hildenbrand
[not found] ` <201606022044.u52KaIkv017063@mx0a-001b2d01.pphosted.com>
2016-06-03 0:02 ` Eduardo Habkost
2016-06-03 6:36 ` David Hildenbrand
[not found] ` <20160603083621.6547bde4@thinkpad-w530>
2016-06-03 9:20 ` Igor Mammedov
2016-06-03 10:18 ` David Hildenbrand
2016-06-03 19:54 ` Eduardo Habkost
2016-06-06 9:59 ` David Hildenbrand
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=20160602183203.4814e984@nial.brq.redhat.com \
--to=imammedo@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=ehabkost@redhat.com \
--cc=jdenemar@redhat.com \
--cc=libvir-list@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=pkrempa@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--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).