public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Glauber Costa <glommer@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: Tue, 24 Nov 2009 12:00:17 +0200	[thread overview]
Message-ID: <4B0BAEB1.7010704@redhat.com> (raw)
In-Reply-To: <20091123190059.GD11530@mothafucka.localdomain>

On 11/23/2009 09:00 PM, Glauber Costa wrote:
> 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
>>      

"you" = Glauber Costa

>>      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?
>
>    

No.  _You_ tested it and it worked for you.  qemu-kvm next fails badly 
(doesn't even run the bios).  I need help from you in finding out why 
and fixing it.

-- 
error compiling committee.c: too many arguments to function


      parent reply	other threads:[~2009-11-24 10: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
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 [this message]

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=4B0BAEB1.7010704@redhat.com \
    --to=avi@redhat.com \
    --cc=glommer@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