qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Aurelien Jarno <aurelien@aurel32.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu/target-sparc exec.h op.c op_helper.c op_me...
Date: Sun, 23 Sep 2007 01:11:35 +0200	[thread overview]
Message-ID: <46F5A127.2020502@aurel32.net> (raw)
In-Reply-To: <0069164A-F02D-4512-891F-E55E88E3B4F3@web.de>

Andreas Färber a écrit :
> Am 22.09.2007 um 23:41 schrieb Aurelien Jarno:
> 
>> Aurelien Jarno a écrit :
>>> Thanks, that's helpful, it looks like the "lduba" instructions is not
>>> working correctly in your case. Now I have to find why.
>> I don't really understand, because that is the part of the code (at
>> least from the op point of view) that is almost unchanged. Looking at
>> the code again and again I can't see any problem.
>>
>> Could you please try to find the values of T1 at the end of
>> helper_ld_asi (adding a printf or using gdb). That may help us to
>> understand what is the problem.
> 
> With:
> 
> printf("helper_ld_asi: T1 = %llx\n", T1); // not sure if that's correct?

Yes that is correct.

> I get these two:
> 
> helper_ld_asi: T1 = 5171200000

The correct value here is 51. I don't really understand why this value
is not a 8-bit one, as the memory access is done through ldub_phys().
Could you please verify that helper_ld_asi() is called with the correct
parameters. This should be 0x20 0x1 0x0.

PS: I don't know if I will be able to get internet access in the next 4
days.

-- 
  .''`.  Aurelien Jarno	            | GPG: 1024D/F1BCDB73
 : :' :  Debian developer           | Electrical Engineer
 `. `'   aurel32@debian.org         | aurelien@aurel32.net
   `-    people.debian.org/~aurel32 | www.aurel32.net

  reply	other threads:[~2007-09-22 23:11 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-21 19:10 [Qemu-devel] qemu/target-sparc exec.h op.c op_helper.c op_me Blue Swirl
2007-09-21 19:32 ` Andreas Färber
2007-09-21 20:25   ` Blue Swirl
2007-09-21 20:41     ` Andreas Färber
2007-09-21 20:26   ` Aurelien Jarno
2007-09-21 21:07     ` Aurelien Jarno
2007-09-21 21:20       ` Andreas Färber
2007-09-22 11:49         ` Aurelien Jarno
2007-09-22 12:07           ` Blue Swirl
2007-09-22 13:11           ` Andreas Färber
2007-09-22 17:50             ` Aurelien Jarno
2007-09-22 19:27               ` Andreas Färber
2007-09-22 20:06                 ` Aurelien Jarno
2007-09-22 20:23                   ` Andreas Färber
2007-09-22 20:34                     ` Aurelien Jarno
2007-09-22 21:21                       ` Andreas Färber
2007-09-22 21:41                       ` Aurelien Jarno
2007-09-22 21:58                         ` Andreas Färber
2007-09-22 23:11                           ` Aurelien Jarno [this message]
2007-09-23  8:44                             ` Andreas Färber
2007-09-25 17:45                             ` Andreas Färber
2007-09-26 11:05                               ` Aurelien Jarno
2007-09-28 14:37                                 ` Andreas Färber
  -- strict thread matches above, loose matches on Subject: below --
2008-02-24 14:10 Blue Swirl

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=46F5A127.2020502@aurel32.net \
    --to=aurelien@aurel32.net \
    --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).