All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Nathan Fontenot <nfont@linux.vnet.ibm.com>, linuxppc-dev@ozlabs.org
Subject: Right location in sysfs for dlpar file
Date: Thu, 27 Nov 2014 14:12:21 +1100	[thread overview]
Message-ID: <1417057941.5089.81.camel@kernel.crashing.org> (raw)

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.

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...

Cheers,
Ben.

             reply	other threads:[~2014-11-27  3:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-27  3:12 Benjamin Herrenschmidt [this message]
2014-12-01 15:41 ` Right location in sysfs for dlpar file 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
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=1417057941.5089.81.camel@kernel.crashing.org \
    --to=benh@kernel.crashing.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=nfont@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.