From: Artyom Tarasenko <atar4qemu@googlemail.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: sparc32 do not clear interrupts when masking
Date: Sun, 17 Jan 2010 19:42:11 +0100 [thread overview]
Message-ID: <fb8d4f71001171042x76db53c4m11ef9a621d432c6f@mail.gmail.com> (raw)
In-Reply-To: <f43fc5581001160110n7d8e2bc1q7f51fbada5ffb8e1@mail.gmail.com>
2010/1/16 Blue Swirl <blauwirbel@gmail.com>:
> On Sat, Jan 16, 2010 at 8:47 AM, Blue Swirl <blauwirbel@gmail.com> wrote:
>> On Sat, Jan 16, 2010 at 8:16 AM, Blue Swirl <blauwirbel@gmail.com> wrote:
>>> On Fri, Jan 15, 2010 at 10:37 PM, Artyom Tarasenko
>>> <atar4qemu@googlemail.com> wrote:
>>>> Don't clear interrupts on disabling, because
>>>> * Sun4M_SystemArchitecture_edited2.pdf doesn't describe
>>>> that masking or un-masking IRQ shall clear pending ones.
>>>>
>>>> * Field tests also show that SPARCstation-20 doesn't
>>>> clear them.
>>>
>>> Awesome work!
>>>
>>>> * The patch makes Solaris 2.5.1/2.6 boot ~1500 times
>>>> faster (~20 seconds instead of ~8 hours)
>>>
>>> Unfortunately there is some problem with the patch (or more likely
>>> there is some other bug that this uncovers), because all my Linux test
>>> now panic. NetBSD and OpenBSD are unaffected.
>>>
>>> For example, sparc-test:
>>> eth0: LANCE 52:54:00:12:34:56
>>> esp0: no command in esp_handle()
>>> Kernel panic - not syncing: esp_handle: current_SC == penguin within interrupt!
>>> <0>Press L1-A to return to the boot prom
>>>
>>> The bug may be in ESP interrupt handling (or in the interrupt chain
>>> between ESP, DMA controller and interrupt controller) as the panic
>>> always happens in ESP probe.
>>
>> In fact the bug was that OpenBIOS didn't clear ESP interrupts after
>> issuing commands, so the IRQ line was left raised which confused
>> Linux.
>>
>
> Thanks, applied. I fixed the OpenBIOS bug and updated images in pc-bios.
Looks like this version of the OpenBIOS has a sort of a regression: it
doesn't recognize
NetBSD 1.3.3 miniroot anymore:
qemu-system-sparc -nographic -hda ../images/miniroot-133.fs -m 64 -M SS-20
Welcome to OpenBIOS v1.0 built on Jan 16 2010 08:54
Type 'help' for detailed information
[sparc] Booting file 'disk' with parameters ''
Trying disk (disk)
Trying disk:d (disk:d)
Unsupported image format
I say "sort of" because it may be the correct behavior: due to the bad
disk labels OBP doesn't boot miniroots either.
On the other hand it doesn't recognize Solaris cdroms too:
0 > boot cdrom
[sparc] Booting file 'cdrom' with parameters ''
Trying cdrom (cdrom)
Trying cdrom:d (cdrom:d)
Unsupported image format
ok
--
Regards,
Artyom Tarasenko
solaris/sparc under qemu blog: http://tyom.blogspot.com/
next prev parent reply other threads:[~2010-01-17 18:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-15 22:37 [Qemu-devel] sparc32 do not clear interrupts when masking Artyom Tarasenko
2010-01-16 8:16 ` [Qemu-devel] " Blue Swirl
2010-01-16 8:47 ` Blue Swirl
2010-01-16 9:10 ` Blue Swirl
2010-01-16 9:31 ` Blue Swirl
2010-01-17 18:42 ` Artyom Tarasenko [this message]
2010-01-17 19:51 ` 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=fb8d4f71001171042x76db53c4m11ef9a621d432c6f@mail.gmail.com \
--to=atar4qemu@googlemail.com \
--cc=blauwirbel@gmail.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).