From: Greg KH <gregkh@linuxfoundation•org>
To: Nathan Fontenot <nfont@linux•vnet.ibm.com>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: Right location in sysfs for dlpar file
Date: Mon, 1 Dec 2014 20:26:26 -0800 [thread overview]
Message-ID: <20141202042626.GC9271@kroah.com> (raw)
In-Reply-To: <547C8C0F.5070701@linux.vnet.ibm.com>
On Mon, Dec 01, 2014 at 09:41:03AM -0600, Nathan Fontenot wrote:
> On 11/26/2014 09:12 PM, Benjamin Herrenschmidt wrote:
> > Hi Greg,
> >
> > So Nathan is working on a patch series to cleanup and improve our
> > "DLPAR" infrastructure which is basically our hotplug mechanism when
> > running under the PowerVM (aka pHyp) and KVM hypervisors.
>
> The cleanup to the dlpar infrastructure will move the entire operation
> of hotplugging a device to the kernel instead of doing it partially in
> userspace and partially in the kernel as is currently done.
>
> >
> > I'll let Nathan give you a bit more details/background and answer
> > subsequent question you might have as this is really his area of
> > expertise.
> >
> > To cut a long story short, we need a sysfs file that allows our
> > userspace tools to notify the kernel of hotplug events coming from
> > the management console (which talks to userspace daemons using a
> > proprietary protocol) to "initiate" the hotplug operations, which in
> > turn get dispatched internally in the kernel to the right subsystem
> > (memory, cpu, pci, ...) based on the resource type.
> >
> > On IRC, Greg suggested /sys/firmware and /sys/hypervisor which both
> > look like a reasonable option to me, probably better than dlpar...
>
> For PowerVM systems we need this sysfs file to deliver what is
> essentially a binary blob (specifically a rtas error log) to the
> kernel. The current patch set is creating /sys/kernel/dlpar. As Ben
> mentioned we would like your input on what would be the proper place
> to create this file.
And what is the kernel supposed to do with such a binary blob? Parse
it? Or pass it to something else?
Anyway, let's see the patches before I guess anything else, that will
determine how things work out best.
thanks,
greg k-h
next prev parent reply other threads:[~2014-12-02 4:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 3:12 Right location in sysfs for dlpar file Benjamin Herrenschmidt
2014-12-01 15:41 ` Nathan Fontenot
2014-12-02 4:26 ` Greg KH [this message]
2014-12-04 3:07 ` Nathan Fontenot
2014-12-04 4:31 ` Greg KH
2014-12-08 15:21 ` Nathan Fontenot
2014-12-08 20:08 ` Benjamin Herrenschmidt
2014-12-02 5:09 ` Michael Ellerman
2014-12-04 3:06 ` Nathan Fontenot
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=20141202042626.GC9271@kroah.com \
--to=gregkh@linuxfoundation$(echo .)org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=nfont@linux$(echo .)vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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