From: Gleb Natapov <gleb@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] KVM: Windows 64-bit troubles with user space irqchip
Date: Sun, 6 Feb 2011 12:28:23 +0200 [thread overview]
Message-ID: <20110206102823.GA14984@redhat.com> (raw)
In-Reply-To: <4D4E7760.2050601@redhat.com>
On Sun, Feb 06, 2011 at 12:26:40PM +0200, Avi Kivity wrote:
> On 02/03/2011 04:15 PM, Gleb Natapov wrote:
> >>
> >> Maybe this is true for the in-kernel model, but I don't see the issue
> >> (anymore) for the way user space works.
> >>
> >With patch below I can boot Windows7.
> >
> >diff --git a/hw/apic.c b/hw/apic.c
> >index 146deca..fdcac88 100644
> >--- a/hw/apic.c
> >+++ b/hw/apic.c
> >@@ -600,7 +600,7 @@ int apic_get_interrupt(DeviceState *d)
> > intno = get_highest_priority_int(s->irr);
> > if (intno< 0)
> > return -1;
> >- if (s->tpr&& intno<= s->tpr)
> >+ if ((s->tpr>> 4)&& (intno>> 4)<= (s->tpr>> 4))
> > return s->spurious_vec& 0xff;
> > reset_bit(s->irr, intno);
> > set_bit(s->isr, intno);
>
> That still allows interrupts that have higher priority than the TPR,
> but lower priority than interrupts in the ISR to be injected. I
> think we need to use the PPR here (same as apic_update_irq()).
>
We shouldn't get here if isr is non-empty, but see the patch I posted
today to qemu-devel. It does what you say anyway.
--
Gleb.
prev parent reply other threads:[~2011-02-06 10:28 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 18:02 [Qemu-devel] KVM: Windows 64-bit troubles with user space irqchip Jan Kiszka
2011-02-02 11:55 ` Gleb Natapov
2011-02-02 11:58 ` Jan Kiszka
2011-02-02 12:35 ` Gleb Natapov
2011-02-02 12:50 ` Jan Kiszka
2011-02-02 13:05 ` Avi Kivity
2011-02-02 13:09 ` Jan Kiszka
2011-02-02 13:11 ` Gleb Natapov
2011-02-02 13:14 ` Avi Kivity
2011-02-02 13:18 ` Gleb Natapov
2011-02-02 14:30 ` Jan Kiszka
2011-02-02 14:35 ` Avi Kivity
2011-02-02 14:43 ` Jan Kiszka
2011-02-02 14:52 ` Jan Kiszka
2011-02-02 15:09 ` Avi Kivity
2011-02-02 15:35 ` Jan Kiszka
2011-02-02 15:44 ` Avi Kivity
2011-02-02 15:46 ` Gleb Natapov
2011-02-02 15:52 ` Jan Kiszka
2011-02-02 16:29 ` Gleb Natapov
2011-02-02 16:36 ` Jan Kiszka
2011-02-02 16:39 ` Gleb Natapov
2011-02-02 16:51 ` Jan Kiszka
2011-02-03 7:42 ` Gleb Natapov
2011-02-03 9:31 ` Jan Kiszka
2011-02-03 8:18 ` Avi Kivity
2011-02-03 9:32 ` Jan Kiszka
2011-02-03 10:01 ` Avi Kivity
2011-02-03 10:14 ` Jan Kiszka
2011-02-03 10:04 ` Marcelo Tosatti
2011-02-03 10:11 ` Jan Kiszka
2011-02-03 14:15 ` Gleb Natapov
2011-02-03 14:27 ` Jan Kiszka
2011-02-06 10:26 ` Avi Kivity
2011-02-06 10:28 ` Gleb Natapov [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=20110206102823.GA14984@redhat.com \
--to=gleb@redhat.com \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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).