public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>,
	Gleb Natapov <gleb@redhat.com>
Subject: Re: [PATCH] qemu-kvm: x86: Fix mismerge in cpu_post_load
Date: Sun, 06 Dec 2009 11:54:45 +0200	[thread overview]
Message-ID: <4B1B7F65.2040904@redhat.com> (raw)
In-Reply-To: <4B18018D.1060305@siemens.com>

On 12/03/2009 08:21 PM, Jan Kiszka wrote:
> Merge 8e2c5ec2f6 forgot to restore some qemu-kvm-specific hooks in
> cpu_post_load. mp_state was readded later on, but tsc was missing,
> breaking the guest timing after resume. Also, reset of halt was dropped
> which is obviously required for in-kernel irqchip.
>    

Applied, thanks.

> BTW, this patch just made me realize that the TSC MSR belongs to the
> list states that should not be written back unconditionally. Upstream
> does this currently, qemu-kvm not (at the price one more kvm-specific
> hook into generic code).

   Yet another reminder why we don't rewrite, only refactor.

> Unlike the other states we discussed, this one
> is not "fixable" in the kernel. So I tend to think there is a real need
> for my write-back scope abstraction - which would also be able to handle
> the other states cleanly, both in upstream and here.
>    

Yes.  Gleb suggested treating mpstate/nmi as part of the APIC state 
(which makes sense), which would work, as APIC state is not 
automatically written back.  But the tsc msr would need special treatment.


-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2009-12-06  9:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03 18:21 [PATCH] qemu-kvm: x86: Fix mismerge in cpu_post_load Jan Kiszka
2009-12-06  9:54 ` Avi Kivity [this message]
2009-12-06 10:39   ` Jan Kiszka
2009-12-06 10:41     ` Avi Kivity
2009-12-06 10:56     ` Gleb Natapov
2009-12-06 10:33 ` Gleb Natapov
2009-12-06 10:44   ` Jan Kiszka
2009-12-06 10:49     ` Gleb Natapov

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=4B1B7F65.2040904@redhat.com \
    --to=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    /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