From: Jan Kiszka <jan.kiszka@siemens.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Chris Wright <chrisw@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: KVM call minutes for Mar 8
Date: Tue, 08 Mar 2011 18:10:19 +0100 [thread overview]
Message-ID: <4D7662FB.2060000@siemens.com> (raw)
In-Reply-To: <4D76603F.2090905@redhat.com>
On 2011-03-08 17:58, Paolo Bonzini wrote:
> On 03/08/2011 05:51 PM, Jan Kiszka 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.
>
> The qemu.git bit seen with my win32 patch series should also be a
> regression from qemu-kvm.git to qemu.git, no?
Can't follow. What do you mean?
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2011-03-08 17:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 15:50 [Qemu-devel] KVM call minutes for Mar 8 Chris Wright
2011-03-08 16:00 ` Anthony Liguori
2011-03-08 16:09 ` Stefan Hajnoczi
2011-03-08 16:51 ` [Qemu-devel] " Jan Kiszka
2011-03-08 16:58 ` Paolo Bonzini
2011-03-08 17:10 ` Jan Kiszka [this message]
2011-03-08 17:15 ` Paolo Bonzini
2011-03-08 17:21 ` Jan Kiszka
2011-03-08 17:40 ` Avi Kivity
2011-03-08 17:41 ` Avi Kivity
2011-03-08 17:42 ` Jan Kiszka
2011-03-08 17:43 ` Jan Kiszka
2011-03-08 17:45 ` Avi Kivity
2011-03-15 3:38 ` Marcelo Tosatti
2011-03-15 7:13 ` Jan Kiszka
2011-03-09 9:25 ` [Qemu-devel] " 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=4D7662FB.2060000@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@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).