From: Paolo Bonzini <pbonzini@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH RFC] qemu-char: add an "overlay" backend type
Date: Wed, 16 Dec 2015 19:13:08 +0100 [thread overview]
Message-ID: <5671A9B4.4010004@redhat.com> (raw)
In-Reply-To: <1450288571-5939-1-git-send-email-berrange@redhat.com>
On 16/12/2015 18:56, Daniel P. Berrange wrote:
> Introduce a new QEMU chardev backend called "overlay" which
> allows you to splice together a pair of chardev backends into
> one combined backend. The master backend permits full input/output
> but the slave backend is output only.
>
> The primary use case for this is to allow arbitrary backends to
> have their data logged to a file, eg a 'file' backend would be
> setup as the slave.
>
> $ qemu-system-x86_64 \
> -chardev socket,host=localhost,port=9000,server=on,nowait,id=char0master \
> -chardev file,path=/some/log/file.log,id=char0slave \
> -chardev overlay,id=char0,master=char0master,slave=char0slave \
> -device isa-serial,chardev=char0 \
> ...other args...
> ---
>
> This idea was suggsted in
>
> https://lists.gnu.org/archive/html/qemu-devel/2015-12/msg01256.html
>
> this patch is a very quick proof of concept impl to illustrate the
> idea.
Hmm, I was a fan of the "do it outside QEMU" idea... It would also fix
the issue you have with qemu_chr_fe_write_all...
Paolo
next prev parent reply other threads:[~2015-12-16 18:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 17:56 [Qemu-devel] [PATCH RFC] qemu-char: add an "overlay" backend type Daniel P. Berrange
2015-12-16 18:13 ` Paolo Bonzini [this message]
2015-12-17 12:01 ` Daniel P. Berrange
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=5671A9B4.4010004@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@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.