All of lore.kernel.org
 help / color / mirror / Atom feed
From: hdegoede@redhat.com (Hans de Goede)
To: linux-arm-kernel@lists.infradead.org
Subject: Memory size unaligned to section boundary
Date: Sat, 09 May 2015 15:54:00 +0200	[thread overview]
Message-ID: <554E1178.5030409@redhat.com> (raw)
In-Reply-To: <20150509134818.GP2067@n2100.arm.linux.org.uk>

Hi,

On 09-05-15 15:48, Russell King - ARM Linux wrote:
> On Sat, May 09, 2015 at 03:38:16PM +0200, Hans de Goede wrote:
>> Ok, so does that mean that Mark's original patch:
>>
>> ---->8----
>> diff --git a/arch/arm/mm/mmu.c b/arch/arm/mm/mmu.c
>> index 4e6ef89..2ea13f0 100644
>> --- a/arch/arm/mm/mmu.c
>> +++ b/arch/arm/mm/mmu.c
>> @@ -1125,9 +1125,9 @@ void __init sanity_check_meminfo(void)
>>                           * occurs before any free memory is mapped.
>>                           */
>>                          if (!memblock_limit) {
>> -                               if (!IS_ALIGNED(block_start, SECTION_SIZE))
>> +                               if (!IS_ALIGNED(block_start, PMD_SIZE))
>>                                          memblock_limit = block_start;
>> -                               else if (!IS_ALIGNED(block_end, SECTION_SIZE))
>> +                               else if (!IS_ALIGNED(block_end, PMD_SIZE))
>>                                          memblock_limit = arm_lowmem_limit;
>>                          }
>>
>> @@ -1142,7 +1142,7 @@ void __init sanity_check_meminfo(void)
>>           * last full section, which should be mapped.
>>           */
>>          if (memblock_limit)
>> -               memblock_limit = round_down(memblock_limit, SECTION_SIZE);
>> +               memblock_limit = round_down(memblock_limit, PMD_SIZE);
>>          if (!memblock_limit)
>>                  memblock_limit = arm_lowmem_limit;
>>
>>
>> Is good, or do we only need to have the last chunk of this patch ?
>
> That should do it, thanks.

"that should do it" means the entire patch or only the last chunk?

Regards,

Hans

  reply	other threads:[~2015-05-09 13:54 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-23 13:19 Memory size unaligned to section boundary Stefan Agner
2015-04-28 10:05 ` [REGRESSION?] ARM: 7677/1: LPAE: Fix mapping in alloc_init_section for unaligned addresses (was Re: Memory size unaligned to section boundary) Hans de Goede
2015-05-05 14:22   ` Mark Rutland
2015-05-05 14:38     ` Hans de Goede
2015-05-05 16:11       ` Mark Rutland
2015-05-09  0:48         ` Laura Abbott
2015-05-06 10:11 ` Memory size unaligned to section boundary Russell King - ARM Linux
2015-05-06 10:43   ` Mark Rutland
2015-05-06 10:51   ` Catalin Marinas
2015-05-06 11:35     ` Russell King - ARM Linux
2015-05-09 13:38       ` Hans de Goede
2015-05-09 13:48         ` Russell King - ARM Linux
2015-05-09 13:54           ` Hans de Goede [this message]
2015-05-09 13:54             ` Russell King - ARM Linux
2015-05-09 14:06               ` Hans de Goede
2015-05-11 10:31 ` [PATCH] ARM: mm: handle non-pmd-aligned end of RAM Mark Rutland
2015-05-11 11:43   ` Stefan Agner
2015-05-13 13:40     ` Hans de Goede
2015-05-13 14:11       ` Mark Rutland
2015-05-14 10:15         ` Russell King - ARM Linux
2015-05-12  2:54   ` Laura Abbott
2015-06-30 10:01   ` Javier Martinez Canillas
2015-07-01  8:13     ` Javier Martinez Canillas

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=554E1178.5030409@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.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.