linux-efi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: cuigaosheng <cuigaosheng1@huawei.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-efi <linux-efi@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	<wangweiyang2@huawei.com>
Subject: Re: [PATCH -next,v2] efi/libstub: arm32: Use "align" for the size alignment
Date: Mon, 8 Nov 2021 20:56:41 +0800	[thread overview]
Message-ID: <d9ea13ab-843d-0036-0a27-6083023f4712@huawei.com> (raw)
In-Reply-To: <CAMj1kXFE1Gv41TowKZHqkwn+WVLsAOqJSFbi706KbMC0G_rqgw@mail.gmail.com>

Hi Ard,

Thanks for your reply.

In my understanding address and size need to meet consistent alignment 
constraints,If I understand wrong, please reject this patch.

Best,

GaoSheng.

在 2021/11/4 17:26, Ard Biesheuvel 写道:
> On Tue, 2 Nov 2021 at 03:04, Gaosheng Cui <cuigaosheng1@huawei.com> wrote:
>> We are doing page-based allocations, and both the address
>> and size must meet alignment constraints, so using "align"
>> for the size alignment is a better choice.
>>
> Why is it a better choice? If I allocate a 2 MB aligned block of
> memory, why is it better to align the size to a multiple of 2 MB as
> well?
>
>
>> Signed-off-by: Gaosheng Cui <cuigaosheng1@huawei.com>
>> ---
>>   drivers/firmware/efi/libstub/randomalloc.c | 2 +-
>>   drivers/firmware/efi/libstub/relocate.c    | 2 +-
>>   2 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/firmware/efi/libstub/randomalloc.c b/drivers/firmware/efi/libstub/randomalloc.c
>> index 724155b9e10d..7b7159bb035d 100644
>> --- a/drivers/firmware/efi/libstub/randomalloc.c
>> +++ b/drivers/firmware/efi/libstub/randomalloc.c
>> @@ -76,7 +76,7 @@ efi_status_t efi_random_alloc(unsigned long size,
>>          if (align < EFI_ALLOC_ALIGN)
>>                  align = EFI_ALLOC_ALIGN;
>>
>> -       size = round_up(size, EFI_ALLOC_ALIGN);
>> +       size = round_up(size, align);
>>
>>          /* count the suitable slots in each memory map entry */
>>          for (map_offset = 0; map_offset < map_size; map_offset += desc_size) {
>> diff --git a/drivers/firmware/efi/libstub/relocate.c b/drivers/firmware/efi/libstub/relocate.c
>> index 8ee9eb2b9039..d6d27e8c23f8 100644
>> --- a/drivers/firmware/efi/libstub/relocate.c
>> +++ b/drivers/firmware/efi/libstub/relocate.c
>> @@ -50,7 +50,7 @@ efi_status_t efi_low_alloc_above(unsigned long size, unsigned long align,
>>          if (align < EFI_ALLOC_ALIGN)
>>                  align = EFI_ALLOC_ALIGN;
>>
>> -       size = round_up(size, EFI_ALLOC_ALIGN);
>> +       size = round_up(size, align);
>>          nr_pages = size / EFI_PAGE_SIZE;
>>          for (i = 0; i < map_size / desc_size; i++) {
>>                  efi_memory_desc_t *desc;
>> --
>> 2.30.0
>>
> .

      parent reply	other threads:[~2021-11-08 12:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-02  2:05 [PATCH -next,v2] efi/libstub: arm32: Use "align" for the size alignment Gaosheng Cui
2021-11-04  9:26 ` Ard Biesheuvel
2021-11-08 12:48   ` cuigaosheng
2021-11-08 12:56   ` cuigaosheng [this message]

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=d9ea13ab-843d-0036-0a27-6083023f4712@huawei.com \
    --to=cuigaosheng1@huawei.com \
    --cc=ardb@kernel.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wangweiyang2@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).