[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ef3f3117-6cd5-4b94-8ddb-e6d224efac60@intel.com>
Date: Wed, 12 Mar 2025 07:57:31 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Joerg Roedel <joro@...tes.org>, x86@...nel.org
Cc: hpa@...or.com, Tom Lendacky <thomas.lendacky@....com>,
Nikunj A Dadhania <nikunj@....com>, Larry.Dewey@....com,
linux-kernel@...r.kernel.org, linux-coco@...ts.linux.dev,
Juergen Gross <jgross@...e.com>, kirill.shutemov@...ux.intel.com,
alexey.gladkov@...el.com, Joerg Roedel <jroedel@...e.de>
Subject: Re: [PATCH 2/2] x86/sev: Make SEV_STATUS available via SYSFS
On 3/12/25 07:41, Joerg Roedel wrote:
> +static ssize_t sev_status_show(struct kobject *kobj,
> + struct kobj_attribute *attr, char *buf)
> +{
> + return sysfs_emit(buf, "%llx\n", sev_status);
> +}
Do we really want to just plumb the raw MSR out to userspace? Users
would still need to parse the thing, so it's not _really_ human readable.
Powered by blists - more mailing lists