From: tsnsaito@gmail.com
To: Artyom Tarasenko <atar4qemu@gmail.com>
Cc: blauwirbel@gmail.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] fix disabling interrupts in sun4u
Date: Thu, 28 Jul 2011 21:03:45 +0900 [thread overview]
Message-ID: <4e315024.11948e0a.4077.2795@mx.google.com> (raw)
In-Reply-To: <CACXAS8DAn3mEeSb2Xhr0Xk_sxeD=_V5ODMkX0QV=egfz0sk_ZQ@mail.gmail.com>
At Thu, 28 Jul 2011 13:51:08 +0200,
Artyom Tarasenko wrote:
> On Thu, Jul 28, 2011 at 12:31 PM, <tsnsaito@gmail.com> wrote:
> > Hi,
> >
> > At Mon, 25 Jul 2011 19:22:38 +0200,
> > Artyom Tarasenko wrote:
> >
> >> clear interrupt request if the interrupt priority < CPU pil
> >> clear hardware interrupt request if interrupts are disabled
> >
> > Not directly related to the fix, but I'd like to note a problem
> > of hw/sun4u.c interrupt code:
> >
> > The interrupt code probably mixes hardware interrupts and
> > software interrupts.
> > %pil is for software interrupts (interrupt_level_n traps).
> > %pil can not mask hardware interrupts (interrupt_vector traps);
> > the CPU raises interrupt_vector traps even on %pil=15.
> > But in cpu_check_irqs() and cpu_set_irq(), hardware interrupts
> > seem to be masked by %pil.
>
> The interrupt_vector traps are currently not implemented, are they?
> So it's hard to tell whether they are masked.
Yes, interrupt_vector is not implemented yet.
I failed to explain the problem.
The problem is that cpu_set_irqs() should raise interrupt_vector
traps but it raises interrupt_level_n traps actually.
sun4uv_init() calls qemu_allocate_irqs() with cpu_set_irq as
the 1st argument. The allocated irqs (the irq variable) are
passed to pci_apb_init(). APB should generate interrupt_vector
traps (hardware interrupts), not the interrupt_vector_n traps.
The interrupts from APB would be reported by cpu_set_irq(),
but cpu_set_irq() seems to generate interrupt_vector_n traps.
> >> Signed-off-by: Artyom Tarasenko <atar4qemu@gmail.com>
> >> ---
> >> hw/sun4u.c | 6 ++++--
> >> 1 files changed, 4 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/hw/sun4u.c b/hw/sun4u.c
> >> index d7dcaf0..7f95aeb 100644
> >> --- a/hw/sun4u.c
> >> +++ b/hw/sun4u.c
> >> @@ -255,7 +255,7 @@ void cpu_check_irqs(CPUState *env)
> >> pil |= 1 << 14;
> >> }
> >>
> >> - if (!pil) {
> >> + if (pil < (2 << env->psrpil)){
> >> if (env->interrupt_request & CPU_INTERRUPT_HARD) {
> >> CPUIRQ_DPRINTF("Reset CPU IRQ (current interrupt %x)\n",
> >> env->interrupt_index);
> >> @@ -287,10 +287,12 @@ void cpu_check_irqs(CPUState *env)
> >> break;
> >> }
> >> }
> >> - } else {
> >> + } else if (env->interrupt_request & CPU_INTERRUPT_HARD) {
> >> CPUIRQ_DPRINTF("Interrupts disabled, pil=%08x pil_in=%08x softint=%08x "
> >> "current interrupt %x\n",
> >> pil, env->pil_in, env->softint, env->interrupt_index);
> >> + env->interrupt_index = 0;
> >> + cpu_reset_interrupt(env, CPU_INTERRUPT_HARD);
> >> }
> >> }
> >>
> >> --
> >> 1.7.3.4
> >
> >
> > ----
> > Tsuneo Saito <tsnsaito@gmail.com>
> >
>
>
>
> --
> Regards,
> Artyom Tarasenko
>
> solaris/sparc under qemu blog: http://tyom.blogspot.com/
----
Tsuneo Saito <tsnsaito@gmail.com>
next prev parent reply other threads:[~2011-07-28 12:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-25 17:22 [Qemu-devel] [PATCH] fix disabling interrupts in sun4u Artyom Tarasenko
2011-07-28 10:31 ` tsnsaito
2011-07-28 11:51 ` Artyom Tarasenko
2011-07-28 12:03 ` tsnsaito [this message]
2011-07-28 12:10 ` Tsuneo Saito
2011-07-28 12:55 ` Artyom Tarasenko
2011-07-28 12:50 ` Artyom Tarasenko
2011-07-28 13:40 ` tsnsaito
2011-07-28 14:44 ` Artyom Tarasenko
2011-07-29 1:21 ` tsnsaito
2011-07-30 9:28 ` Blue Swirl
2011-07-30 9:09 ` Blue Swirl
2011-07-30 12:31 ` Artyom Tarasenko
2011-07-30 13:25 ` Blue Swirl
2011-07-30 20:19 ` Artyom Tarasenko
2011-07-30 20:32 ` Blue Swirl
2011-07-30 20:58 ` Artyom Tarasenko
2011-07-30 21:13 ` Blue Swirl
2011-08-28 11:39 ` 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=4e315024.11948e0a.4077.2795@mx.google.com \
--to=tsnsaito@gmail.com \
--cc=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 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).