From: Greg KH <gregkh@linuxfoundation.org>
To: "Czerwacki, Eial" <eial.czerwacki@sap.com>
Cc: "linux-staging@lists.linux.dev" <linux-staging@lists.linux.dev>,
SAP vSMP Linux Maintainer <linux.vsmp@sap.com>
Subject: Re: [RFC] staging/vSMP: new driver
Date: Thu, 17 Mar 2022 09:59:15 +0100 [thread overview]
Message-ID: <YjL4Y2l6oOabjmpX@kroah.com> (raw)
In-Reply-To: <PAXPR02MB73100E24FCE4E04B45F9285781129@PAXPR02MB7310.eurprd02.prod.outlook.com>
On Thu, Mar 17, 2022 at 08:52:37AM +0000, Czerwacki, Eial wrote:
> >> >What tasks?
> >> support of other information bits like stats
> >
> >I have no idea what that means :)
> in short, the hypervisor can provide stats it collects, future implementation will export that too
The trick will be _how_ you export this information. Let's wait on that
one for now, your current api has lots of other questions to work out
first :)
thanks,
greg k-h
next prev parent reply other threads:[~2022-03-17 8:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 18:13 [RFC] staging/vSMP: new driver Czerwacki, Eial
2022-03-16 18:31 ` Randy Dunlap
2022-03-16 18:57 ` Czerwacki, Eial
2022-03-17 7:23 ` Greg KH
2022-03-17 7:34 ` Czerwacki, Eial
2022-03-17 7:51 ` Greg KH
2022-03-17 8:17 ` Czerwacki, Eial
2022-03-17 8:35 ` Greg KH
2022-03-17 8:52 ` Czerwacki, Eial
2022-03-17 8:59 ` Greg KH [this message]
2022-03-17 9:04 ` Czerwacki, Eial
2022-04-20 11:18 ` Czerwacki, Eial
2022-04-20 11:24 ` Greg KH
2022-04-20 11:38 ` Czerwacki, Eial
2022-04-20 11:42 ` Greg KH
2022-04-20 11:57 ` Czerwacki, Eial
2022-04-20 12:17 ` Greg KH
2022-04-20 12:36 ` Czerwacki, Eial
2022-04-20 14:24 ` Greg KH
2022-03-17 7:24 ` Greg KH
2022-03-17 7:38 ` Czerwacki, Eial
2022-03-17 7:52 ` Greg KH
2022-03-17 10:19 ` Dan Carpenter
2022-03-17 10:27 ` Dan Carpenter
2022-03-17 13:41 ` Czerwacki, Eial
2022-03-17 13:56 ` Dan Carpenter
2022-03-17 14:05 ` 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=YjL4Y2l6oOabjmpX@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=eial.czerwacki@sap.com \
--cc=linux-staging@lists.linux.dev \
--cc=linux.vsmp@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