From: Aurelien Jarno <aurelien@aurel32.net>
To: chen huacai <zltjiangshi@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [BUG?] Problem when emulate mips target on mips host
Date: Fri, 16 Jul 2010 14:27:41 +0200 [thread overview]
Message-ID: <4C40503D.6090709@aurel32.net> (raw)
In-Reply-To: <AANLkTinLAqz50BbqYyeyN2unozECS2CX7NZwL3QEfOON@mail.gmail.com>
chen huacai a écrit :
> Thank you for your information.
> I'am a little confusing, cacheflush syscall you mentioned is in guest
> or in host?
> If you means syscall in guest, why x86 host can boot mips guest?
> If you means syscall in host, why qemu-0.9.x doesn't crash?
>
On the host. I guess qemu-0.9.x doesn't crash, because it's not using
TCG, so it doesn't write the code to memory the same way.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
next prev parent reply other threads:[~2010-07-16 12:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 14:35 [Qemu-devel] [BUG?] Problem when emulate mips target on mips host chen huacai
2010-07-15 15:00 ` [Qemu-devel] " Aurelien Jarno
2010-07-16 11:07 ` chen huacai
2010-07-16 12:27 ` Aurelien Jarno [this message]
2010-07-18 1:53 ` chen huacai
2010-07-18 18:31 ` Aurelien Jarno
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=4C40503D.6090709@aurel32.net \
--to=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
--cc=zltjiangshi@gmail.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;
as well as URLs for NNTP newsgroup(s).