From: Nathan Lynch <ntl@pobox.com>
To: Geoff Levand <geoffrey.levand@am.sony.com>
Cc: linuxppc-dev@ozlabs.org, Badari Pulavarty <pbadari@us.ibm.com>
Subject: Re: [PATCH 0/3] hotplug memory remove updates
Date: Fri, 29 Feb 2008 13:15:18 -0600 [thread overview]
Message-ID: <20080229191518.GV16241@localdomain> (raw)
In-Reply-To: <47C76BBA.5000503@am.sony.com>
Geoff Levand wrote:
>
> I'm wondering how the memory hot un-plug is initiated on the pseries.
> Could you tell me about this HMC? Is it an application running in
> the lpar, or is it an external entity?
The HMC (Hardware Management Console) is a system separate from the
pseries box. It's used to provision and, um, manage, one or more
systems and their partitions. It communicates with both the POWER
hypervisor and some optional userspace daemons and utilities running
on the lpars.
> Is there a 'standard' interface from userspace that can be used to
> trigger the hot-unplug sequence? I'm asking because PS3's lv1
> hypervisor supports hot un-plug of memory, but it would need to be
> triggered from some kind of management application running in in
> userspace.
I think sysfs is the conventional interface for "offlining" a
resource, that is, getting Linux to stop using it. That's what is
used for cpu online/offline (and memory as well, I think). Releasing
a resource to the hypervisor's control is necessarily a
platform-specific operation; on pseries a userspace utility calls a
set of RTAS methods to accomplish this.
next prev parent reply other threads:[~2008-02-29 19:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 16:43 [PATCH 0/3] hotplug memory remove updates Badari Pulavarty
2008-02-28 16:44 ` [PATCH 1/3] ppc64-specific remove htab bolted mapping support Badari Pulavarty
2008-02-28 16:45 ` [PATCH 2/3] generic __remove_pages() support Badari Pulavarty
2008-02-28 16:46 ` [PATCH 3/3] ppc64-specific memory notifier support Badari Pulavarty
2008-02-28 17:20 ` Nathan Lynch
2008-02-28 18:57 ` Badari Pulavarty
2008-02-29 0:11 ` Michael Ellerman
2008-02-29 0:39 ` Nathan Lynch
2008-02-29 1:03 ` Michael Ellerman
2008-02-29 17:47 ` Badari Pulavarty
2008-03-01 2:51 ` Stephen Rothwell
2008-03-01 3:01 ` Badari Pulavarty
2008-03-03 0:49 ` Michael Ellerman
2008-02-29 17:56 ` [RFC] updating lmb.memory information for hot mem add/remove Badari Pulavarty
2008-03-01 1:12 ` Badari Pulavarty
2008-03-01 1:44 ` David Miller
2008-03-01 3:06 ` Badari Pulavarty
2008-02-29 1:39 ` [PATCH 0/3] hotplug memory remove updates Nathan Lynch
2008-02-29 2:19 ` Geoff Levand
2008-02-29 19:15 ` Nathan Lynch [this message]
2008-02-29 4:51 ` Badari Pulavarty
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=20080229191518.GV16241@localdomain \
--to=ntl@pobox.com \
--cc=geoffrey.levand@am.sony.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=pbadari@us.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).