From: Dave Hansen <dave@sr71.net>
To: Toshi Kani <toshi.kani@hp.com>
Cc: Dave Hansen <dave.hansen@intel.com>,
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 11:34:30 -0700 [thread overview]
Message-ID: <51E83536.6070100@sr71.net> (raw)
In-Reply-To: <1374164815.24916.84.camel@misato.fc.hp.com>
On 07/18/2013 09:26 AM, Toshi Kani wrote:
> On Thu, 2013-07-18 at 08:27 -0700, Dave Hansen wrote:
>> 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.
That's like saying that /dev/sda takes any value and blindly writes it
to the disk.
> 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?
For me, it's testing. It allows testing of the memory hotplug software
stack without actual hardware, which is incredibly valuable. That
includes testing on distribution kernels which I do not want to modify.
I thought there were some hypervisor users which don't use ACPI for
hotplug event notifications too.
All that I'm asking is that you either leave it the way it is, or make a
Kconfig menu entry for it.
But, really, what's the problem that you're solving? Has this caused
you issues somehow? It's been there for, what, 10 years? Surely it's
part of the ABI.
--
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 18:34 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
2013-07-18 18:34 ` Dave Hansen [this message]
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=51E83536.6070100@sr71.net \
--to=dave@sr71.net \
--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=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