From: "Michael S. Tsirkin" <mst@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [PULL] Memory core space reduction
Date: Wed, 29 Feb 2012 16:15:20 +0200 [thread overview]
Message-ID: <20120229141520.GB6945@redhat.com> (raw)
In-Reply-To: <4F4E0FED.8040301@redhat.com>
On Wed, Feb 29, 2012 at 01:45:49PM +0200, Avi Kivity wrote:
> On 02/29/2012 01:31 PM, Avi Kivity wrote:
> > On 02/29/2012 01:25 PM, Michael S. Tsirkin wrote:
> > > It does not crash under valgrind :)
> > > But valgrid did show some info:
> > >
> > > ==9202== Invalid write of size 8
> > > ==9202== at 0x2F313D: portio_list_add_1 (ioport.c:379)
> > >
> >
> > Anthony, your "bad bisect" was in fact good - it was the very first
> > patch that was bad:
> >
> > piolist->regions[piolist->nr++] = region;
> > piolist->aliases[piolist->nr++] = alias;
> >
> > will fix.
> >
>
> Please retry with the new memory/core branch I just pushed. If using
> kvm, also apply the patch I posted elsewhere in this thread.
Yes, seems to boot now.
> --
> error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-02-29 14:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 12:25 [Qemu-devel] [PULL] Memory core space reduction Avi Kivity
2012-02-28 12:26 ` Avi Kivity
2012-02-28 17:59 ` Michael S. Tsirkin
2012-02-28 18:13 ` Anthony Liguori
2012-02-28 18:15 ` Avi Kivity
2012-02-28 18:31 ` Anthony Liguori
2012-02-28 18:56 ` Anthony Liguori
2012-02-28 19:14 ` Anthony Liguori
2012-02-28 19:17 ` Avi Kivity
2012-02-28 19:20 ` Anthony Liguori
2012-02-28 22:58 ` Michael S. Tsirkin
2012-02-29 10:09 ` Avi Kivity
2012-02-29 10:23 ` Michael S. Tsirkin
2012-02-29 10:53 ` Avi Kivity
2012-02-29 11:25 ` Michael S. Tsirkin
2012-02-29 11:31 ` Avi Kivity
2012-02-29 11:45 ` Avi Kivity
2012-02-29 14:15 ` Michael S. Tsirkin [this message]
2012-02-29 11:27 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2012-02-28 12:24 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=20120229141520.GB6945@redhat.com \
--to=mst@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=avi@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 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.