From: Paul Durrant <xadimgnik@gmail.com>
To: "'Jan Beulich'" <jbeulich@suse.com>
Cc: xen-devel@lists.xenproject.org,
'Ian Jackson' <ian.jackson@eu.citrix.com>, 'Wei Liu' <wl@xen.org>
Subject: RE: [PATCH 3/5] tools/misc: add xen-ctx to present domain context
Date: Fri, 3 Apr 2020 16:20:20 +0100 [thread overview]
Message-ID: <001e01d609cb$64913fa0$2db3bee0$@xen.org> (raw)
In-Reply-To: <b94676ab-371b-bb69-0d07-dd38fe22ceba@suse.com>
> -----Original Message-----
> From: Jan Beulich <jbeulich@suse.com>
> Sent: 30 March 2020 11:54
> To: Paul Durrant <paul@xen.org>
> Cc: xen-devel@lists.xenproject.org; Ian Jackson <ian.jackson@eu.citrix.com>; Wei Liu <wl@xen.org>
> Subject: Re: [PATCH 3/5] tools/misc: add xen-ctx to present domain context
>
> On 27.03.2020 19:50, Paul Durrant wrote:
> > This tools is analogous to 'xen-hvmctx' which presents HVM context.
> > Subsequent patches will add 'dump' functions when new records are
> > introduced.
> >
> > Signed-off-by: Paul Durrant <paul@xen.org>
> > ---
> > Cc: Ian Jackson <ian.jackson@eu.citrix.com>
> > Cc: Wei Liu <wl@xen.org>
> > ---
> > .gitignore | 1 +
> > tools/misc/Makefile | 4 ++
> > tools/misc/xen-ctx.c | 144 +++++++++++++++++++++++++++++++++++++++++++
>
> Is xen-ctx a good choice of a name, considering we already have not
> only xen-hvmctx, but also xenctx? If the new functionality isn't a
> good fit for either, perhaps its name would better reflect its
> connection to save/restore records? xen-sr-dump looks pretty clumsy
> to me, but still seems better than a name easily mixed up with
> others.
How about xen-domctx?
Paul
>
> Jan
next prev parent reply other threads:[~2020-04-03 15:20 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 18:50 [Xen-devel] [PATCH 0/5] domain context infrastructure Paul Durrant
2020-03-27 18:50 ` [Xen-devel] [PATCH 1/5] xen/common: introduce a new framework for save/restore of 'domain' context Paul Durrant
2020-04-01 12:00 ` Julien Grall
2020-04-01 12:07 ` Jan Beulich
2020-04-01 12:16 ` Julien Grall
2020-04-01 12:23 ` Jan Beulich
2020-04-03 15:55 ` Paul Durrant
2020-04-03 17:24 ` Julien Grall
2020-04-06 8:27 ` Paul Durrant
2020-04-06 9:08 ` Julien Grall
2020-04-06 9:18 ` Paul Durrant
2020-04-06 9:50 ` Julien Grall
2020-04-06 10:34 ` Paul Durrant
2020-04-06 12:43 ` Jan Beulich
2020-04-01 14:50 ` Jan Beulich
2020-04-02 9:58 ` Paul Durrant
2020-04-02 11:08 ` Jan Beulich
2020-04-02 14:00 ` Paul Durrant
2020-04-03 8:38 ` Jan Beulich
2020-03-27 18:50 ` [Xen-devel] [PATCH 2/5] xen/common/domctl: introduce XEN_DOMCTL_get/setdomaincontext Paul Durrant
2020-04-01 13:42 ` Julien Grall
2020-04-06 9:07 ` Paul Durrant
2020-04-06 12:46 ` Jan Beulich
2020-04-01 13:46 ` Julien Grall
2020-03-27 18:50 ` [Xen-devel] [PATCH 3/5] tools/misc: add xen-ctx to present domain context Paul Durrant
2020-03-30 10:54 ` Jan Beulich
2020-04-03 15:20 ` Paul Durrant [this message]
2020-04-03 15:29 ` Jan Beulich
2020-04-03 16:08 ` Paul Durrant
2020-03-27 18:50 ` [Xen-devel] [PATCH 4/5] common/domain: add a domain context record for shared_info Paul Durrant
2020-04-01 14:27 ` Julien Grall
2020-03-27 18:50 ` [Xen-devel] [PATCH 5/5] tools/libxc: make use of domain context SHARED_INFO record Paul Durrant
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='001e01d609cb$64913fa0$2db3bee0$@xen.org' \
--to=xadimgnik@gmail.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=paul@xen.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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.