All of lore.kernel.org
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Dave Hansen <dave.hansen@intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>,
	Grygorii Strashko <grygorii.strashko@ti.com>,
	Linux-MM <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>, Tejun Heo <tj@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Panic on 8-node system in memblock_virt_alloc_try_nid()
Date: Fri, 24 Jan 2014 02:22:47 -0500	[thread overview]
Message-ID: <52E214C7.9050309@ti.com> (raw)
In-Reply-To: <CAE9FiQWRkP1Hir6UFuPRGu6bXNd_SHonuaC-MG1UD-tSeE0teQ@mail.gmail.com>

On Friday 24 January 2014 02:04 AM, Yinghai Lu wrote:
> On Thu, Jan 23, 2014 at 10:56 PM, Santosh Shilimkar
> <santosh.shilimkar@ti.com> wrote:
>> On Friday 24 January 2014 01:38 AM, Santosh Shilimkar wrote:
> 
>> The patch which is now commit 457ff1d {lib/swiotlb.c: use
>> memblock apis for early memory allocations} was the breaking the
>> boot on Andrew's machine. Now if I look back the patch, based on your
>> above description, I believe below hunk waS/is the culprit.
>>
>> @@ -172,8 +172,9 @@ int __init swiotlb_init_with_tbl(char *tlb, unsigned long nslabs, int verbose)
>>         /*
>>          * Get the overflow emergency buffer
>>          */
>> -       v_overflow_buffer = alloc_bootmem_low_pages_nopanic(
>> -                                               PAGE_ALIGN(io_tlb_overflow));
>> +       v_overflow_buffer = memblock_virt_alloc_nopanic(
>> +                                               PAGE_ALIGN(io_tlb_overflow),
>> +                                               PAGE_SIZE);
>>         if (!v_overflow_buffer)
>>                 return -ENOMEM;
>>
>>
>> Looks like 'v_overflow_buffer' must be allocated from low memory in this
>> case. Is that correct ?
> 
> yes.
> 
> but should the change like following
> 
> commit 457ff1de2d247d9b8917c4664c2325321a35e313
> Author: Santosh Shilimkar <santosh.shilimkar@ti.com>
> Date:   Tue Jan 21 15:50:30 2014 -0800
> 
>     lib/swiotlb.c: use memblock apis for early memory allocations
> 
> 
> @@ -215,13 +220,13 @@ swiotlb_init(int verbose)
>         bytes = io_tlb_nslabs << IO_TLB_SHIFT;
> 
>         /* Get IO TLB memory from the low pages */
> -       vstart = alloc_bootmem_low_pages_nopanic(PAGE_ALIGN(bytes));
> +       vstart = memblock_virt_alloc_nopanic(PAGE_ALIGN(bytes), PAGE_SIZE);
>         if (vstart && !swiotlb_init_with_tbl(vstart, io_tlb_nslabs, verbose))
>                 return;
> 
OK. So we need '__alloc_bootmem_low()' equivalent memblock API. We will try
to come up with a patch for the same. Thanks for inputs.

Regards,
Santosh

--
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: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Dave Hansen <dave.hansen@intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>,
	Grygorii Strashko <grygorii.strashko@ti.com>,
	Linux-MM <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>, Tejun Heo <tj@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Panic on 8-node system in memblock_virt_alloc_try_nid()
Date: Fri, 24 Jan 2014 02:22:47 -0500	[thread overview]
Message-ID: <52E214C7.9050309@ti.com> (raw)
In-Reply-To: <CAE9FiQWRkP1Hir6UFuPRGu6bXNd_SHonuaC-MG1UD-tSeE0teQ@mail.gmail.com>

