[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <dc2c5f88-89c6-7a20-8135-d6650c5baf21@citrix.com>
Date: Tue, 29 Nov 2022 17:38:06 +0000
From: "Per Bilse (3P)" <Per.Bilse@...rix.com>
To: Andrew Cooper <Andrew.Cooper3@...rix.com>
CC: Stefano Stabellini <sstabellini@...nel.org>,
Oleksandr Tyshchenko <oleksandr_tyshchenko@...m.com>,
Boris Ostrovsky <boris.ostrovsky@...cle.com>,
Jan Beulich <jbeulich@...e.com>,
"moderated list:XEN HYPERVISOR INTERFACE"
<xen-devel@...ts.xenproject.org>, Juergen Gross <jgross@...e.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] drivers/xen/hypervisor: Expose VM SIF flags to userspace
On 29/11/2022 16:41, Andrew Cooper wrote:
> As for the actual flags exposed, it would be very beneficial not to copy
> the exist proc interface. It would be better to expose a subdir that
> had files containing booleans, because that also gives userspace an easy
> way to figure out if the particular flag is known to Linux,
> independently of whether the flag is set for a specific VM.
OK, I'll do that instead; I thought it was the single "control_d" that
shouldn't be perpetuated.
Best,
-- Per
Powered by blists - more mailing lists