qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: michael <trimarchi@gandalf.sssup.it>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] sh4 linux user emulation on an x86_64 system
Date: Wed, 15 Oct 2008 22:53:11 +0200	[thread overview]
Message-ID: <48F65837.90500@gandalf.sssup.it> (raw)
In-Reply-To: <20081015144403.Y48494@stanley.csl.cornell.edu>

Vince Weaver wrote:
> Hello
>
>> On Wed, 15 Oct 2008, michael wrote:
>> qemu-sh4-32 I don't have problems. I have the log and the program run 
>> ok.
>>
>> If I recompile for the qemu-sh4-64 the system crash. I find the 
>> reason of the
>
> I have nothing useful to add, except that I have been trying to track 
> down a very similar problem with qemu-cris.  It works fine on x86, but 
> gets stuck in x86-64 due to the PC getting mis-set.  The problem seems 
> possibly related to the exception handling code which uses longjmp.  
> Maybe the problems are related.
>
> Vince
>
In the user-mode I see that the expection handling just set the 
expeciont reason to -1. I will try to
track down the problem. I don't find how the tcg avoid the use of low 
part of a register that is used
used for special purpose. The x86_64 has the notion only of the 64bit 
register but a 64bit register
can be used only in the low part. Another thing is the define:

#define CODE_GEN_ALIGN           16 /* must be >= of the size of a 
icache line */

In the x86_64 is not 64?

Regards Michael



>
>

  reply	other threads:[~2008-10-15 20:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-15 17:49 [Qemu-devel] sh4 linux user emulation on an x86_64 system michael
2008-10-15 18:46 ` Vince Weaver
2008-10-15 20:53   ` michael [this message]
2008-10-20 11:31 ` [Qemu-devel] [PATCH] SH: Fix struct target_stat64 for 64bit host takasi-y
2008-10-20 13:52   ` [Qemu-devel] " michael
2008-10-20 17:18   ` [Qemu-devel] " michael
2008-10-20 17:35   ` michael
2008-10-21  3:48     ` [Qemu-devel] " takasi-y
2008-10-26 15:37   ` [Qemu-devel] [PATCH] take2. " takasi-y
2009-01-30 19:48     ` 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=48F65837.90500@gandalf.sssup.it \
    --to=trimarchi@gandalf.sssup.it \
    --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).