devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Usama Arif <usamaarif642@gmail.com>
To: Saravana Kannan <saravanak@google.com>
Cc: mark.rutland@arm.com, will@kernel.org, leitao@debian.org,
	catalin.marinas@arm.com, robh@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	kexec@lists.infradead.org
Subject: Re: [PATCH] of/kexec: save pa of initial_boot_params for arm64 and use it at kexec
Date: Mon, 7 Oct 2024 14:54:07 +0100	[thread overview]
Message-ID: <b14ac6d4-9d29-4193-ac2f-7e7d7ae3a60a@gmail.com> (raw)
In-Reply-To: <CAGETcx9r+VwMBt=Ra-+-ZFgO66DK1LGjbT8cXFZ7v-c-N20qTQ@mail.gmail.com>



On 03/10/2024 21:20, Saravana Kannan wrote:
> On Thu, Oct 3, 2024 at 4:38 AM Usama Arif <usamaarif642@gmail.com> wrote:
>>
>>  __pa() is only intended to be used for linear map addresses and using
>> it for initial_boot_params which is in fixmap for arm64 will give an
>> incorrect value. Hence stash the physical address when it is known at
>> boot time and use it at kexec time instead of converting the virtual
>> address using __pa().
>>
>> Reported-by: Breno Leitao <leitao@debian.org>
>> Suggested-by: Mark Rutland <mark.rutland@arm.com>
>> Signed-off-by: Usama Arif <usamaarif642@gmail.com>
>> Fixes: ac10be5cdbfa ("arm64: Use common of_kexec_alloc_and_setup_fdt()")
>> ---
>>  arch/arm64/kernel/setup.c | 8 ++++++++
>>  drivers/of/fdt.c          | 6 ++++++
>>  drivers/of/kexec.c        | 8 ++++++--
>>  include/linux/of_fdt.h    | 2 ++
>>  4 files changed, 22 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/arm64/kernel/setup.c b/arch/arm64/kernel/setup.c
>> index b22d28ec8028..a4d96f5e2e05 100644
>> --- a/arch/arm64/kernel/setup.c
>> +++ b/arch/arm64/kernel/setup.c
>> @@ -194,6 +194,14 @@ static void __init setup_machine_fdt(phys_addr_t dt_phys)
>>         /* Early fixups are done, map the FDT as read-only now */
>>         fixmap_remap_fdt(dt_phys, &size, PAGE_KERNEL_RO);
>>
>> +       /*
>> +        * Save dt_phys address so that it can be used later for kexec. This
>> +        * is done as __pa() is only intended to be used for linear map addresses
>> +        * and using it for initial_boot_params which is in fixmap will give an
>> +        * incorrect value.
>> +        */
>> +       set_initial_boot_params_pa(dt_phys);
>> +
>>         name = of_flat_dt_get_machine_name();
>>         if (!name)
>>                 return;
>> diff --git a/drivers/of/fdt.c b/drivers/of/fdt.c
>> index 4d528c10df3a..9e312b7c246e 100644
>> --- a/drivers/of/fdt.c
>> +++ b/drivers/of/fdt.c
>> @@ -457,6 +457,7 @@ int __initdata dt_root_addr_cells;
>>  int __initdata dt_root_size_cells;
>>
>>  void *initial_boot_params __ro_after_init;
>> +phys_addr_t initial_boot_params_pa __ro_after_init;
>>
>>  #ifdef CONFIG_OF_EARLY_FLATTREE
>>
>> @@ -1185,6 +1186,11 @@ bool __init early_init_dt_scan(void *params)
>>         return true;
>>  }
>>
>> +void __init set_initial_boot_params_pa(phys_addr_t params)
>> +{
>> +       initial_boot_params_pa = params;
>> +}
>> +
>>  static void *__init copy_device_tree(void *fdt)
>>  {
>>         int size;
>> diff --git a/drivers/of/kexec.c b/drivers/of/kexec.c
>> index 9ccde2fd77cb..ca9f27b27f71 100644
>> --- a/drivers/of/kexec.c
>> +++ b/drivers/of/kexec.c
>> @@ -300,8 +300,12 @@ void *of_kexec_alloc_and_setup_fdt(const struct kimage *image,
>>                 goto out;
>>         }
>>
>> -       /* Remove memory reservation for the current device tree. */
>> -       ret = fdt_find_and_del_mem_rsv(fdt, __pa(initial_boot_params),
>> +       /* Remove memory reservation for the current device tree.
>> +        * For arm64, initial_boot_params is a fixmap address, hence __pa(),
>> +        * can't be used to get the physical address.
>> +        */
>> +       ret = fdt_find_and_del_mem_rsv(fdt, IS_ENABLED(CONFIG_ARM64) ?
>> +                                      initial_boot_params_pa : __pa(initial_boot_params),
>>                                        fdt_totalsize(initial_boot_params));
> 
> Not sure about the correctness of the patch (not a kexec expert) but
> no need to do all of this inside a function parameter. Just create a
> variable and use it here.
> 
> -Saravana
> 

Thanks, will do in the next revision.


  reply	other threads:[~2024-10-07 13:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-03 11:38 [PATCH] of/kexec: save pa of initial_boot_params for arm64 and use it at kexec Usama Arif
2024-10-03 20:20 ` Saravana Kannan
2024-10-07 13:54   ` Usama Arif [this message]
2024-10-04  0:03 ` Rob Herring
2024-10-07 14:06   ` Usama Arif
2024-10-07 14:39     ` Rob Herring
2024-10-07 15:30       ` Usama Arif
2024-10-23  9:38         ` Usama Arif
2024-10-23 13:40         ` Rob Herring
2024-10-23 14:43           ` Usama Arif
2024-10-23 15:17             ` Rob Herring
2024-10-23 15:24               ` Usama Arif

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=b14ac6d4-9d29-4193-ac2f-7e7d7ae3a60a@gmail.com \
    --to=usamaarif642@gmail.com \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kexec@lists.infradead.org \
    --cc=leitao@debian.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh@kernel.org \
    --cc=saravanak@google.com \
    --cc=will@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 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).