From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qemu master tests/vmstate prints "Failed to load simple/primitive:b_1" etc
Date: Thu, 20 Oct 2016 11:41:49 +0100 [thread overview]
Message-ID: <20161020104148.GD2039@work-vm> (raw)
In-Reply-To: <b80d5a00-3f28-8dca-7c36-1c1c2c0175c0@redhat.com>
* Paolo Bonzini (pbonzini@redhat.com) wrote:
>
>
> On 18/10/2016 11:54, Dr. David Alan Gilbert wrote:
> > I've not quite figured it out but we're linked against the stubs/ monitor
> > code rather than the real monitor code; and the stubs monitor_vprintf discards
> > and the stubs monitor_cur_is_qmp() always returns false, so to silence things
> > we just have to make cur_mon non-NULL.
> > Unfortunately cur_mon is of type Monitor * and Monitor isn't defined publicly,
> > so we can't know it's size. The following evil hack does silence things
> > for anyone desperate, but I do need to find a neater way; perhaps the right
> > thing is just to link against monitor and create a dummy "null" chardev as you
> > say.
>
> If error_printf/error_vprintf are to a separate file, then stubs/ can be
> changed to use vfprintf unconditionally.
Moving code out of util/qemu-error.c just so they can be stubbed separately
seems a little odd.
> And then I wonder what we actually use cur_mon for, perhaps with this
> change we can remove stubs/mon*.
I've just posted a slightly cleaner version of that nasty hack that gives
a value to assign to cur_mon.
Dave
> Paolo
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2016-10-20 10:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 18:37 [Qemu-devel] qemu master tests/vmstate prints "Failed to load simple/primitive:b_1" etc Peter Maydell
2016-10-17 18:51 ` Dr. David Alan Gilbert
2016-10-17 19:04 ` Peter Maydell
2016-10-17 19:15 ` Dr. David Alan Gilbert
2016-10-17 21:08 ` Paolo Bonzini
2016-10-18 8:03 ` Markus Armbruster
2016-10-18 9:54 ` Dr. David Alan Gilbert
2016-10-18 13:38 ` Paolo Bonzini
2016-10-20 10:41 ` Dr. David Alan Gilbert [this message]
2016-10-24 14:26 ` Paolo Bonzini
2016-10-20 8:41 ` Halil Pasic
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=20161020104148.GD2039@work-vm \
--to=dgilbert@redhat.com \
--cc=armbru@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).