From: "Blue Swirl" <blauwirbel@gmail.com>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu/hw slavio_intctl.c slavio_timer.c sun4m.c
Date: Tue, 1 Jan 2008 22:00:32 +0200 [thread overview]
Message-ID: <f43fc5580801011200p2c9f39e2k48da5d3f429a3ed4@mail.gmail.com> (raw)
In-Reply-To: <20080101192515.GA30183@volta.aurel32.net>
On 1/1/08, Aurelien Jarno <aurelien@aurel32.net> wrote:
> On Sat, Dec 29, 2007 at 08:09:57PM +0000, Blue Swirl wrote:
> > CVSROOT: /cvsroot/qemu
> > Module name: qemu
> > Changes by: Blue Swirl <blueswir1> 07/12/29 20:09:57
> >
> > Modified files:
> > hw : slavio_intctl.c slavio_timer.c sun4m.c
> >
> > Log message:
> > Fix CPU timer interrupts
> >
> > CVSWeb URLs:
> > http://cvs.savannah.gnu.org/viewcvs/qemu/hw/slavio_intctl.c?cvsroot=qemu&r1=1.26&r2=1.27
> > http://cvs.savannah.gnu.org/viewcvs/qemu/hw/slavio_timer.c?cvsroot=qemu&r1=1.26&r2=1.27
> > http://cvs.savannah.gnu.org/viewcvs/qemu/hw/sun4m.c?cvsroot=qemu&r1=1.76&r2=1.77
> >
>
> Unfortunately this commit has broken SS-5 running Linux:
Thanks for the report, I can reproduce the bug. What a strange error!
The following patch hides the problem, but it also un-fixes the CPU
timer. I have to think of a better solution.
diff -u -r1.28 slavio_intctl.c
--- hw/slavio_intctl.c 1 Jan 2008 17:06:38 -0000 1.28
+++ hw/slavio_intctl.c 1 Jan 2008 19:52:22 -0000
@@ -257,7 +257,7 @@
if (pending & (1 << j))
pil_pending |= 1 << s->intbit_to_level[j];
}
- pil_pending |= s->intreg_pending[i] & CPU_HARDIRQ_MASK;
+ //pil_pending |= s->intreg_pending[i] & CPU_HARDIRQ_MASK;
}
pil_pending |= (s->intreg_pending[i] & CPU_SOFTIRQ_MASK) >> 16;
next prev parent reply other threads:[~2008-01-01 20:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-29 20:09 [Qemu-devel] qemu/hw slavio_intctl.c slavio_timer.c sun4m.c Blue Swirl
2008-01-01 19:25 ` Aurelien Jarno
2008-01-01 20:00 ` Blue Swirl [this message]
2008-01-01 20:25 ` Andreas Färber
2008-01-01 21:00 ` Blue Swirl
2008-01-01 21:26 ` Aurelien Jarno
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=f43fc5580801011200p2c9f39e2k48da5d3f429a3ed4@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=aurelien@aurel32.net \
--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).