From: Glauber Costa <glommer@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: KVM list <kvm@vger.kernel.org>
Subject: Re: Breakage due to commit c1699988 ("v3: don't call reset functions on cpu initialization")
Date: Mon, 23 Nov 2009 17:00:59 -0200 [thread overview]
Message-ID: <20091123190059.GD11530@mothafucka.localdomain> (raw)
In-Reply-To: <4B094DC4.1000107@redhat.com>
On Sun, Nov 22, 2009 at 04:42:12PM +0200, Avi Kivity wrote:
> A qemu-kvm which merges this commit breaks badly (see qemu-kvm.git next
> branch). In the commit log for this commit, you write
>
> I tested it with qemu (with and without io-thread) and qemu-kvm, and it
> seems to be doing okay - although qemu-kvm uses a slightly different
> patch.
>
> Can you share the slightly different patch (against 'next') please?
Sorry, I don't follow. You said you tested it and it works, so what exactly
do we need from me here?
next prev parent reply other threads:[~2009-11-23 19:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-22 14:42 Breakage due to commit c1699988 ("v3: don't call reset functions on cpu initialization") Avi Kivity
2009-11-23 19:00 ` Glauber Costa [this message]
2009-11-23 21:07 ` Glauber Costa
2009-11-24 10:01 ` Avi Kivity
2009-11-24 12:16 ` Glauber Costa
2009-11-24 12:50 ` Avi Kivity
2009-11-24 10:00 ` 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=20091123190059.GD11530@mothafucka.localdomain \
--to=glommer@redhat.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.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