qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <laurent@vivier.eu>
To: Rob Landley <rob@landley.net>, qemu-devel@nongnu.org
Cc: Finn Thain <fthain@telegraphics.com.au>
Subject: Re: [Qemu-devel] [PULL 0/2] M68k for 2.12 patches
Date: Mon, 2 Apr 2018 21:05:21 +0200	[thread overview]
Message-ID: <e95756ac-f3e8-dc5c-31db-c88fbb37756d@vivier.eu> (raw)
In-Reply-To: <67f4fb22-9ad5-7f41-371a-001d1346fc4f@landley.net>

Le 02/04/2018 à 20:13, Rob Landley a écrit :
> On 03/30/2018 12:00 PM, Laurent Vivier wrote:
>> Le 30/03/2018 à 18:54, Rob Landley a écrit :
>>> On 03/20/2018 04:08 AM, Laurent Vivier wrote:> This series of patches is needed
>>> to fix a problem
>>>> in the m68k translator that can crash QEMU when translation
>>>> cache has too many instructions:
>>>>
>>>>   qemu-m68k: tcg/tcg.c:883: tcg_temp_alloc: Assertion `n < 512' failed.
>>>>   qemu: uncaught target signal 11 (Segmentation fault) - core dumped
>>>>
>>>> I have reproduced it in linux user mode, with "ghc", and in
>>>> system mode with the debian-installer for unstable distro
>>>> from debian-ports.
>>>
>>> If someone wanted to follow along with your "boot linux on qemu-system-m68k"
>>> work on https://github.com/vivier/qemu-m68k, which of the 51 branches should
>>> qemu-system-m68k with like -M q800 or whatever you had working be built from?
>>
>> The branch to use is q800-dev
> 
> There isn't any m68k support in musl-libc yet, so I grabbed my old
> https://github.com/landley/aboriginal project, did a "./build.sh m68k", built
> your q800-dev branch, added the m68k-softmmu from that to the start of the
> $PATH, and ran "more/dev-environment-from-build.sh m68k".
> 
> It booted Linux to a shell prompt, I could wget a file from the internet, and
> /home had the 2 gigabyte ext3 mount from the virtual block device.
> 
> I.E. it works for me. Why is it still out of tree?

Remaining patches need some cleanup before being submitted.

I have to submit some enhancements in the FPU emulation, but as they
modify fpu/softfloat.c, I don't want to put them as is in an m68k pull-req:

	target/m68k: manage FPU exceptions
	softfloat: define floatx80_is_any_nan for m68k
	softfloat: disable floatx80_invalid_encoding() for m68k

I have to add some specific m68k hardware emulation:

	m68k: add via support
	m68k: add video card
	q800: Apple Sound Chip (ASC) emulation
	q800: add Nubus support
	q800: add a dummy SWIM floppy controller
	m68k: define Macintosh Quadra 800

but via support should be rewritten as Mark has introduced a new generic
mos6522 VIA device.

I have to update some existing hardware emulation:

	ESP: add pseudo-DMA as used by Macintosh
	escc: introduce a selector for the register bit
	dp8393x: fix receiving buffer exhaustion
	dp8393x: put DMA temp buffer in the state, not in the stack
	dp8393x: manage big endian bus
	dp8393x: fix dp8393x_receive

So, this only needs some work and time. I hope q800 will be available in
QEMU 2.13.

Thanks,
Laurent

  reply	other threads:[~2018-04-02 19:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-20  9:08 [Qemu-devel] [PULL 0/2] M68k for 2.12 patches Laurent Vivier
2018-03-20  9:08 ` [Qemu-devel] [PULL 1/2] target/m68k: add DisasContext parameter to gen_extend() Laurent Vivier
2018-03-20  9:08 ` [Qemu-devel] [PULL 2/2] target/m68k: add a mechanism to automatically free TCGv Laurent Vivier
2018-03-20 15:43 ` [Qemu-devel] [PULL 0/2] M68k for 2.12 patches Peter Maydell
2018-03-30 16:54 ` Rob Landley
2018-03-30 17:00   ` Laurent Vivier
2018-04-02 18:13     ` Rob Landley
2018-04-02 19:05       ` Laurent Vivier [this message]
2018-04-02 22:35         ` Rob Landley

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=e95756ac-f3e8-dc5c-31db-c88fbb37756d@vivier.eu \
    --to=laurent@vivier.eu \
    --cc=fthain@telegraphics.com.au \
    --cc=qemu-devel@nongnu.org \
    --cc=rob@landley.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).