From: Anthony Liguori <anthony@codemonkey.ws>
To: Alexander Graf <agraf@suse.de>
Cc: Chunyan Liu <cyliu@novell.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH V2] Add "tee" option to qemu char device
Date: Sun, 24 Jul 2011 08:25:40 -0500 [thread overview]
Message-ID: <4E2C1D54.8020908@codemonkey.ws> (raw)
In-Reply-To: <E1FDE9FA-6A58-4BF4-83AE-E60B295AE334@suse.de>
On 07/24/2011 04:47 AM, Alexander Graf wrote:
>
>> These arguments all apply to any possible option. Why not a grep target? Why not a cut or less target?
>
> Because they don't make sense.
Neither does tee :-)
>>> As long as the tee target is reasonably isolated, I don't think it'd clutter the char backend.
>>
>> It'll never be tested and end up becoming dead bloat code.
>
> I'll be extensively tested in Xen code, since that's how Xen will invoke qemu.
If this is being used by Xen as part of Xend, then there's really no
point in worrying about complexity because the user will never be
exposed to it.
>
> I tend to agree, but this time the solution in qemu is cleaner and easier IMHO.
Let's compare the typical use-case:
qemu -hda linux.img -nographic | tee boot.log
vs:
qemu -hda linux.img -serial tee:boot.log,stdio
I'm not even sure I got the syntax right on the later.
> Also, I've had issues with tee several times already.
Then we should fix those issues. But I have a hard time believing there
were ever issues. This is just piping.
> I'm in favor of putting a tee target into qemu's char layer and I'm sure it'll become a well used target.
It will only be used by Xen and Xen could very easily solve this problem
outside of qemu.
It adds another twisted command line syntax that will make it harder to
generalize later.
Regards,
Anthony Liguori
>
> Alex
>
>
next prev parent reply other threads:[~2011-07-24 13:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-14 8:58 [Qemu-devel] [PATCH V2] Add "tee" option to qemu char device Chunyan Liu
2011-07-23 15:23 ` Anthony Liguori
2011-07-23 18:31 ` Alexander Graf
2011-07-23 19:11 ` Anthony Liguori
2011-07-24 9:47 ` Alexander Graf
2011-07-24 13:25 ` Anthony Liguori [this message]
2011-07-24 9:44 ` Alexander Graf
2011-08-05 2:26 Chun Yan Liu
2011-08-05 13:32 ` Anthony Liguori
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=4E2C1D54.8020908@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=agraf@suse.de \
--cc=cyliu@novell.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.