From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Davidlohr Bueso <davidlohr.bueso@hp.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm: add node physical memory range to sysfs
Date: Sat, 8 Dec 2012 11:45:28 -0800 [thread overview]
Message-ID: <20121208194528.GB3897@kroah.com> (raw)
In-Reply-To: <1354919696.2523.6.camel@buesod1.americas.hpqcorp.net>
On Fri, Dec 07, 2012 at 02:34:56PM -0800, Davidlohr Bueso wrote:
> This patch adds a new 'memrange' file that shows the starting and
> ending physical addresses that are associated to a node. This is
> useful for identifying specific DIMMs within the system.
>
> Signed-off-by: Davidlohr Bueso <davidlohr.bueso@hp.com>
> ---
> drivers/base/node.c | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/drivers/base/node.c b/drivers/base/node.c
> index af1a177..f165a0a 100644
> --- a/drivers/base/node.c
> +++ b/drivers/base/node.c
> @@ -211,6 +211,19 @@ static ssize_t node_read_distance(struct device *dev,
> }
> static DEVICE_ATTR(distance, S_IRUGO, node_read_distance, NULL);
>
> +static ssize_t node_read_memrange(struct device *dev,
> + struct device_attribute *attr, char *buf)
> +{
> + int nid = dev->id;
> + unsigned long start_pfn = NODE_DATA(nid)->node_start_pfn;
> + unsigned long end_pfn = start_pfn + NODE_DATA(nid)->node_spanned_pages;
> +
> + return sprintf(buf, "%#010Lx-%#010Lx\n",
> + (unsigned long long) start_pfn << PAGE_SHIFT,
> + (unsigned long long) (end_pfn << PAGE_SHIFT) - 1);
> +}
> +static DEVICE_ATTR(memrange, S_IRUGO, node_read_memrange, NULL);
As you're adding a new sysfs file, we need a Documentation/ABI/ entry as
well. Yes, the existing ones aren't there already, as Andrew points
out, sorry, but that means you get to document them all :)
thanks,
greg k-h
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2012-12-08 19:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 22:34 Davidlohr Bueso
2012-12-07 23:51 ` Andrew Morton
2012-12-08 0:17 ` Dave Hansen
2012-12-13 1:18 ` Davidlohr Bueso
2012-12-13 1:48 ` Dave Hansen
2012-12-13 2:03 ` Davidlohr Bueso
2012-12-13 4:49 ` Dave Hansen
2012-12-13 15:17 ` KOSAKI Motohiro
2012-12-13 23:15 ` Davidlohr Bueso
2012-12-14 0:18 ` Dave Hansen
2012-12-08 19:45 ` Greg Kroah-Hartman [this message]
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=20121208194528.GB3897@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=davidlohr.bueso@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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