qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
	Gleb Natapov <gleb@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC 7/7] target-i386: Disable direct passthrough of PMU CPUID leaf by default
Date: Fri, 26 Apr 2013 17:39:15 +0200	[thread overview]
Message-ID: <20130426173915.20d02c7d@thinkpad> (raw)
In-Reply-To: <517A9E3E.2060901@suse.de>

On Fri, 26 Apr 2013 17:33:18 +0200
Andreas Färber <afaerber@suse.de> wrote:

> Am 26.04.2013 17:31, schrieb Eduardo Habkost:
> > On Fri, Apr 26, 2013 at 05:10:29PM +0200, Igor Mammedov wrote:
> >> On Thu, 25 Apr 2013 15:43:06 -0300
> >> Eduardo Habkost <ehabkost@redhat.com> wrote:
> >>
> >>> The current code handling the CPUID 0xA leaf simply forwards all data
> >>> from GET_SUPPORTED_CPUID directly to the guest, breaking migration
> >>> between hosts with different number of PMU counters.
> >>>
> >>> This patch disables this behavior, except on older machine-types (for
> >>> compatibility) and on the "host" CPU model.
> >> Please, make it static property and use compat properties.
> >> Result will be simpler and  much less will have to be redone/discarded after
> >> converting to the rest to properties and sub-classes.
> > 
> > I was going to say that static properties were too much work to be done
> > in time for 1.5, but you are right: in this specific case adding a
> > static property for the cpuid_pmu_passthrough field looks very easy. I
> > will give it a try.
> 
> I am hoping to get as initial set (though not all) of the static
> properties still into 1.5. Using them to fix CPUID bugs can then be done
> during Hard Freeze. :)
patch "[PATCH 02/10] target-i386: cpu: convert existing dynamic properties
into static properties" should be enough for using model,level compat
properties.

> 
> Andreas
> 
> -- 
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
> 


-- 
Regards,
  Igor

  reply	other threads:[~2013-04-26 15:39 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-25 18:42 [Qemu-devel] [RFC 0/7] CPUID fixes for 1.5 Eduardo Habkost
2013-04-25 18:43 ` [Qemu-devel] [RFC 1/7] target-i386: Introduce generic CPUID feature compat function Eduardo Habkost
2013-05-06 20:34   ` Andreas Färber
2013-04-25 18:43 ` [Qemu-devel] [RFC 2/7] target-i386: Introduce compat function to set CPUID 'level' Eduardo Habkost
2013-04-26 15:16   ` Igor Mammedov
2013-04-26 15:28     ` Eduardo Habkost
2013-04-25 18:43 ` [Qemu-devel] [RFC 3/7] target-i386: Introduce compat function to set CPUID 'model' Eduardo Habkost
2013-04-25 18:43 ` [Qemu-devel] [RFC 4/7] pc: Use separate init functions for pc-*-1.4 Eduardo Habkost
2013-04-25 18:43 ` [Qemu-devel] [RFC 5/7] target-i386: n270 can MOVBE Eduardo Habkost
2013-05-06 20:35   ` Andreas Färber
2013-04-25 18:43 ` [Qemu-devel] [RFC 6/7] target-i386: change CPUID model of 486 to 8 Eduardo Habkost
2013-04-25 19:11   ` Eduardo Habkost
2013-04-25 18:43 ` [Qemu-devel] [RFC 7/7] target-i386: Disable direct passthrough of PMU CPUID leaf by default Eduardo Habkost
2013-04-26 15:10   ` Igor Mammedov
2013-04-26 15:31     ` Eduardo Habkost
2013-04-26 15:33       ` Andreas Färber
2013-04-26 15:39         ` Igor Mammedov [this message]
2013-04-26 17:30           ` Eduardo Habkost
2013-04-26 17:41             ` Igor Mammedov
2013-04-26 19:01               ` Eduardo Habkost
2013-04-30 17:04                 ` Igor Mammedov
2013-04-30 19:57                   ` Eduardo Habkost
2013-05-01 11:14                     ` Andreas Färber
2013-05-02 14:43                       ` Eduardo Habkost
2013-05-02 14:50                         ` Andreas Färber

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=20130426173915.20d02c7d@thinkpad \
    --to=imammedo@redhat.com \
    --cc=afaerber@suse.de \
    --cc=ehabkost@redhat.com \
    --cc=gleb@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).