From: "Andreas Färber" <afaerber@suse.de>
To: Eduardo Habkost <ehabkost@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: Igor Mammedov <imammedo@redhat.com>,
qemu-devel@nongnu.org, Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] [qom-cpu PATCH 0/2] i386: disable PMU CPUID leaf by default
Date: Sun, 28 Jul 2013 22:21:47 +0200 [thread overview]
Message-ID: <51F57D5B.4090704@suse.de> (raw)
In-Reply-To: <51F2D8FB.6040208@suse.de>
Am 26.07.2013 22:15, schrieb Andreas Färber:
> Am 26.07.2013 22:09, schrieb Eduardo Habkost:
>> Changes v1 -> v2:
>> * compat property is now named "pmu" instead of "pmu-passthrough"
>>
>> Eduardo Habkost (2):
>> i386: pass X86CPU object to cpu_x86_find_by_name()
>> i386: disable PMU CPUID leaves by default
>>
>> include/hw/i386/pc.h | 4 ++++
>> target-i386/cpu-qom.h | 7 +++++++
>> target-i386/cpu.c | 16 +++++++++++++---
>> 3 files changed, 24 insertions(+), 3 deletions(-)
>
> Technically the patch looks okay for 1.6. Waiting for functional acks.
Since time is running out and the name requested by Paolo was adopted, I
have queued this on qom-cpu with minor adjustments, most notably moving
and renaming the property array:
https://github.com/afaerber/qemu-cpu/commits/qom-cpu
Paolo, if there's still corrections necessary, let me know whether to
unqueue or whether we can follow-up during Hard Freeze.
Thanks,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
prev parent reply other threads:[~2013-07-28 20:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 20:09 [Qemu-devel] [qom-cpu PATCH 0/2] i386: disable PMU CPUID leaf by default Eduardo Habkost
2013-07-26 20:09 ` [Qemu-devel] [qom-cpu PATCH v2 1/2] i386: pass X86CPU object to cpu_x86_find_by_name() Eduardo Habkost
2013-07-26 20:09 ` [Qemu-devel] [qom-cpu PATCH v2 2/2] i386: disable PMU CPUID leaf by default Eduardo Habkost
2013-07-26 20:15 ` [Qemu-devel] [qom-cpu PATCH 0/2] " Andreas Färber
2013-07-28 20:21 ` Andreas Färber [this message]
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=51F57D5B.4090704@suse.de \
--to=afaerber@suse.de \
--cc=ehabkost@redhat.com \
--cc=gleb@redhat.com \
--cc=imammedo@redhat.com \
--cc=pbonzini@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).