From: Stefan Weil <weil@mail.berlios.de>
To: "Andreas Färber" <planche2k@googlemail.com>
Cc: hpoussin@reactos.org, Avi Kivity <avi@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] mips_malta: move i8259 initialization after piix4 initialization
Date: Wed, 14 Sep 2011 21:03:23 +0200 [thread overview]
Message-ID: <4E70FA7B.6060908@mail.berlios.de> (raw)
In-Reply-To: <4E70D40D.108@googlemail.com>
Am 14.09.2011 18:19, schrieb Andreas Färber:
> Am 14.09.2011 14:00, schrieb Avi Kivity:
>> On 09/12/2011 04:07 PM, Avi Kivity wrote:
>>> i8259 is an ISA device (or at least, depends on the ISA
>>> infrastructure to
>>> register its ioport); and the ISA bus is supplied by piix4. Later
>>> patches
>>> make this dependency explicit.
>>>
>>> Move the i8259 initialization until after the ISA bus is created; and
>>> supply
>>> a new qemu_irq to PCI initialization, since the i8259 isn't ready
>>> yet. Later
>>> wire the new qemu_irq to the i8259.
>>>
>>
>> Can this please be reviewed? It's in the front of the memory queue
>> logjam.
>
> With or without this patch, the mips and mipsel test images on qemu.org
> produce no output at all, on x64 host.
>
> Andreas
I just tested the mipsel test image on i386 and x64 hosts with the
same result. Adding -d in_asm shows that the linux kernel is started,
but runs in a loop at some point (timer initialization?). Timer interrupts
are still served (attach cross gdb to running emulation).
Could you already bisect this problem? I did not run these tests for
years.
My standard mips tests use debian mips kernels and show no problems.
Stefan
next prev parent reply other threads:[~2011-09-14 19:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 13:07 [Qemu-devel] [PATCH] mips_malta: move i8259 initialization after piix4 initialization Avi Kivity
2011-09-14 12:00 ` Avi Kivity
2011-09-14 16:19 ` Andreas Färber
2011-09-14 19:03 ` Stefan Weil [this message]
2011-09-14 20:17 ` Avi Kivity
2011-09-14 20:52 ` Edgar E. Iglesias
2011-09-15 5:23 ` Stefan Weil
2011-09-18 12:04 ` Avi Kivity
2011-09-15 5:56 ` Stefan Weil
2011-09-14 20:32 ` Richard Henderson
2011-09-14 20:37 ` Avi Kivity
2011-09-14 20:40 ` Richard Henderson
2011-09-16 13:19 ` Anthony Liguori
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=4E70FA7B.6060908@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=avi@redhat.com \
--cc=hpoussin@reactos.org \
--cc=planche2k@googlemail.com \
--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).