From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Chris Wright <chrisw@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Marcelo Tosatti <mtosatti@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 19:40:24 +0200 [thread overview]
Message-ID: <4D766A08.50109@redhat.com> (raw)
In-Reply-To: <4D766583.9040507@siemens.com>
On 03/08/2011 07:21 PM, Jan Kiszka wrote:
> On 2011-03-08 18:15, Paolo Bonzini wrote:
> > On 03/08/2011 06:10 PM, Jan Kiszka wrote:
> >>> 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?
> >
> > I didn't understand very well Avi and Marcelo's exchange, but this test
> > definitely 1) fails with qemu iothread, 2) works with qemu non-iothread.
> > What I didn't understand is whether it works with qemu-kvm.
That was Paolo's patchset which I tested, yes? I wasn't talking about
that in the call.
> Are we talking about the failing Fedora installations? Or something else?
Something else - 27f368604a3d27ca4d.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-03-08 17:40 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
2011-03-08 17:15 ` Paolo Bonzini
2011-03-08 17:21 ` Jan Kiszka
2011-03-08 17:40 ` Avi Kivity [this message]
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=4D766A08.50109@redhat.com \
--to=avi@redhat.com \
--cc=chrisw@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--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).