From: Jan Kiszka <jan.kiszka@web.de>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, KVM list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Merging kvm-apic into qemu-kvm
Date: Sun, 29 Jan 2012 12:15:09 +0100 [thread overview]
Message-ID: <4F252A3D.8000905@web.de> (raw)
In-Reply-To: <4F252981.7000708@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 938 bytes --]
On 2012-01-29 12:12, Avi Kivity wrote:
> On 01/29/2012 12:33 PM, Avi Kivity wrote:
>> On 01/27/2012 11:34 PM, Jan Kiszka wrote:
>>>>
>>>> Yes please. It's halfway through autotest and looks good. Even if I
>>>> have to change it, we can 'git rebase -p --onto' your branch (though I
>>>> doubt it will be necessary).
>>>
>>> Done, see
>>>
>>> git://git.kiszka.org/qemu-kvm.git queues/qemu-merge
>>>
>>> Only moderately tested so far, I'm counting on your machinery.
>>>
>>
>> Pulled, thanks a lot. Testing now.
>>
>
> 1. The default shows apic/ioapic in 'info qtree' (no kvm-), yet I see
> the vcpu threads in kvm_vcpu_block(), implying in-kernel irqchip.
> Something's wrong.
Nope, that's just the behavior of the original qemu-kvm irqchip (i.e.
kvm extension is merged into the emulated device). Nothing changed here
so far.
>
> 2. Migration is broken.
OK, that's new. A trivial scenario?
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-01-29 11:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 15:15 [Qemu-devel] Merging kvm-apic into qemu-kvm Avi Kivity
2012-01-26 15:25 ` Jan Kiszka
2012-01-26 15:32 ` Jan Kiszka
2012-01-26 15:39 ` Avi Kivity
2012-01-26 15:45 ` Jan Kiszka
2012-01-26 15:49 ` Avi Kivity
2012-01-27 21:34 ` Jan Kiszka
2012-01-29 10:33 ` Avi Kivity
2012-01-29 11:12 ` Avi Kivity
2012-01-29 11:15 ` Jan Kiszka [this message]
2012-01-29 11:18 ` Avi Kivity
2012-01-29 11:20 ` Jan Kiszka
2012-01-29 11:54 ` Jan Kiszka
2012-01-29 12:01 ` Avi Kivity
2012-01-29 12:02 ` Jan Kiszka
2012-01-29 12:04 ` Avi Kivity
2012-01-29 12:06 ` Avi Kivity
2012-01-29 12:35 ` Avi Kivity
2012-01-29 15:56 ` Avi Kivity
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=4F252A3D.8000905@web.de \
--to=jan.kiszka@web.de \
--cc=avi@redhat.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).