From: Xishi Qiu <qiuxishi@huawei.com>
To: Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: "Luck, Tony" <tony.luck@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@kernel.org>,
Hanjun Guo <guohanjun@huawei.com>, Xiexiuqi <xiexiuqi@huawei.com>,
"leon@leon.nu" <leon@leon.nu>,
"Hansen, Dave" <dave.hansen@intel.com>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
Vlastimil Babka <vbabka@suse.cz>, Mel Gorman <mgorman@suse.de>,
Linux MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC v2 PATCH 7/8] mm: add the buddy system interface
Date: Tue, 30 Jun 2015 09:31:58 +0800 [thread overview]
Message-ID: <5591F18E.3060504@huawei.com> (raw)
In-Reply-To: <5591EA50.1000000@jp.fujitsu.com>
On 2015/6/30 9:01, Kamezawa Hiroyuki wrote:
> On 2015/06/30 8:11, Luck, Tony wrote:
>>> @@ -814,7 +814,7 @@ int __init_memblock memblock_clear_hotplug(phys_addr_t base, phys_addr_t size)
>>> */
>>> int __init_memblock memblock_mark_mirror(phys_addr_t base, phys_addr_t size)
>>> {
>>> - system_has_some_mirror = true;
>>> + static_key_slow_inc(&system_has_mirror);
>>>
>>> return memblock_setclr_flag(base, size, 1, MEMBLOCK_MIRROR);
>>> }
>>
>> This generates some WARN_ON noise when called from efi_find_mirror():
>>
>
> It seems jump_label_init() is called after memory initialization. (init/main.c::start_kernel())
> So, it may be difficut to use static_key function for our purpose because
> kernel memory allocation may occur before jump_label is ready.
>
> Thanks,
> -Kame
>
Hi Kame,
How about like this? Use static bool in bootmem, and use jump label in buddy system.
This means we use two variable to do it.
Thanks,
Xishi Qiu
>> [ 0.000000] e820: last_pfn = 0x7b800 max_arch_pfn = 0x400000000
>> [ 0.000000] ------------[ cut here ]------------
>> [ 0.000000] WARNING: CPU: 0 PID: 0 at kernel/jump_label.c:61 static_key_slow_inc+0x57/0xc0()
>> [ 0.000000] static_key_slow_inc used before call to jump_label_init
>> [ 0.000000] Modules linked in:
>>
>> [ 0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 4.1.0 #4
>> [ 0.000000] Hardware name: Intel Corporation BRICKLAND/BRICKLAND, BIOS BRHSXSD1.86B.0065.R01.1505011640 05/01/2015
>> [ 0.000000] 0000000000000000 ee366a8dff38f745 ffffffff81997d68 ffffffff816683b4
>> [ 0.000000] 0000000000000000 ffffffff81997dc0 ffffffff81997da8 ffffffff8107b0aa
>> [ 0.000000] ffffffff81d48822 ffffffff81f281a0 0000000040000000 0000001fcb7a4000
>> [ 0.000000] Call Trace:
>> [ 0.000000] [<ffffffff816683b4>] dump_stack+0x45/0x57
>> [ 0.000000] [<ffffffff8107b0aa>] warn_slowpath_common+0x8a/0xc0
>> [ 0.000000] [<ffffffff8107b135>] warn_slowpath_fmt+0x55/0x70
>> [ 0.000000] [<ffffffff81660273>] ? memblock_add_range+0x175/0x19e
>> [ 0.000000] [<ffffffff81176c57>] static_key_slow_inc+0x57/0xc0
>> [ 0.000000] [<ffffffff81660655>] memblock_mark_mirror+0x19/0x33
>> [ 0.000000] [<ffffffff81b12c18>] efi_find_mirror+0x59/0xdd
>> [ 0.000000] [<ffffffff81afb8a6>] setup_arch+0x642/0xccf
>> [ 0.000000] [<ffffffff81af3120>] ? early_idt_handler_array+0x120/0x120
>> [ 0.000000] [<ffffffff81663480>] ? printk+0x55/0x6b
>> [ 0.000000] [<ffffffff81af3120>] ? early_idt_handler_array+0x120/0x120
>> [ 0.000000] [<ffffffff81af3d93>] start_kernel+0xe8/0x4eb
>> [ 0.000000] [<ffffffff81af3120>] ? early_idt_handler_array+0x120/0x120
>> [ 0.000000] [<ffffffff81af3120>] ? early_idt_handler_array+0x120/0x120
>> [ 0.000000] [<ffffffff81af35ee>] x86_64_start_reservations+0x2a/0x2c
>> [ 0.000000] [<ffffffff81af373c>] x86_64_start_kernel+0x14c/0x16f
>> [ 0.000000] ---[ end trace baa7fa0514e3bc58 ]---
>> [ 0.000000] ------------[ cut here ]------------
>>
>>
>>
>>
>>
>
>
>
> .
>
--
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: Xishi Qiu <qiuxishi@huawei.com>
To: Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: "Luck, Tony" <tony.luck@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@kernel.org>,
Hanjun Guo <guohanjun@huawei.com>, Xiexiuqi <xiexiuqi@huawei.com>,
"leon@leon.nu" <leon@leon.nu>,
"Hansen, Dave" <dave.hansen@intel.com>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
Vlastimil Babka <vbabka@suse.cz>, Mel Gorman <mgorman@suse.de>,
Linux MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC v2 PATCH 7/8] mm: add the buddy system interface
Date: Tue, 30 Jun 2015 09:31:58 +0800 [thread overview]
Message-ID: <5591F18E.3060504@huawei.com> (raw)
In-Reply-To: <5591EA50.1000000@jp.fujitsu.com>
On 2015/6/30 9:01, Kamezawa Hiroyuki wrote:
> On 2015/06/30 8:11, Luck, Tony wrote:
>>> @@ -814,7 +814,7 @@ int __init_memblock memblock_clear_hotplug(phys_addr_t base, phys_addr_t size)
>>> */
>>> int __init_memblock memblock_mark_mirror(phys_addr_t base, phys_addr_t size)
>>> {
>>> - system_has_some_mirror = true;
>>> + static_key_slow_inc(&system_has_mirror);
>>>
>>> return memblock_setclr_flag(base, size, 1, MEMBLOCK_MIRROR);
>>> }
>>
>> This generates some WARN_ON noise when called from efi_find_mirror():
>>
>
> It seems jump_label_init() is called after memory initialization. (init/main.c::start_kernel())
> So, it may be difficut to use static_key function for our purpose because
> kernel memory allocation may occur before jump_label is ready.
>
> Thanks,
> -Kame
>
Hi Kame,
How about like this? Use static bool in bootmem, and use jump label in buddy system.
This means we use two variable to do it.
Thanks,
Xishi Qiu
>> [ 0.000000] e820: last_pfn = 0x7b800 max_arch_pfn = 0x400000000
>> [ 0.000000] ------------[ cut here ]------------
>> [ 0.000000] WARNING: CPU: 0 PID: 0 at kernel/jump_label.c:61 static_key_slow_inc+0x57/0xc0()
>> [ 0.000000] static_key_slow_inc used before call to jump_label_init
>> [ 0.000000] Modules linked in:
>>
>> [ 0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 4.1.0 #4
>> [ 0.000000] Hardware name: Intel Corporation BRICKLAND/BRICKLAND, BIOS BRHSXSD1.86B.0065.R01.1505011640 05/01/2015
>> [ 0.000000] 0000000000000000 ee366a8dff38f745 ffffffff81997d68 ffffffff816683b4
>> [ 0.000000] 0000000000000000 ffffffff81997dc0 ffffffff81997da8 ffffffff8107b0aa
>> [ 0.000000] ffffffff81d48822 ffffffff81f281a0 0000000040000000 0000001fcb7a4000
>> [ 0.000000] Call Trace:
>> [ 0.000000] [<ffffffff816683b4>] dump_stack+0x45/0x57
>> [ 0.000000] [<ffffffff8107b0aa>] warn_slowpath_common+0x8a/0xc0
>> [ 0.000000] [<ffffffff8107b135>] warn_slowpath_fmt+0x55/0x70
>> [ 0.000000] [<ffffffff81660273>] ? memblock_add_range+0x175/0x19e
>> [ 0.000000] [<ffffffff81176c57>] static_key_slow_inc+0x57/0xc0
>> [ 0.000000] [<ffffffff81660655>] memblock_mark_mirror+0x19/0x33
>> [ 0.000000] [<ffffffff81b12c18>] efi_find_mirror+0x59/0xdd
>> [ 0.000000] [<ffffffff81afb8a6>] setup_arch+0x642/0xccf
>> [ 0.000000] [<ffffffff81af3120>] ? early_idt_handler_array+0x120/0x120
>> [ 0.000000] [<ffffffff81663480>] ? printk+0x55/0x6b
>> [ 0.000000] [<ffffffff81af3120>] ? early_idt_handler_array+0x120/0x120
>> [ 0.000000] [<ffffffff81af3d93>] start_kernel+0xe8/0x4eb
>> [ 0.000000] [<ffffffff81af3120>] ? early_idt_handler_array+0x120/0x120
>> [ 0.000000] [<ffffffff81af3120>] ? early_idt_handler_array+0x120/0x120
>> [ 0.000000] [<ffffffff81af35ee>] x86_64_start_reservations+0x2a/0x2c
>> [ 0.000000] [<ffffffff81af373c>] x86_64_start_kernel+0x14c/0x16f
>> [ 0.000000] ---[ end trace baa7fa0514e3bc58 ]---
>> [ 0.000000] ------------[ cut here ]------------
>>
>>
>>
>>
>>
>
>
>
> .
>
next prev parent reply other threads:[~2015-06-30 1:41 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-27 2:19 [RFC v2 PATCH 0/8] mm: mirrored memory support for page buddy allocations Xishi Qiu
2015-06-27 2:19 ` Xishi Qiu
2015-06-27 2:23 ` [RFC v2 PATCH 1/8] mm: add a new config to manage the code Xishi Qiu
2015-06-27 2:23 ` Xishi Qiu
2015-06-29 6:50 ` Kamezawa Hiroyuki
2015-06-29 6:50 ` Kamezawa Hiroyuki
2015-06-30 2:52 ` Xishi Qiu
2015-06-30 2:52 ` Xishi Qiu
2015-06-27 2:24 ` [RFC v2 PATCH 2/8] mm: introduce MIGRATE_MIRROR to manage the mirrored pages Xishi Qiu
2015-06-27 2:24 ` Xishi Qiu
2015-06-29 7:32 ` Kamezawa Hiroyuki
2015-06-29 7:32 ` Kamezawa Hiroyuki
2015-06-30 2:45 ` Xishi Qiu
2015-06-30 2:45 ` Xishi Qiu
2015-06-30 7:53 ` Kamezawa Hiroyuki
2015-06-30 7:53 ` Kamezawa Hiroyuki
2015-06-30 9:22 ` Xishi Qiu
2015-06-30 9:22 ` Xishi Qiu
2015-06-27 2:24 ` [RFC v2 PATCH 3/8] mm: find mirrored memory in memblock Xishi Qiu
2015-06-27 2:24 ` Xishi Qiu
2015-06-27 2:25 ` [RFC v2 PATCH 4/8] mm: add mirrored memory to buddy system Xishi Qiu
2015-06-27 2:25 ` Xishi Qiu
2015-06-29 7:39 ` Kamezawa Hiroyuki
2015-06-29 7:39 ` Kamezawa Hiroyuki
2015-06-27 2:26 ` [RFC v2 PATCH 5/8] mm: introduce a new zone_stat_item NR_FREE_MIRROR_PAGES Xishi Qiu
2015-06-27 2:26 ` Xishi Qiu
2015-06-27 2:27 ` [RFC v2 PATCH 6/8] mm: add free mirrored pages info Xishi Qiu
2015-06-27 2:27 ` Xishi Qiu
2015-06-27 2:27 ` [RFC v2 PATCH 7/8] mm: add the buddy system interface Xishi Qiu
2015-06-27 2:27 ` Xishi Qiu
2015-06-29 23:11 ` Luck, Tony
2015-06-29 23:11 ` Luck, Tony
2015-06-30 1:01 ` Kamezawa Hiroyuki
2015-06-30 1:01 ` Kamezawa Hiroyuki
2015-06-30 1:31 ` Xishi Qiu [this message]
2015-06-30 1:31 ` Xishi Qiu
2015-06-30 2:01 ` Kamezawa Hiroyuki
2015-06-30 2:01 ` Kamezawa Hiroyuki
2015-06-27 2:28 ` [RFC v2 PATCH 8/8] mm: add the PCP interface Xishi Qiu
2015-06-27 2:28 ` Xishi Qiu
2015-06-29 15:19 ` [RFC v2 PATCH 0/8] mm: mirrored memory support for page buddy allocations Dave Hansen
2015-06-29 15:19 ` Dave Hansen
2015-06-30 1:26 ` Xishi Qiu
2015-06-30 1:26 ` Xishi Qiu
2015-06-30 1:52 ` Dave Hansen
2015-06-30 1:52 ` Dave Hansen
2015-06-30 2:48 ` Xishi Qiu
2015-06-30 2:48 ` Xishi Qiu
2015-06-30 9:41 ` Mel Gorman
2015-06-30 9:41 ` Mel Gorman
2015-06-30 10:46 ` Ingo Molnar
2015-06-30 10:46 ` Ingo Molnar
2015-06-30 11:53 ` Mel Gorman
2015-06-30 11:53 ` Mel Gorman
2015-06-30 18:12 ` Luck, Tony
2015-06-30 18:12 ` Luck, Tony
2015-07-13 4:56 ` Xishi Qiu
2015-07-13 4:56 ` Xishi Qiu
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=5591F18E.3060504@huawei.com \
--to=qiuxishi@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=guohanjun@huawei.com \
--cc=hpa@zytor.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=leon@leon.nu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=tony.luck@intel.com \
--cc=vbabka@suse.cz \
--cc=xiexiuqi@huawei.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.