mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Per Bilse (3P)" <Per.Bilse@citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Juergen Gross <jgross@suse.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>,
	Jan Beulich <jbeulich@suse.com>,
	"moderated list:XEN HYPERVISOR INTERFACE" 
	<xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] drivers/xen/hypervisor: Expose VM SIF flags to userspace
Date: Tue, 29 Nov 2022 16:46:36 +0000	[thread overview]
Message-ID: <34f726e7-461e-b4b5-96bb-5f934c4d9dbc@citrix.com> (raw)
In-Reply-To: <c8c13453-c453-7de1-ae07-045064a938b8@oracle.com>

On 29/11/2022 16:29, Boris Ostrovsky wrote:
> Why not simply show unprocessed xen_start_flags as a hex value?

Providing a text representation follows what is currently the case:

[root@lcy2-dt128 /proc/xen]# cat capabilities
control_d
[root@lcy2-dt128 /proc/xen]#

The migrated form would yield:

root@dt90:/sys/hypervisor/properties# cat flags
privileged initdomain mod_start_pfn
root@dt90:/sys/hypervisor/properties#

There is good precedence for being more helpful than printing hex 
values, but I have no objections if there is consensus that a hex value 
is better.

Best,

   -- Per

      reply	other threads:[~2022-11-29 16:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29 15:00 Per Bilse
2022-11-29 15:27 ` Juergen Gross
2022-11-29 16:41   ` Andrew Cooper
2022-11-29 17:38     ` Per Bilse (3P)
2022-11-29 16:29 ` Boris Ostrovsky
2022-11-29 16:46   ` Per Bilse (3P) [this message]

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=34f726e7-461e-b4b5-96bb-5f934c4d9dbc@citrix.com \
    --to=per.bilse@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=jbeulich@suse.com \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleksandr_tyshchenko@epam.com \
    --cc=sstabellini@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®