All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: BALATON Zoltan <balaton@eik.bme.hu>, qemu-devel@nongnu.org
Cc: Programmingkid <programmingkidx@gmail.com>,
	qemu-ppc <qemu-ppc@nongnu.org>,
	"Andreas Färber" <afaerber@suse.de>,
	"Tom Musta" <tommusta@gmail.com>
Subject: Re: [Qemu-devel] Help needed testing on ppc
Date: Tue, 17 Jun 2014 10:42:21 +0200	[thread overview]
Message-ID: <539FFF6D.2070407@suse.de> (raw)
In-Reply-To: <alpine.LMD.2.02.1406170137470.32601@jedlik.phy.bme.hu>


On 17.06.14 01:42, BALATON Zoltan wrote:
> On Thu, 12 Jun 2014, BALATON Zoltan wrote:
>> On Wed, 7 May 2014, Alexander Graf wrote:
>>> On 05/07/2014 05:31 PM, Tom Musta wrote:
>>>> On 5/6/2014 6:17 PM, BALATON Zoltan wrote:
>>>>> On Tue, 6 May 2014, Tom Musta wrote:
>>>>>> (2) Your patch makes some store instructions compliant with the 
>>>>>> most recent ISAs but there are many other instructions that are 
>>>>>> not addressed by the patch.  I think fixing only some will be a 
>>>>>> future source of confusion.>>
>>>> Alex:  do you have an opinion on this?  Are you OK with changing 
>>>> masks for a few stores but not all instructions in general?
>>>
>>> I would like to see someone just test all those load/store 
>>> instructions on old CPUs and see whether they fault. If none faults, 
>>> we should just be consistent and remove them for all. If say a 750 
>>> really only ignores the Rc bit for stwx for some reason we should 
>>> just model it accordingly.
>>
>> To get some answers to this and other questions that are still open 
>> I've made a test program by stripping down yaboot and adding tests to 
>> it so that it should be possible to run from Open Firmware as a boot 
>> loader. It can be found here:
>>
>> http://goliat.eik.bme.hu/~balaton/oftest/
>>
>> The files there are:
>> * oftest - an ELF executable that you can put on some device OF can read
>>        and run it if it were a boot loader ( e.g. 0> boot 
>> hd0,0:\oftest )
>> * oftest.hfs.xz - the same file on an 800k HFS volume that can be put on
>>        e.g. a USB drive or CD then used as the previous one
>> * oftest-src.tar.xz - the source
>>
>> When run from Open Firmware it should print some information about 
>> memory layout, MSR setting, stack location, BAT registers and test 
>> the stwx opcode with and without reserved bit which should help us 
>> understand better the differences between QEMU and real hardware. I 
>> could only test it on QEMU though.
>
> I've got some results (but more are welcome) which can be seen here:
>
> http://goliat.eik.bme.hu/~balaton/oftest/results/
>
> The results show that the stwx instruction with reserved bit set does 
> not change status bits and does not generate an exception on any CPU 
> tested (G3 and G4) so it is most probably just ignored as we thought.

[adding qemu-ppc and tom to CC]

Tom already commented on this. Is there a pattern that matches all the 
indexed load/store instructions or is stwx a one-off?


Alex

  reply	other threads:[~2014-06-17  8:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-06 10:03 [Qemu-devel] Help needed testing on ppc BALATON Zoltan
2014-05-06 12:20 ` Tom Musta
2014-05-06 23:17   ` BALATON Zoltan
2014-05-07 15:31     ` Tom Musta
2014-05-07 16:59       ` Alexander Graf
2014-06-12  0:49         ` BALATON Zoltan
2014-06-16 23:42           ` BALATON Zoltan
2014-06-17  8:42             ` Alexander Graf [this message]
2014-06-17  9:34               ` [Qemu-devel] [Qemu-ppc] " BALATON Zoltan
2014-06-17  9:37                 ` Alexander Graf
2014-06-17 11:05                   ` BALATON Zoltan
2014-06-17 11:54                     ` Tom Musta
2014-06-17 15:17                       ` BALATON Zoltan
2014-06-18 12:40                         ` Tom Musta
2014-06-19 13:21                           ` BALATON Zoltan
2014-06-23 17:07                             ` Alexander Graf
2014-05-20 23:55       ` [Qemu-devel] " BALATON Zoltan

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=539FFF6D.2070407@suse.de \
    --to=agraf@suse.de \
    --cc=afaerber@suse.de \
    --cc=balaton@eik.bme.hu \
    --cc=programmingkidx@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=tommusta@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.