From: Michael Ellerman <mpe@ellerman•id.au>
To: Nathan Fontenot <nfont@linux•vnet.ibm.com>
Cc: linuxppc-dev@ozlabs•org, Greg KH <gregkh@linuxfoundation•org>
Subject: Re: Right location in sysfs for dlpar file
Date: Tue, 02 Dec 2014 16:09:23 +1100 [thread overview]
Message-ID: <1417496963.31336.6.camel@concordia> (raw)
In-Reply-To: <547C8C0F.5070701@linux.vnet.ibm.com>
On Mon, 2014-12-01 at 09:41 -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.
>
...
>
> For PowerVM systems we need this sysfs file to deliver what is
> essentially a binary blob (specifically a rtas error log) to the
> kernel.
Those two statements don't really agree with each other. ie. "move the entire
operation .. to the kernel", but then we need a sysfs file so userspace can
deliver us a blob?
I think what you mean is that all the actual logic will move into the kernel,
and the only thing userspace will do (on PowerVM) is write the blog to kick off
the process.
On PowerKVM the entire process will be handled in the kernel (after some
additional patches to hook up the rtas event to the hotplug).
As ugly as it is, we already have /proc/rtas, which includes a bunch of files,
including error_log, which is where you can *read* the RTAS error logs from.
So maybe we just extend that, either a new file, or just by making error_log
writable?
It'd be nice to drop all that rtas gunk and move to something cleaner in /sys,
but I don't think we can realistically do that any time soon anyway?
cheers
next prev parent reply other threads:[~2014-12-02 5:09 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
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 [this message]
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=1417496963.31336.6.camel@concordia \
--to=mpe@ellerman$(echo .)id.au \
--cc=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