From: Jan Kiszka <jan.kiszka@siemens.com>
To: Chris Wright <chrisw@redhat.com>
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: KVM call minutes for Mar 8
Date: Tue, 08 Mar 2011 17:51:03 +0100 [thread overview]
Message-ID: <4D765E77.4020406@siemens.com> (raw)
In-Reply-To: <20110308155024.GA10392@x200.localdomain>
On 2011-03-08 16:50, Chris Wright wrote:
> iothread merge?
> - progressing slowly, marcelo working on it
> - have found regressions (signal handling code) (ifdef'd away for now)
The regressions will automagically go away (to be replaced with others
then...) when the switch of qemu-kvm to upstream bits is performed. They
were related to qemu-kvm implementing iothread on top of non-threaded
qemu and /me not looking careful enough on the implications.
How this switch may look like can be seen here (slightly outdated version):
http://git.kiszka.org/?p=qemu-kvm.git;a=shortlog;h=refs/heads/queues/qemu-kvm-merge
git://git.kiszka.org/qemu-kvm.git queues/qemu-kvm-merge
Part V of KVM upstream patches is under review ATM. I can post v2 if no
one has further remarks. Then we could start with the review/merge work
on qemu-kvm.
The next time upstream will be involved again would be when preparing
its device models and adding "-machine xxx,kvm-irqchip=..." for
in-kernel irqchip support. That's more work, but it should not affect
the execution model anymore.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Chris Wright <chrisw@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: KVM call minutes for Mar 8
Date: Tue, 08 Mar 2011 17:51:03 +0100 [thread overview]
Message-ID: <4D765E77.4020406@siemens.com> (raw)
In-Reply-To: <20110308155024.GA10392@x200.localdomain>
On 2011-03-08 16:50, Chris Wright wrote:
> iothread merge?
> - progressing slowly, marcelo working on it
> - have found regressions (signal handling code) (ifdef'd away for now)
The regressions will automagically go away (to be replaced with others
then...) when the switch of qemu-kvm to upstream bits is performed. They
were related to qemu-kvm implementing iothread on top of non-threaded
qemu and /me not looking careful enough on the implications.
How this switch may look like can be seen here (slightly outdated version):
http://git.kiszka.org/?p=qemu-kvm.git;a=shortlog;h=refs/heads/queues/qemu-kvm-merge
git://git.kiszka.org/qemu-kvm.git queues/qemu-kvm-merge
Part V of KVM upstream patches is under review ATM. I can post v2 if no
one has further remarks. Then we could start with the review/merge work
on qemu-kvm.
The next time upstream will be involved again would be when preparing
its device models and adding "-machine xxx,kvm-irqchip=..." for
in-kernel irqchip support. That's more work, but it should not affect
the execution model anymore.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2011-03-08 16:51 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 15:50 KVM call minutes for Mar 8 Chris Wright
2011-03-08 15:50 ` [Qemu-devel] " Chris Wright
2011-03-08 16:00 ` Anthony Liguori
2011-03-08 16:00 ` Anthony Liguori
2011-03-08 16:09 ` Stefan Hajnoczi
2011-03-08 16:09 ` Stefan Hajnoczi
2011-03-08 16:51 ` Jan Kiszka [this message]
2011-03-08 16:51 ` [Qemu-devel] " Jan Kiszka
2011-03-08 16:58 ` Paolo Bonzini
2011-03-08 16:58 ` [Qemu-devel] " Paolo Bonzini
2011-03-08 17:10 ` Jan Kiszka
2011-03-08 17:10 ` [Qemu-devel] " Jan Kiszka
2011-03-08 17:15 ` Paolo Bonzini
2011-03-08 17:15 ` [Qemu-devel] " Paolo Bonzini
2011-03-08 17:21 ` Jan Kiszka
2011-03-08 17:21 ` [Qemu-devel] " Jan Kiszka
2011-03-08 17:40 ` Avi Kivity
2011-03-08 17:40 ` [Qemu-devel] " Avi Kivity
2011-03-08 17:41 ` Avi Kivity
2011-03-08 17:41 ` [Qemu-devel] " Avi Kivity
2011-03-08 17:42 ` Jan Kiszka
2011-03-08 17:42 ` [Qemu-devel] " Jan Kiszka
2011-03-08 17:43 ` Jan Kiszka
2011-03-08 17:43 ` [Qemu-devel] " Jan Kiszka
2011-03-08 17:45 ` Avi Kivity
2011-03-08 17:45 ` [Qemu-devel] " Avi Kivity
2011-03-15 3:38 ` Marcelo Tosatti
2011-03-15 3:38 ` [Qemu-devel] " Marcelo Tosatti
2011-03-15 7:13 ` Jan Kiszka
2011-03-15 7:13 ` [Qemu-devel] " Jan Kiszka
2011-03-09 9:25 ` [Qemu-devel] " Kevin Wolf
2011-03-09 9:25 ` Kevin Wolf
2011-03-09 13:13 ` Anthony Liguori
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=4D765E77.4020406@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=chrisw@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.