On 07/23/2011 01:31 PM, Alexander Graf wrote:
On 23.07.2011, at 17:23, Anthony Liguori wrote:
On 07/14/2011 03:58 AM, Chunyan Liu wrote:
Add "tee" backend to char device. It could be used as follows:
-serial tee:filepath,pty
-chardev tee,tee_fpath=path,tee_backend=pty,,path=path,,[mux=on|off]
With "tee" option, "pty" output would be duplicated to filepath.
Related thread:
http://lists.nongnu.org/archive/html/qemu-devel/2011-07/msg00105.html
I loathe adding even more complexity to the the char layer. Can't you do this
just as well with socat?
I disagree. For socat we'd have to open some listening port (unix, tcg, etc)
and then have socat connect to it.
And what's the problem? Use a unix domain socket and call it a day.
While socat is not up yet, the VM won't run. It also adds another layer of
complexity (syncing of socat and qemu process) to the picture that I don't like.
These arguments all apply to any possible option. Why not a grep
target? Why not a cut or less target?
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.
For uncommon use cases where there's another way to do something with no
real obvious technical advantages, using existing code (and utilities)
always wins vs reinventing the wheel IMHO.
Regards,
Anthony Liguori
