From: Michael Tokarev <mjt@tls.msk.ru>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: carl@nextdayvideo.com, Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] (i386) TCG is broken in 1.5-rc0 with guest kernel 3.2?
Date: Wed, 08 May 2013 13:16:31 +0400 [thread overview]
Message-ID: <518A17EF.2020909@msgid.tls.msk.ru> (raw)
In-Reply-To: <518A14F4.80907@msgid.tls.msk.ru>
08.05.2013 13:03, Michael Tokarev wrote:
> This is broken by the following:
>
> commit 57eb0cc85469a8948d1036ab830951e63aa32f66
> Author: Richard Henderson <rth@twiddle.net>
> Date: Wed Jan 16 11:00:14 2013 -0800
>
> target-i386: expand cmov via movcond
>
> Signed-off-by: Richard Henderson <rth@twiddle.net>
This change works fine on amd64. Only i386 (32bit x86)
userspace is broken. Running amd64 guest kernel inside
in all cases.
Thanks,
/mjt
next prev parent reply other threads:[~2013-05-08 9:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 8:22 [Qemu-devel] (i386) TCG is broken in 1.5-rc0 with guest kernel 3.2? Michael Tokarev
2013-05-08 9:03 ` Michael Tokarev
2013-05-08 9:16 ` Michael Tokarev [this message]
2013-05-09 16:43 ` Richard Henderson
2013-05-09 16:52 ` Aurelien Jarno
2013-05-09 17:11 ` Michael Tokarev
2013-05-08 10:09 ` Richard W.M. Jones
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=518A17EF.2020909@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=carl@nextdayvideo.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).