linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@intel.com>
To: Toshi Kani <toshi.kani@hp.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 08:27:47 -0700	[thread overview]
Message-ID: <51E80973.9000308@intel.com> (raw)
In-Reply-To: <1374097503-25515-1-git-send-email-toshi.kani@hp.com>

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.

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?

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

  parent reply	other threads:[~2013-07-18 15:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-17 21:45 [PATCH] mm/hotplug, x86: Disable ARCH_MEMORY_PROBE by default 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 [this message]
2013-07-18 16:26   ` Toshi Kani
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=51E80973.9000308@intel.com \
    --to=dave.hansen@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=isimatu.yasuaki@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=tangchen@cn.fujitsu.com \
    --cc=toshi.kani@hp.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;
as well as URLs for NNTP newsgroup(s).