From: Ian Campbell <ian.campbell@citrix.com>
To: ian.jackson@eu.citrix.com, wei.liu2@citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH 1/2] xl: uptime: skip dom0 when calling print_domU_uptime
Date: Tue, 23 Feb 2016 10:30:00 +0000 [thread overview]
Message-ID: <1456223400.6225.122.camel@citrix.com> (raw)
In-Reply-To: <1455705264-17744-1-git-send-email-ian.campbell@citrix.com>
On Wed, 2016-02-17 at 10:34 +0000, Ian Campbell wrote:
> Dom0 is handled separately (via print_dom0_uptime) and the domU
> variant doesn't work for dom0 since libxl_vm_get_start_time() doesn't.
>
> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
Ping? (and for 2/2 "xl: NULL terminate buf when reading dom0 /proc/uptime")
> ---
> tools/libxl/xl_cmdimpl.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/tools/libxl/xl_cmdimpl.c b/tools/libxl/xl_cmdimpl.c
> index f38e3dd..89fa42c 100644
> --- a/tools/libxl/xl_cmdimpl.c
> +++ b/tools/libxl/xl_cmdimpl.c
> @@ -7055,8 +7055,10 @@ static void print_uptime(int short_mode, uint32_t
> doms[], int nb_doms)
> fprintf(stderr, "Could not list vms.\n");
> return;
> }
> - for (i = 0; i < nb_vm; i++)
> + for (i = 0; i < nb_vm; i++) {
> + if (info[i].domid == 0) continue;
> print_domU_uptime(info[i].domid, short_mode, now);
> + }
> libxl_vminfo_list_free(info, nb_vm);
> } else {
> for (i = 0; i < nb_doms; i++) {
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-02-23 10:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 10:34 [PATCH 1/2] xl: uptime: skip dom0 when calling print_domU_uptime Ian Campbell
2016-02-17 10:34 ` [PATCH 2/2] xl: NULL terminate buf when reading dom0 /proc/uptime Ian Campbell
2016-03-01 16:11 ` Ian Jackson
2016-02-23 10:30 ` Ian Campbell [this message]
2016-03-01 16:10 ` [PATCH 1/2] xl: uptime: skip dom0 when calling print_domU_uptime 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=1456223400.6225.122.camel@citrix.com \
--to=ian.campbell@citrix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).