From: "Andreas Färber" <afaerber@suse.de>
To: Gleb Natapov <gleb@redhat.com>, Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, ehabkost@redhat.com
Subject: Re: [Qemu-devel] [PATCH] kvm: migrate vPMU state
Date: Thu, 25 Jul 2013 16:50:38 +0200 [thread overview]
Message-ID: <51F13B3E.4080707@suse.de> (raw)
In-Reply-To: <51F13A46.7010003@suse.de>
Am 25.07.2013 16:46, schrieb Andreas Färber:
> Am 25.07.2013 12:14, schrieb Gleb Natapov:
>> On Wed, Jul 24, 2013 at 05:01:15PM +0200, Andreas Färber wrote:
>>> New msr_* fields would be candidates for X86CPU, but there's already one
>>> in CPUX86State. :/
>>>
>> Is this NAK?
>
> No, it was more an implicit question of whether Paolo had considered a
> different placement?
>
> Since there is a uint64_t msr_ia32_misc_enable visible as precedent, I
> was thinking it would be better for consistency to do such movements as
> follow-up, if at all. However checking on that now, I do not have any
> msr_* there in my repo, and it is after CPU_COMMON, thus not reset -
> Paolo, what do you think?
Consider me confused, please ignore. msr_ia32_misc_enable is further
above and is *before* CPU_COMMON, thus moving it into X86CPU would
require zero'ing them on reset, so not as simple as a pure code movement
and s/env/cpu/g, so better leave it as is for now so short before v1.6
Hard Freeze.
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-25 14:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 14:37 [Qemu-devel] [PATCH] kvm: migrate vPMU state Paolo Bonzini
2013-07-24 15:01 ` Andreas Färber
2013-07-25 10:14 ` Gleb Natapov
2013-07-25 10:27 ` Paolo Bonzini
2013-07-25 14:46 ` Andreas Färber
2013-07-25 14:50 ` 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=51F13B3E.4080707@suse.de \
--to=afaerber@suse.de \
--cc=ehabkost@redhat.com \
--cc=gleb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.