linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: KOSAKI Motohiro <kosaki.motohiro@gmail.com>
To: Toshi Kani <toshi.kani@hp.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>,
	x86@kernel.org,
	Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
	Tang Chen <tangchen@cn.fujitsu.com>,
	vasilis.liaskovitis@profitbricks.com
Subject: Re: [PATCH] mm/hotplug, x86: Disable ARCH_MEMORY_PROBE by default
Date: Wed, 17 Jul 2013 19:22:12 -0400	[thread overview]
Message-ID: <CAHGf_=pND-R=qMHg7b=Fi5SqS6ahXJCG865WsOS2eKWa6g3A7A@mail.gmail.com> (raw)
In-Reply-To: <1374097503-25515-1-git-send-email-toshi.kani@hp.com>

On Wed, Jul 17, 2013 at 5:45 PM, Toshi Kani <toshi.kani@hp.com> wrote:
> CONFIG_ARCH_MEMORY_PROBE enables /sys/devices/system/memory/probe
> interface, which allows a given memory address to be hot-added as
> follows. (See Documentation/memory-hotplug.txt for more detail.)
>
> # echo start_address_of_new_memory > /sys/devices/system/memory/probe
>
> This probe interface is required on powerpc. On x86, however, ACPI
> notifies a memory hotplug event to the kernel, which performs its
> hotplug operation as the result. Therefore, users should not be
> required to use this interface on x86. This probe interface is also
> error-prone that the kernel blindly adds a given memory address
> without checking if the memory is present on the system; no probing
> is done despite of its name. The kernel crashes when a user requests
> to online a memory block that is not present on the system.
>
> This patch disables CONFIG_ARCH_MEMORY_PROBE by default on x86,
> and clarifies it in Documentation/memory-hotplug.txt.

Why don't you completely remove it? Who should use this strange interface?

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

  reply	other threads:[~2013-07-17 23:22 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 [this message]
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
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='CAHGf_=pND-R=qMHg7b=Fi5SqS6ahXJCG865WsOS2eKWa6g3A7A@mail.gmail.com' \
    --to=kosaki.motohiro@gmail.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