From: Cedric Bosdonnat <cbosdonnat@suse.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>, Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: per-domain logging
Date: Mon, 10 Oct 2016 09:05:37 +0200 [thread overview]
Message-ID: <1476083137.2856.5.camel@suse.com> (raw)
In-Reply-To: <22519.49484.742767.819871@mariner.uk.xensource.com>
On Fri, 2016-10-07 at 16:37 +0100, Ian Jackson wrote:
> > But let's step back a bit: have we agreed on the approach forward? This
> > thread doesn't seem to have a clear conclusion yet. Obviously I don't
> > want you to waste your writing code that's going to be threw away.
> >
> > If you're happy with demuxing in libvirt, I won't object to it. Looks
> > like there is relatively less code churn involved than other solutions,
> > say, libxl keeping track of a set of per-domain xtl loggers.
>
> The libvirt solution is not particularly general.
It uses a bunch of libvirt-specific utility functions, but nothing that
can't be mimicked by other applications. After all xtl defines one logger
but anyone wan implement his own ;)
--
Cedric
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-10-10 7:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 14:22 per-domain logging Cedric Bosdonnat
2016-09-15 14:50 ` Wei Liu
2016-09-15 15:11 ` Wei Liu
2016-09-15 15:41 ` Cedric Bosdonnat
2016-09-19 15:23 ` Ian Jackson
2016-09-19 16:53 ` Konrad Rzeszutek Wilk
2016-10-04 9:14 ` Cedric Bosdonnat
2016-10-07 14:09 ` Wei Liu
2016-10-07 15:37 ` Ian Jackson
2016-10-10 7:05 ` Cedric Bosdonnat [this message]
2016-10-10 7:03 ` Cedric Bosdonnat
2016-10-10 10:06 ` Wei Liu
2016-10-13 9:28 ` Cedric Bosdonnat
2016-10-13 9:41 ` Wei Liu
2016-11-09 10:27 ` Cedric Bosdonnat
2016-11-11 1:51 ` Wei Liu
2016-11-11 11:22 ` Ian Jackson
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=1476083137.2856.5.camel@suse.com \
--to=cbosdonnat@suse.com \
--cc=ian.jackson@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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.