From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: kvm <kvm@vger.kernel.org>, Gleb Natapov <gleb@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] KVM: Windows 64-bit troubles with user space irqchip
Date: Wed, 02 Feb 2011 17:09:01 +0200 [thread overview]
Message-ID: <4D49738D.7080404@redhat.com> (raw)
In-Reply-To: <4D496FA6.8070301@siemens.com>
On 02/02/2011 04:52 PM, Jan Kiszka wrote:
> On 2011-02-02 15:43, Jan Kiszka wrote:
> > On 2011-02-02 15:35, Avi Kivity wrote:
> >> On 02/02/2011 04:30 PM, Jan Kiszka wrote:
> >>> On 2011-02-02 14:05, Avi Kivity wrote:
> >>>> On 02/02/2011 02:50 PM, Jan Kiszka wrote:
> >>>>>>>
> >>>>>> Opps, -smp 1. With -smp 2 it boot almost completely and then hangs.
> >>>>>
> >>>>> Ah, good (or not good). With Windows 2003 Server, I actually get a Blue
> >>>>> Screen (Stop 0x000000b8).
> >>>>
> >>>> Userspace APIC is broken since it may run with an outdated cr8, does
> >>>> reverting 27a4f7976d5 help?
> >>>
> >>> Can you elaborate on what is broken? The way hw/apic.c maintains the
> >>> tpr? Would it make sense to compare this against the in-kernel model? Or
> >>> do you mean something else?
> >>
> >> The problem, IIRC, was that we look up the TPR but it may already have
> >> been changed by the running vcpu. Not 100% sure.
> >>
> >> If that is indeed the problem then the fix would be to process the APIC
> >> in vcpu context (which is what the kernel does - we set a bit in the IRR
> >> and all further processing is synchronous).
> >
> > You mean: user space changes the tpr value while the vcpu is in KVM_RUN,
> > then we return from the kernel and overwrite the tpr in the apic with
> > the vcpu's view, right?
>
> Hmm, probably rather that there is a discrepancy between tpr and irr.
> The latter is changed asynchronously /wrt to the vcpu, the former /wrt
> the user space device model.
And yet, both are synchronized via qemu_mutex. So we're still missing
something in this picture.
> Run apic_set_irq on the vcpu?
static void apic_set_irq(APICState *s, int vector_num, int trigger_mode)
{
apic_irq_delivered += !get_bit(s->irr, vector_num);
trace_apic_set_irq(apic_irq_delivered);
set_bit(s->irr, vector_num);
This is even more async with kernel irqchip
if (trigger_mode)
set_bit(s->tmr, vector_num);
else
reset_bit(s->tmr, vector_num);
This is protected by qemu_mutex
apic_update_irq(s);
This will be run the next time the vcpu exits, via apic_get_interrupt().
}
Did you check whether reverting that commit helps?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-02-02 15:09 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 [this message]
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
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=4D49738D.7080404@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--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).