qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <laurent@vivier.eu>
To: Richard Henderson <rth@twiddle.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/5] target-m68k patches
Date: Mon, 7 Nov 2016 13:24:20 +0100	[thread overview]
Message-ID: <48c5952a-0f12-bc53-c104-5440f79ffb7b@vivier.eu> (raw)
In-Reply-To: <cb43dc45-d4ee-901e-108c-b68b7eb5e927@twiddle.net>

Le 07/11/2016 à 13:08, Richard Henderson a écrit :
> On 11/06/2016 08:52 PM, Laurent Vivier wrote:
>>> Richard Henderson (4):
>>>   target-m68k: Do not cpu_abort on undefined insns
>>>   target-m68k: Inline shifts
>>>   target-m68k: Implement bitfield ops for registers
>>>   target-m68k: Implement bitfield ops for memory
>>
>> There is something wrong with the bitfield patches, because when I use
>> them instead of the version I use usually I'm not able to boot a
>> container with qemu-m68k (SEGFAULT).
> 
> Ah, too bad.  I was testing with the linux-user-0.3 busybox, but we
> don't yet implement enough to actually execute it.  So the testing
> consisted of maybe 3 or 4 such insns until I reach the fmovemx.  ;-)
> 
> Can you tell if the breakage is limited to the memory patch, or if the
> register patch is also broken?

I need to test more, because if I only apply the register patch, I have
an illegal instruction exception.

If it can help:

sudo QEMU_LOG=in_asm chroot /var/lib/lxc/virtm68k-etch-m68k/rootfs 2>&1
|grep bf
0xf67f9160:  bfextu %d3,27,3,%d1
0xf67f8988:  bftst %d1,30,2
0xf67f2786:  bfins %d0,%a1@,0,2
0xf67eeb56:  bfins %d0,%a2@(824),0,2
0xf67f362c:  bfins %d0,%a2@(384),5,2
0xf67f8b80:  bftst %d1,30,2
0xf67f8b9e:  bftst %d4,30,2
0xf67f8998:  bftst %d0,30,2
0xf67f8998:  bftst %d0,30,2
0xf67f9160:  bfextu %d3,27,3,%d1
0xf67f8f88:  bftst %d4,30,2
0xf67f39d8:  bfins %d0,%a1@(384),5,2
0xf67f3876:  bfclr %a0@(384),5,2

If you want to have a try, this tree is based on tgt-m68k + what is
needed to boot an etch-m68k container.

git://github.com/vivier/qemu-m68k.git for-rth

The working tree is:

git://github.com/vivier/qemu-m68k.git m68k-dev

Thanks,
Laurent

  reply	other threads:[~2016-11-07 12:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-06  6:18 [Qemu-devel] [PATCH 0/5] target-m68k patches Richard Henderson
2016-11-06  6:18 ` [Qemu-devel] [PATCH 1/5] target-m68k: implement 680x0 movem Richard Henderson
2016-11-06 16:52   ` Laurent Vivier
2016-11-06  6:18 ` [Qemu-devel] [PATCH 2/5] target-m68k: Do not cpu_abort on undefined insns Richard Henderson
2016-11-06 16:53   ` Laurent Vivier
2016-11-06  6:18 ` [Qemu-devel] [PATCH 3/5] target-m68k: Inline shifts Richard Henderson
2016-11-06  6:18 ` [Qemu-devel] [PATCH 4/5] target-m68k: Implement bitfield ops for registers Richard Henderson
2016-11-06  6:18 ` [Qemu-devel] [PATCH 5/5] target-m68k: Implement bitfield ops for memory Richard Henderson
2016-11-06 19:52 ` [Qemu-devel] [PATCH 0/5] target-m68k patches Laurent Vivier
2016-11-07 12:08   ` Richard Henderson
2016-11-07 12:24     ` Laurent Vivier [this message]
2016-11-07 13:12       ` Peter Maydell
2016-11-07 13:44         ` Laurent Vivier
2016-11-07 13:50           ` Peter Maydell
2016-11-07 14:00             ` Laurent Vivier

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=48c5952a-0f12-bc53-c104-5440f79ffb7b@vivier.eu \
    --to=laurent@vivier.eu \
    --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).