From: Artyom Tarasenko <atar4qemu@gmail.com>
To: qemu-devel@nongnu.org
Cc: blauwirbel@gmail.com, Artyom Tarasenko <atar4qemu@gmail.com>
Subject: [Qemu-devel] [PATCH 0/3] sparc64 fixes
Date: Sat, 27 Apr 2013 07:55:10 +0200 [thread overview]
Message-ID: <cover.1366987353.git.atar4qemu@gmail.com> (raw)
Various fixes:
On the real hardware IRQ lines of the PCI bus are not shared.
In the previous QEMU implementation before this series, all PCI devices
used the IRQ line 0. Combined with auto-clearing interrupts this made
the guest OS extremely unstable. The test case is installing
Debian Wheezy / sparc64:
http://tyom.blogspot.de/2013/03/debiansparc64-wheezy-under-qemu-how-to.html
Without the patches the install process hangs at random places between 6% and 60%.
With this series the installation succeeds.
Please note that the patch 3/3 requires updating OpenBIOS.
Artyom Tarasenko (3):
sparc64: allow 64 IRQ lines
sparc64: fix loosing interrupts
sparc64: use direct interrupt mapping for PCI devices
hw/pci-host/apb.c | 118 +++++++++++++++++++++++++++++++++++++++++++---------
hw/sparc64/sun4u.c | 2 +-
2 files changed, 99 insertions(+), 21 deletions(-)
next reply other threads:[~2013-04-27 5:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-27 5:55 Artyom Tarasenko [this message]
2013-04-27 5:55 ` [Qemu-devel] [PATCH 1/3] sparc64: allow 64 IRQ lines Artyom Tarasenko
2013-04-27 5:55 ` [Qemu-devel] [PATCH 2/3] sparc64: fix loosing interrupts Artyom Tarasenko
2013-04-27 5:55 ` [Qemu-devel] [PATCH 3/3] sparc64: use direct interrupt mapping for PCI devices Artyom Tarasenko
2013-04-27 11:44 ` [Qemu-devel] [PATCH 0/3] sparc64 fixes 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=cover.1366987353.git.atar4qemu@gmail.com \
--to=atar4qemu@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.