From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Sparc guest - SCSI
Date: Sat, 4 Aug 2007 13:53:40 +0300 [thread overview]
Message-ID: <f43fc5580708040353s24df37adg84c0c1cf07b9c084@mail.gmail.com> (raw)
In-Reply-To: <f43fc5580708031235w15cc3510oa91b6fb572ccd980@mail.gmail.com>
I reworked the interrupt handling so that both e2fsck and SMP work.
Previously there may have been lost or spurious interrupts, now they
should be fixed. I pushed the interrupt priority handling from
SLAVIO to CPU.
prev parent reply other threads:[~2007-08-04 10:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 8:45 [Qemu-devel] Sparc guest - SCSI Nigel Horne
2007-08-03 10:27 ` Andreas Färber
2007-08-03 10:42 ` Nigel Horne
2007-08-03 11:30 ` Andreas Färber
2007-08-03 12:02 ` Nigel Horne
2007-08-03 14:21 ` Andreas Färber
2007-08-03 11:52 ` Aurelien Jarno
2007-08-03 13:50 ` Andreas Färber
2007-08-03 14:15 ` Aurelien Jarno
2007-08-03 14:36 ` Andreas Färber
2007-08-03 14:54 ` Aurelien Jarno
2007-08-03 15:31 ` Andreas Färber
2007-08-03 19:35 ` Blue Swirl
2007-08-04 10:53 ` Blue Swirl [this message]
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=f43fc5580708040353s24df37adg84c0c1cf07b9c084@mail.gmail.com \
--to=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).