All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>,
	Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4] qemu-char: add logfile facility to all chardev backends
Date: Fri, 15 Jan 2016 16:58:31 +0100	[thread overview]
Message-ID: <56991727.5040901@redhat.com> (raw)
In-Reply-To: <20160115091502.GA2863@redhat.com>



On 15/01/2016 10:15, Daniel P. Berrange wrote:
> On Thu, Jan 14, 2016 at 09:05:03PM -0700, Eric Blake wrote:
>> On 01/11/2016 05:44 AM, Daniel P. Berrange wrote:
>>> Typically a UNIX guest OS will log boot messages to a serial
>>> port in addition to any graphical console. An admin user
>>> may also wish to use the serial port for an interactive
>>> console. A virtualization management system may wish to
>>> collect system boot messages by logging the serial port,
>>> but also wish to allow admins interactive access.
>>>
>>
>>> This patch introduces a 'ChardevCommon' struct which
>>> is setup as a base for all the ChardevBackend types.
>>> Ideally this would be registered directly as a base
>>> against ChardevBackend, rather than each type, but
>>> the QAPI generator doesn't allow that since the
>>> ChardevBackend is a non-discriminated union. The
>>> ChardevCommon struct provides the optional 'logfile'
>>> parameter, as well as 'logappend' which controls
>>> whether QEMU truncates or appends (default truncate).
>>>
>>> Signed-off-by: Daniel P. Berrange <berrange@redhat.com>

This patch fails make check, due to a segmentation fault that can be 
reproduced with "x86_64-softmmu/qemu-system-x86_64 -serial null".

I'm squashing in the fix:

diff --git a/qemu-char.c b/qemu-char.c
index 02b0318..11caa56 100644
--- a/qemu-char.c
+++ b/qemu-char.c
@@ -3827,7 +3827,12 @@ CharDriverState *qemu_chr_new_from_opts(QemuOpts *opts,
             error_propagate(errp, local_err);
             goto qapi_out;
         }
+    } else {
+        ChardevCommon *cc = g_new0(ChardevCommon, 1);
+        qemu_chr_parse_common(opts, cc);
+        backend->u.data = cc;
     }
+
     ret = qmp_chardev_add(bid ? bid : id, backend, errp);
     if (!ret) {
         goto qapi_out;


Paolo

      reply	other threads:[~2016-01-15 15:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-11 12:44 [Qemu-devel] [PATCH v4] qemu-char: add logfile facility to all chardev backends Daniel P. Berrange
2016-01-15  4:05 ` Eric Blake
2016-01-15  9:15   ` Daniel P. Berrange
2016-01-15 15:58     ` Paolo Bonzini [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=56991727.5040901@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=eblake@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.