From: Gerd Hoffmann <kraxel@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Glauber Costa <glommer@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [Qemu-commits] [COMMIT 733318e] don't call cpu_sychronize_state from reset handlers
Date: Thu, 10 Sep 2009 12:16:11 +0200 [thread overview]
Message-ID: <4AA8D1EB.4040909@redhat.com> (raw)
In-Reply-To: <200909092236.n89MaDVc020267@d01av01.pok.ibm.com>
On 09/10/09 00:37, Anthony Liguori wrote:
> From: Glauber Costa<glommer@redhat.com>
>
> Doing this will make the vcpu ioctl be issued from the I/O thread, instead
> of cpu thread. The correct behaviour is to call it from within the cpu thread,
> as soon as we are ready to go.
With this patch booting rawhide stops working.
The kernel has trouble setting up the timer and stops after hpet setup:
[ ... ]
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
..MP-BIOS bug: 8254 timer not connected to IO-APIC
...trying to set up timer (IRQ0) through the 8259A ...
..... (found apic 0 pin 2) ...
....... failed.
...trying to set up timer as Virtual Wire IRQ...
..... failed.
...trying to set up timer as ExtINT IRQ...
..... works.
[ ... ]
hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
hpet0: 3 comparators, 64-bit 100.000000 MHz counter
[ kernel hangs here ]
cheers,
Gerd
next parent reply other threads:[~2009-09-10 10:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200909092236.n89MaDVc020267@d01av01.pok.ibm.com>
2009-09-10 10:16 ` Gerd Hoffmann [this message]
2009-09-10 11:44 ` [Qemu-devel] Re: [Qemu-commits] [COMMIT 733318e] don't call cpu_sychronize_state from reset handlers Avi Kivity
2009-09-10 12:29 ` Glauber Costa
2009-09-11 11:15 ` [Qemu-devel] " Jan Kiszka
2009-09-11 11:43 ` Glauber Costa
2009-09-11 11:52 ` Jan Kiszka
2009-09-11 12:06 ` Glauber Costa
2009-09-11 12:28 ` Jan Kiszka
2009-09-11 14:28 ` Glauber Costa
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=4AA8D1EB.4040909@redhat.com \
--to=kraxel@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=glommer@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).