From: "Andreas Färber" <afaerber@suse.de>
To: Avi Kivity <avi@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
mengcong <mc@linux.vnet.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>,
Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [qom-next] Bisecting virtio-scsi issue
Date: Sun, 17 Jun 2012 17:16:54 +0200 [thread overview]
Message-ID: <4FDDF4E6.3000006@suse.de> (raw)
In-Reply-To: <4FDDF072.4040702@redhat.com>
Am 17.06.2012 16:57, schrieb Avi Kivity:
> On 06/17/2012 05:33 PM, Anthony Liguori wrote:
>
>>> (gdb) qemu mtree
>>> 0000000000000000-7ffffffffffffffe system (@ 0x5555564627b0)
>>> 0000000000000000-000000000000ffff io (@ 0x555556462880)
>>> 000000000000007e-000000000000007f kvmvapic (I/O) (@ 0x55555647c838)
>>
>> FWIW:
>>
>>
>> commit 55016e6ab178f0d27f85fc6b09d235817ccd4b4c
>> Author: Paolo Bonzini <pbonzini@redhat.com>
>> Date: Thu Apr 12 18:00:18 2012 +0200
>
> Is this the fix? Where is it?
Nah, it's on qom-next-2 branch (for upcoming PULL).
It turned out it's really got nothing to do with this fix, it's a
dependency problem due to the added level of subdirs in the target-*/
directories: While bisecting, hw/kvm/apic.o apparently didn't get
rebuilt when object.h or qdev.h changed.
Anthony posted a patch that I'm testing now.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
prev parent reply other threads:[~2012-06-17 15:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-16 0:41 [Qemu-devel] [qom-next] Bisecting virtio-scsi issue Andreas Färber
2012-06-17 8:37 ` Avi Kivity
2012-06-17 14:08 ` Andreas Färber
2012-06-17 14:16 ` Avi Kivity
2012-06-17 14:28 ` Andreas Färber
2012-06-17 14:33 ` Anthony Liguori
2012-06-17 14:57 ` Avi Kivity
2012-06-17 15:16 ` Andreas Färber [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=4FDDF4E6.3000006@suse.de \
--to=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=mc@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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.