All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Toshi Kani <toshi.kani@hp.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, x86@kernel.org, dave@sr71.net,
	kosaki.motohiro@gmail.com, isimatu.yasuaki@jp.fujitsu.com,
	tangchen@cn.fujitsu.com, vasilis.liaskovitis@profitbricks.com
Subject: Re: [PATCH v2] mm/hotplug, x86: Disable ARCH_MEMORY_PROBE by default
Date: Thu, 25 Jul 2013 23:38:22 +0200	[thread overview]
Message-ID: <20130725213822.GG18254@gmail.com> (raw)
In-Reply-To: <1374685121.16322.218.camel@misato.fc.hp.com>


* Toshi Kani <toshi.kani@hp.com> wrote:

> > You claimed that the only purpose of this on x86 was 
> > that testing was done on non-hotplug systems, using 
> > this interface. Non-hotplug systems have e820 maps.
> 
> Right.  Sorry, I first thought that the interface needed 
> to work as defined, i.e. detect a new memory.  But for 
> the test purpose on non-hotplug systems, that is not 
> necessary.  So, I agree that we can check e820.
> 
> I summarized two options in the email below.
> https://lkml.org/lkml/2013/7/23/602
> 
> Option 1) adds a check with e820.  Option 2) deprecates 
> the interface by removing the config option from x86 
> Kconfig.  I was thinking that we could evaluate two 
> options after this patch gets in.  Does it make sense?

Yeah.

That having said, if the e820 check is too difficult to 
pull off straight away, I also don't mind keeping it as-is 
if it's useful for testing. Just make sure you document it 
as "you need to be careful with this" (beyond it being a 
root-only interface to begin with).

Thanks,

	Ingo

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

WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@kernel.org>
To: Toshi Kani <toshi.kani@hp.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, x86@kernel.org, dave@sr71.net,
	kosaki.motohiro@gmail.com, isimatu.yasuaki@jp.fujitsu.com,
	tangchen@cn.fujitsu.com, vasilis.liaskovitis@profitbricks.com
Subject: Re: [PATCH v2] mm/hotplug, x86: Disable ARCH_MEMORY_PROBE by default
Date: Thu, 25 Jul 2013 23:38:22 +0200	[thread overview]
Message-ID: <20130725213822.GG18254@gmail.com> (raw)
In-Reply-To: <1374685121.16322.218.camel@misato.fc.hp.com>


* Toshi Kani <toshi.kani@hp.com> wrote:

> > You claimed that the only purpose of this on x86 was 
> > that testing was done on non-hotplug systems, using 
> > this interface. Non-hotplug systems have e820 maps.
> 
> Right.  Sorry, I first thought that the interface needed 
> to work as defined, i.e. detect a new memory.  But for 
> the test purpose on non-hotplug systems, that is not 
> necessary.  So, I agree that we can check e820.
> 
> I summarized two options in the email below.
> https://lkml.org/lkml/2013/7/23/602
> 
> Option 1) adds a check with e820.  Option 2) deprecates 
> the interface by removing the config option from x86 
> Kconfig.  I was thinking that we could evaluate two 
> options after this patch gets in.  Does it make sense?

Yeah.

That having said, if the e820 check is too difficult to 
pull off straight away, I also don't mind keeping it as-is 
if it's useful for testing. Just make sure you document it 
as "you need to be careful with this" (beyond it being a 
root-only interface to begin with).

Thanks,

	Ingo

  reply	other threads:[~2013-07-25 21:38 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-19 17:47 [PATCH v2] mm/hotplug, x86: Disable ARCH_MEMORY_PROBE by default Toshi Kani
2013-07-19 17:47 ` Toshi Kani
2013-07-19 19:30 ` KOSAKI Motohiro
2013-07-19 19:30   ` KOSAKI Motohiro
2013-07-19 19:35   ` Toshi Kani
2013-07-19 19:35     ` Toshi Kani
2013-07-22  8:37 ` Ingo Molnar
2013-07-22  8:37   ` Ingo Molnar
2013-07-22 17:12   ` Toshi Kani
2013-07-22 17:12     ` Toshi Kani
2013-07-22 20:57     ` KOSAKI Motohiro
2013-07-22 20:57       ` KOSAKI Motohiro
2013-07-22 21:04       ` Dave Hansen
2013-07-22 21:04         ` Dave Hansen
2013-07-23  0:34       ` Toshi Kani
2013-07-23  0:34         ` Toshi Kani
2013-07-23  8:01     ` Ingo Molnar
2013-07-23  8:01       ` Ingo Molnar
2013-07-23 20:45       ` Toshi Kani
2013-07-23 20:45         ` Toshi Kani
2013-07-23 20:59         ` Dave Hansen
2013-07-23 20:59           ` Dave Hansen
2013-07-23 21:34           ` Toshi Kani
2013-07-23 21:34             ` Toshi Kani
2013-07-24  0:18         ` Hush Bensen
2013-07-24  0:18           ` Hush Bensen
2013-07-24 16:02           ` Toshi Kani
2013-07-24 16:02             ` Toshi Kani
2013-07-25  0:17             ` Hush Bensen
2013-07-25  0:17               ` Hush Bensen
2013-07-25 15:47               ` Toshi Kani
2013-07-25 15:47                 ` Toshi Kani
2013-07-25  0:44             ` Hush Bensen
2013-07-25  0:44               ` Hush Bensen
2013-07-25  0:56             ` Hush Bensen
2013-07-25  0:56               ` Hush Bensen
2013-07-25  3:08               ` Yasuaki Ishimatsu
2013-07-25  3:08                 ` Yasuaki Ishimatsu
2013-07-25  3:34                 ` Hush Bensen
2013-07-25  3:34                   ` Hush Bensen
2013-07-25  4:55                   ` Yasuaki Ishimatsu
2013-07-25  4:55                     ` Yasuaki Ishimatsu
2013-07-24  4:20         ` Ingo Molnar
2013-07-24  4:20           ` Ingo Molnar
2013-07-24 16:58           ` Toshi Kani
2013-07-24 16:58             ` Toshi Kani
2013-07-25 21:38             ` Ingo Molnar [this message]
2013-07-25 21:38               ` Ingo Molnar
2013-07-25 22:36               ` Toshi Kani
2013-07-25 22:36                 ` Toshi Kani
2013-07-23  0:24 ` Yasuaki Ishimatsu
2013-07-23  0:24   ` Yasuaki Ishimatsu
2013-07-23  0:45   ` Toshi Kani
2013-07-23  0:45     ` Toshi Kani
2013-07-23  7:46 ` [tip:x86/mm] " tip-bot for 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=20130725213822.GG18254@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=dave@sr71.net \
    --cc=isimatu.yasuaki@jp.fujitsu.com \
    --cc=kosaki.motohiro@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.