From: Toshi Kani <toshi.kani@hp.com>
To: Dave Hansen <dave.hansen@intel.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, x86@kernel.org,
isimatu.yasuaki@jp.fujitsu.com, tangchen@cn.fujitsu.com,
vasilis.liaskovitis@profitbricks.com
Subject: Re: [PATCH] mm/hotplug, x86: Disable ARCH_MEMORY_PROBE by default
Date: Thu, 18 Jul 2013 10:26:55 -0600 [thread overview]
Message-ID: <1374164815.24916.84.camel@misato.fc.hp.com> (raw)
In-Reply-To: <51E80973.9000308@intel.com>
On Thu, 2013-07-18 at 08:27 -0700, Dave Hansen wrote:
> On 07/17/2013 02:45 PM, Toshi Kani wrote:
> > +CONFIG_ARCH_MEMORY_PROBE is supported on powerpc only. On x86, this config
> > +option is disabled by default since ACPI notifies a memory hotplug event to
> > +the kernel, which performs its hotplug operation as the result. Please
> > +enable this option if you need the "probe" interface on x86.
>
> There's no prompt for this and no way to override what you've done here
> without hacking Kconfig/.config files.
>
> It's also completely wrong to say "CONFIG_ARCH_MEMORY_PROBE is supported
> on powerpc only." It works just fine on x86. In fact, I was just using
> it today without ACPI being around.
This statement has been there in the document (no change), and I
consider "supported" and "may work" are two different things.
> I'd really prefer you don't do this. Do you really have random
> processes on your system poking at random sysfs files and then
> complaining when things break?
I am afraid that the "probe" interface does not provide the level of
quality suitable for regular users. It takes any value and blindly
extends the page table. Also, we are not aware of the use of this
interface on x86. Would you elaborate why you need this interface on
x86? Is it for your testing, or is it necessary for end-users? If the
former, can you modify .config file to enable it?
Thanks,
-Toshi
--
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>
next prev parent reply other threads:[~2013-07-18 16:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 21:45 Toshi Kani
2013-07-17 23:22 ` KOSAKI Motohiro
2013-07-17 23:29 ` Toshi Kani
2013-07-17 23:33 ` KOSAKI Motohiro
2013-07-17 23:51 ` Toshi Kani
2013-07-18 0:24 ` KOSAKI Motohiro
2013-07-18 0:30 ` Toshi Kani
2013-07-19 17:56 ` Toshi Kani
2013-07-18 1:48 ` Yasuaki Ishimatsu
2013-07-18 16:02 ` Toshi Kani
2013-07-18 15:27 ` Dave Hansen
2013-07-18 16:26 ` Toshi Kani [this message]
2013-07-18 18:34 ` Dave Hansen
2013-07-18 20:10 ` Toshi Kani
2013-07-18 20:29 ` Dave Hansen
2013-07-18 21:38 ` Toshi Kani
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=1374164815.24916.84.camel@misato.fc.hp.com \
--to=toshi.kani@hp.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tangchen@cn.fujitsu.com \
--cc=vasilis.liaskovitis@profitbricks.com \
--cc=x86@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