From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Czerwacki, Eial" <eial.czerwacki@sap.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Arsh, Leonid" <leonid.arsh@sap.com>,
"Twaig, Oren" <oren.twaig@sap.com>,
SAP vSMP Linux Maintainer <linux.vsmp@sap.com>,
Arnd Bergmann <arnd@arndb.de>,
Dan Carpenter <dan.carpenter@oracle.com>,
Andra Paraschiv <andraprs@amazon.com>,
Borislav Petkov <bp@suse.de>,
Brijesh Singh <brijesh.singh@amd.com>,
Eric Biggers <ebiggers@google.com>, Fei Li <fei1.li@intel.com>,
Hans de Goede <hdegoede@redhat.com>, Jens Axboe <axboe@kernel.dk>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Subject: Re: [PATCH v2] drivers/virt/vSMP: new driver
Date: Thu, 25 Aug 2022 13:46:31 +0200 [thread overview]
Message-ID: <YwdhF6r0egBc3w1m@kroah.com> (raw)
In-Reply-To: <PAXPR02MB73108383655C1FB4B98C3C2281729@PAXPR02MB7310.eurprd02.prod.outlook.com>
On Thu, Aug 25, 2022 at 10:41:28AM +0000, Czerwacki, Eial wrote:
> >On Thu, Aug 25, 2022 at 10:16:59AM +0000, Czerwacki, Eial wrote:
> >> >> >And why is your version file a binary file? It should just be a small
> >> >> >text string, right?
> >> >> not so small, it can reach up to 512kb.
> >> >
> >> >That was not obvious at all. Please document this.
> >> where should the document be?
> >> in the code as a comment or in another file?
> >
> >In the Documentation/ABI/ file that describes this file.
> ok, will place it there
>
> >
> >> >And how in the world is a "version" that big? What exactly does this
> >> >contain?
> >> it 's size depends on the number of resources it uses.
> >> here is an example:
> >> :~> cat /sys/hypervisor/vsmp/version
> >> SAP vSMP Foundation: 10.6.2862.0 (Aug 22 2022 15:21:02)
> >> System configuration:
> >> Boards: 2
> >> 1 x Proc. + I/O + Memory
> >> 1 x NVM devices (Amazon.com Amazon EC2 NVMe Instance Storage)
> >> Processors: 1, Cores: 2, Threads: 4
> >> Intel(R) Xeon(R) Platinum 8124M CPU @ 3.00GHz Stepping 04
> >> Memory (MB): 30976 (of 103192), Cache: 7527, Private: 64689
> >> 1 x 6400MB [ 7825/ 321/ 1104]
> >> 1 x 24576MB [95367/7206/63585] 00:1f.0#1
> >> Boot device: [HDD] NVMe: Amazon Elastic Block Store
> >> Supported until: Aug 22 2024
> >
> >That is crazy, and is not a version. It's a "configuration".
> it is called version for history reasons...
There is no "history" here, you can create whatever sane interface you
want right now, there is no backwards compatible issues involved at all.
> >See above, make it text only for the version. If you want to export
> >other things, be explicit and make them "one value per sysfs file" or
> >use debugfs for debugging things that no one relies on.
> so you suggest braking the summery into files, e.g. one for cpus, one for ram and etcetera?
Again, who uses this information and what is it used for?
thanks,
greg k-h
next prev parent reply other threads:[~2022-08-25 11:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 6:24 [PATCH v2] drivers/virt/vSMP: new driver Czerwacki, Eial
2022-08-25 7:32 ` Greg Kroah-Hartman
2022-08-25 9:17 ` Czerwacki, Eial
2022-08-25 9:30 ` Greg Kroah-Hartman
2022-08-25 10:16 ` Czerwacki, Eial
2022-08-25 10:24 ` Greg Kroah-Hartman
2022-08-25 10:41 ` Czerwacki, Eial
2022-08-25 11:46 ` Greg Kroah-Hartman [this message]
2022-08-25 12:02 ` Czerwacki, Eial
2022-08-25 12:19 ` Greg Kroah-Hartman
2022-08-25 12:38 ` Czerwacki, Eial
2022-08-25 12:42 ` Greg Kroah-Hartman
2022-08-25 12:55 ` Czerwacki, Eial
2022-08-25 10:46 ` Dan Carpenter
2022-08-25 10:48 ` Czerwacki, Eial
2022-08-25 10:59 ` Borislav Petkov
2022-08-25 11:03 ` Czerwacki, Eial
2022-08-25 12:41 ` Dan Carpenter
2022-08-25 13:04 ` Czerwacki, Eial
2022-09-06 13:50 ` Greg Kroah-Hartman
2022-09-06 16:47 ` Greg Kroah-Hartman
2022-09-07 6:30 ` Czerwacki, Eial
2022-09-07 6:11 ` Czerwacki, Eial
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=YwdhF6r0egBc3w1m@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andraprs@amazon.com \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=bp@suse.de \
--cc=brijesh.singh@amd.com \
--cc=dan.carpenter@oracle.com \
--cc=ebiggers@google.com \
--cc=eial.czerwacki@sap.com \
--cc=fei1.li@intel.com \
--cc=hdegoede@redhat.com \
--cc=leonid.arsh@sap.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.vsmp@sap.com \
--cc=mchehab+huawei@kernel.org \
--cc=oren.twaig@sap.com \
/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