From: BALATON Zoltan <balaton@eik.bme.hu>
To: jasper.lowell@bt.com
Cc: John Snow <jsnow@redhat.com>,
mark.cave-ayland@ilande.co.uk, dgilbert@redhat.com,
atar4qemu@gmail.com, qemu-devel@nongnu.org
Subject: RE: Emulating Solaris 10 on SPARC64 sun4u
Date: Tue, 25 Feb 2020 23:12:18 +0100 (CET) [thread overview]
Message-ID: <alpine.BSF.2.22.395.2002252307210.87116@zero.eik.bme.hu> (raw)
In-Reply-To: <alpine.BSF.2.22.395.2002101546080.56058@zero.eik.bme.hu>
On Mon, 10 Feb 2020, BALATON Zoltan wrote:
> This suggests the common IDE bmdma and ide-cd code is likely OK and problem
> is somewhere in irq routing. What's relevant for this thread and sparc64 is
> that then you should also check interrupt controller and routing if an
> interrupt raised by the IDE controller could get to the CPU in your case as
> that could be where the problem is and maybe not in common code as I've
> suspected before.
I can now confirm that my problem was related to IRQ routing as noted
here:
https://lists.nongnu.org/archive/html/qemu-devel/2020-02/msg07225.html
so any similar problem for Solaris is not related to this and common IDE
and BMDMA code are likely OK so you may want to check IRQ handling in
board and chipset emulation in case the cause is similar to what I had.
Regards,
BALATON Zoltan
next prev parent reply other threads:[~2020-02-25 22:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 6:31 Emulating Solaris 10 on SPARC64 sun4u jasper.lowell
2020-02-05 17:33 ` Dr. David Alan Gilbert
2020-02-07 5:43 ` jasper.lowell
2020-02-08 0:03 ` BALATON Zoltan
2020-02-10 15:38 ` BALATON Zoltan
2020-02-10 19:04 ` John Snow
2020-02-10 22:32 ` Missing IRQ with bmdma on ppc/mips/sparc? (was: Re: Emulating Solaris 10 on SPARC64 sun4u) BALATON Zoltan
2020-02-25 20:55 ` IDE IRQ problem after UDMA enabled " BALATON Zoltan
2020-02-25 22:00 ` BALATON Zoltan
2020-02-25 22:12 ` BALATON Zoltan [this message]
2020-02-09 11:26 ` Emulating Solaris 10 on SPARC64 sun4u Mark Cave-Ayland
2020-02-19 3:42 ` jasper.lowell
2020-02-19 18:54 ` BALATON Zoltan
2020-02-19 20:10 ` BALATON Zoltan
2020-02-21 19:53 ` Dr. David Alan Gilbert
2020-02-28 22:05 ` BALATON Zoltan
2020-03-01 0:15 ` BALATON Zoltan
2020-05-07 14:29 ` jasper.lowell
2020-05-07 15:02 ` Artyom Tarasenko
2020-05-08 2:33 ` jasper.lowell
2020-05-08 8:51 ` Peter Tribble
2020-05-08 13:45 ` Artyom Tarasenko
2020-05-10 2:46 ` jasper.lowell
2020-05-10 9:22 ` Mark Cave-Ayland
2020-05-17 7:57 ` jasper.lowell
2020-05-17 12:37 ` Artyom Tarasenko
2020-05-18 2:56 ` jasper.lowell
2020-05-20 17:44 ` Mike Russo
2020-05-07 18:54 ` BALATON Zoltan
2020-05-08 2:55 ` jasper.lowell
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=alpine.BSF.2.22.395.2002252307210.87116@zero.eik.bme.hu \
--to=balaton@eik.bme.hu \
--cc=atar4qemu@gmail.com \
--cc=dgilbert@redhat.com \
--cc=jasper.lowell@bt.com \
--cc=jsnow@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--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).