From: jschopp <jschopp@austin.ibm.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
LHMS <lhms-devel@lists.sourceforge.net>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [Lhms-devel] [PATCH] register hot-added memory to iomem resource
Date: Thu, 27 Apr 2006 11:10:16 -0500 [thread overview]
Message-ID: <4450ECE8.6050708@austin.ibm.com> (raw)
In-Reply-To: <20060427204904.5037f6ea.kamezawa.hiroyu@jp.fujitsu.com>
> +/* add this memory to iomem resource */
> +static void register_memory_resource(u64 start, u64 size)
> +{
> + struct resource *res;
> +
> + res = kzalloc(sizeof(struct resource), GFP_KERNEL);
> + BUG_ON(!res);
> +
> + res->name = "System RAM";
> + res->start = start;
> + res->end = start + size - 1;
> + res->flags = IORESOURCE_MEM;
> + if (request_resource(&iomem_resource, res) < 0) {
> + printk("System RAM resource %llx - %llx cannot be added\n",
> + (unsigned long long)res->start, (unsigned long long)res->end);
> + kfree(res);
> + }
> +}
This is more of a question than a comment. Is this code saying that all memory we are
adding is available for IO? And is it really true that on all platforms any memory we add
can be used that way?
next prev parent reply other threads:[~2006-04-27 16:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 11:49 [PATCH] register hot-added memory to iomem resource KAMEZAWA Hiroyuki
2006-04-27 16:10 ` jschopp [this message]
2006-04-28 0:47 ` [Lhms-devel] " KAMEZAWA Hiroyuki
2006-04-27 23:01 ` Andrew Morton
2006-04-28 0:27 ` [Lhms-devel] " KAMEZAWA Hiroyuki
2006-04-28 14:50 ` Vivek Goyal
2006-04-28 18:43 ` Vivek Goyal
2006-04-29 0:18 ` KAMEZAWA Hiroyuki
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=4450ECE8.6050708@austin.ibm.com \
--to=jschopp@austin.ibm.com \
--cc=akpm@osdl.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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