public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Avi Kivity <avi@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH][uq/master] KVM: x86: Fix eflags corruption in kvm mode
Date: Mon, 22 Feb 2010 09:13:14 +0100	[thread overview]
Message-ID: <4B823C9A.2010205@siemens.com> (raw)
In-Reply-To: <4B80F983.7040706@redhat.com>

Avi Kivity wrote:
> On 02/19/2010 07:21 PM, Jan Kiszka wrote:
>> This should explain a lot of the weird breakages of upstream KVM we've
>> seen recently (actually we should have seen it much earlier):
>>
>> Stop translating eflags into TCG format when in kvm mode as we never
>> translate it back and rather sync this broken state into the kernel.
>>
>>    
> 
> Applied to uq/master and uq/stable-0.12, thanks (though realistically 
> 0.12 kvm users should stick with qemu-kvm).
> 

Actually, I would prefer if more "light" kvm users (no demanding
performance requirements, no dependency on qemu-kvm-only features)
consider upstream instead of qemu-kvm so that it gains way more testing
than just by us when pushing some more bits. So we should keep on
informing people about limitations and known issues. We need them on
both sides.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2010-02-22  8:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-19 17:21 [PATCH][uq/master] KVM: x86: Fix eflags corruption in kvm mode Jan Kiszka
2010-02-21  9:14 ` Avi Kivity
2010-02-22  8:13   ` Jan Kiszka [this message]
2010-02-22  8:24     ` Avi Kivity

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=4B823C9A.2010205@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@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