On Friday 24 January 2014 02:04 AM, Yinghai Lu wrote:
> On Thu, Jan 23, 2014 at 10:56 PM, Santosh Shilimkar
> <santosh.shilimkar@ti.com> wrote:
>> On Friday 24 January 2014 01:38 AM, Santosh Shilimkar wrote:
> 
>> The patch which is now commit 457ff1d {lib/swiotlb.c: use
>> memblock apis for early memory allocations} was the breaking the
>> boot on Andrew's machine. Now if I look back the patch, based on your
>> above description, I believe below hunk waS/is the culprit.
>>
>> @@ -172,8 +172,9 @@ int __init swiotlb_init_with_tbl(char *tlb, unsigned long nslabs, int verbose)
>>         /*
>>          * Get the overflow emergency buffer
>>          */
>> -       v_overflow_buffer = alloc_bootmem_low_pages_nopanic(
>> -                                               PAGE_ALIGN(io_tlb_overflow));
>> +       v_overflow_buffer = memblock_virt_alloc_nopanic(
>> +                                               PAGE_ALIGN(io_tlb_overflow),
>> +                                               PAGE_SIZE);
>>         if (!v_overflow_buffer)
>>                 return -ENOMEM;
>>
>>
>> Looks like 'v_overflow_buffer' must be allocated from low memory in this
>> case. Is that correct ?
> 
> yes.
> 
> but should the change like following
> 
> commit 457ff1de2d247d9b8917c4664c2325321a35e313
> Author: Santosh Shilimkar <santosh.shilimkar@ti.com>
> Date:   Tue Jan 21 15:50:30 2014 -0800
> 
>     lib/swiotlb.c: use memblock apis for early memory allocations
> 
> 
> @@ -215,13 +220,13 @@ swiotlb_init(int verbose)
>         bytes = io_tlb_nslabs << IO_TLB_SHIFT;
> 
>         /* Get IO TLB memory from the low pages */
> -       vstart = alloc_bootmem_low_pages_nopanic(PAGE_ALIGN(bytes));
> +       vstart = memblock_virt_alloc_nopanic(PAGE_ALIGN(bytes), PAGE_SIZE);
>         if (vstart && !swiotlb_init_with_tbl(vstart, io_tlb_nslabs, verbose))
>                 return;
> 
OK. So we need '__alloc_bootmem_low()' equivalent memblock API. We will try
to come up with a patch for the same. Thanks for inputs.

Regards,
Santosh

  reply	other threads:[~2014-01-24  7:23 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-23 22:49 Panic on 8-node system in memblock_virt_alloc_try_nid() Dave Hansen
2014-01-23 22:49 ` Dave Hansen
2014-01-24  0:27 ` Dave Hansen
2014-01-24  0:27   ` Dave Hansen
2014-01-24  3:43 ` Santosh Shilimkar
2014-01-24  3:43   ` Santosh Shilimkar
2014-01-24  5:55 ` Yinghai Lu
2014-01-24  6:38   ` Santosh Shilimkar
2014-01-24  6:38     ` Santosh Shilimkar
2014-01-24  6:56     ` Santosh Shilimkar
2014-01-24  6:56       ` Santosh Shilimkar
2014-01-24  7:04       ` Yinghai Lu
2014-01-24  7:04         ` Yinghai Lu
2014-01-24  7:22         ` Santosh Shilimkar [this message]
2014-01-24  7:22           ` Santosh Shilimkar
2014-01-24  7:46           ` Yinghai Lu
2014-01-24  7:54             ` Santosh Shilimkar
2014-01-24  7:54               ` Santosh Shilimkar
2014-01-24  6:57     ` Yinghai Lu
2014-01-24  6:57       ` Yinghai Lu
2014-01-24  7:04       ` Andrew Morton
2014-01-24  7:04         ` Andrew Morton
2014-01-24 15:01   ` Dave Hansen
2014-01-24 15:01     ` Dave Hansen
2014-01-24 15:25     ` Dave Hansen
2014-01-24 15:25       ` Dave Hansen
2014-01-24 17:45     ` Yinghai Lu
2014-01-24 17:45       ` Yinghai Lu
2014-01-24 18:09       ` Dave Hansen
2014-01-24 18:09         ` Dave Hansen
2014-01-24 18:13         ` Yinghai Lu
2014-01-24 18:13           ` Yinghai Lu
2014-01-24 18:19           ` Dave Hansen
2014-01-24 18:24             ` Yinghai Lu
2014-01-24 18:24               ` Yinghai Lu
2014-01-24 18:42               ` Dave Hansen
2014-01-24 18:42                 ` Dave Hansen
2014-01-24 18:51                 ` Yinghai Lu
2014-01-24 18:51                   ` Yinghai Lu

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=52E214C7.9050309@ti.com \
    --to=santosh.shilimkar@ti.com \
    --cc=akpm@linux-foundation.org \
    --cc=dave.hansen@intel.com \
    --cc=grygorii.strashko@ti.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    --cc=tj@kernel.org \
    --cc=yinghai@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.