All of lore.kernel.org
 help / color / mirror / Atom feed
From: KOSAKI Motohiro <kosaki.motohiro@gmail.com>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Li Zhong <zhong@linux.vnet.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	nfont@linux.vnet.ibm.com, Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [RFC PATCH] memory driver: make phys_index/end_phys_index reflect the start/end section number
Date: Thu, 3 Apr 2014 18:41:48 -0400	[thread overview]
Message-ID: <CAHGf_=r-zMMuTLy7QKw7K63A29xXd2fY3bqKRPp-wOvHXWU4AA@mail.gmail.com> (raw)
In-Reply-To: <533C362E.1020605@intel.com>

On Wed, Apr 2, 2014 at 12:09 PM, Dave Hansen <dave.hansen@intel.com> wrote:
> On 04/02/2014 01:56 AM, Li Zhong wrote:
>> I noticed the phys_index and end_phys_index under
>> /sys/devices/system/memory/memoryXXX/ have the same value, e.g.
>> (for the test machine, one memory block has 8 sections, that is
>>  sections_per_block equals 8)
>>
>> # cd /sys/devices/system/memory/memory100/
>> # cat phys_index end_phys_index
>> 00000064
>> 00000064
>>
>> Seems they should reflect the start/end section number respectively, which
>> also matches what is said in Documentation/memory-hotplug.txt
>
> This changes a user-visible interface.  Won't this break userspace?

But who uses this? This is totally broken and I think nobody can use
meaningfully.
I bet we can fix this right now.

  parent reply	other threads:[~2014-04-03 22:42 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-02  8:56 [RFC PATCH] memory driver: make phys_index/end_phys_index reflect the start/end section number Li Zhong
2014-04-02 16:09 ` Dave Hansen
2014-04-03  1:50   ` Li Zhong
2014-04-03 22:41   ` KOSAKI Motohiro [this message]
2014-04-03  1:37 ` Zhang Yanfei
2014-04-03  2:37   ` Li Zhong
2014-04-03  3:06     ` Zhang Yanfei
2014-04-03  6:45       ` Li Zhong
2014-04-04  1:29 ` Yasuaki Ishimatsu
2014-04-08  8:27   ` Li Zhong
2014-04-08 16:13     ` Dave Hansen
2014-04-08 18:23       ` Nathan Fontenot
2014-04-08 19:47         ` Dave Hansen
2014-04-09  9:20           ` Li Zhong
2014-04-09 15:49             ` Dave Hansen
2014-04-09 16:16               ` Nathan Fontenot
2014-04-10  3:14               ` Li Zhong
2014-04-10  3:47                 ` Zhang Yanfei
2014-04-09 16:20           ` Nathan Fontenot
2014-04-09 17:39           ` Nathan Fontenot
2014-04-10  1:03             ` Zhang Yanfei
2014-04-10  4:17             ` Li Zhong
2014-04-11 18:54               ` Nathan Fontenot
2014-04-14  8:43                 ` [RFC PATCH v2] memory-hotplug: Update documentation to hide information about SECTIONS and remove end_phys_index Li Zhong
2014-04-14  9:13                   ` Zhang Yanfei
2014-04-15  2:49                     ` Li Zhong
2014-04-16  1:49                     ` [RFC PATCH v3] " Li Zhong

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_=r-zMMuTLy7QKw7K63A29xXd2fY3bqKRPp-wOvHXWU4AA@mail.gmail.com' \
    --to=kosaki.motohiro@gmail.com \
    --cc=dave.hansen@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfont@linux.vnet.ibm.com \
    --cc=zhong@linux.vnet.ibm.com \
    /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.