qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.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: [Qemu-devel] Re: [PATCH][uq/master] KVM: x86: Fix eflags corruption in kvm mode
Date: Mon, 22 Feb 2010 10:24:04 +0200	[thread overview]
Message-ID: <4B823F24.7060406@redhat.com> (raw)
In-Reply-To: <4B823C9A.2010205@siemens.com>

On 02/22/2010 10:13 AM, Jan Kiszka wrote:
> 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.
>
>    

Agreed.

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

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-19 17:21 [Qemu-devel] [PATCH][uq/master] KVM: x86: Fix eflags corruption in kvm mode Jan Kiszka
2010-02-21  9:14 ` [Qemu-devel] " Avi Kivity
2010-02-22  8:13   ` Jan Kiszka
2010-02-22  8:24     ` Avi Kivity [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=4B823F24.7060406@redhat.com \
    --to=avi@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=jan.kiszka@siemens.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;
as well as URLs for NNTP newsgroup(s).