From: Tom Lendacky <thomas.lendacky@amd.com>
To: Baoquan He <bhe@redhat.com>, linux-kernel@vger.kernel.org, bp@alien8.de
Cc: x86@kernel.org
Subject: Re: [PATCH 3/3] x86/mm: clean up unused parameters of functions
Date: Fri, 15 Nov 2024 08:27:50 -0600 [thread overview]
Message-ID: <a3b36643-f9cd-79d1-241d-a7aaddee49b7@amd.com> (raw)
In-Reply-To: <20241115012131.509226-4-bhe@redhat.com>
On 11/14/24 19:21, Baoquan He wrote:
> For functions memremap_is_efi_data(), memremap_is_setup_data and
> early_memremap_is_setup_data(), their parameter 'size' is not used
> and sometime cause confusion. Remove it now.
>
> Signed-off-by: Baoquan He <bhe@redhat.com>
Reviewed-by: Tom Lendacky <thomas.lendacky@amd.com>
> ---
> arch/x86/mm/ioremap.c | 17 +++++++----------
> 1 file changed, 7 insertions(+), 10 deletions(-)
>
> diff --git a/arch/x86/mm/ioremap.c b/arch/x86/mm/ioremap.c
> index 5d1b5e4a8756..71b282e5a4a0 100644
> --- a/arch/x86/mm/ioremap.c
> +++ b/arch/x86/mm/ioremap.c
> @@ -593,8 +593,7 @@ static bool memremap_should_map_decrypted(resource_size_t phys_addr,
> * Examine the physical address to determine if it is EFI data. Check
> * it against the boot params structure and EFI tables and memory types.
> */
> -static bool memremap_is_efi_data(resource_size_t phys_addr,
> - unsigned long size)
> +static bool memremap_is_efi_data(resource_size_t phys_addr)
> {
> u64 paddr;
>
> @@ -709,14 +708,12 @@ static bool __init __memremap_is_setup_data(resource_size_t phys_addr,
> }
> #undef SD_SIZE
>
> -static bool __ref memremap_is_setup_data(resource_size_t phys_addr,
> - unsigned long size)
> +static bool __ref memremap_is_setup_data(resource_size_t phys_addr)
> {
> return __memremap_is_setup_data(phys_addr, false);
> }
>
> -static bool __init early_memremap_is_setup_data(resource_size_t phys_addr,
> - unsigned long size)
> +static bool __init early_memremap_is_setup_data(resource_size_t phys_addr)
> {
> return __memremap_is_setup_data(phys_addr, true);
> }
> @@ -739,8 +736,8 @@ bool arch_memremap_can_ram_remap(resource_size_t phys_addr, unsigned long size,
> return false;
>
> if (cc_platform_has(CC_ATTR_HOST_MEM_ENCRYPT)) {
> - if (memremap_is_setup_data(phys_addr, size) ||
> - memremap_is_efi_data(phys_addr, size))
> + if (memremap_is_setup_data(phys_addr) ||
> + memremap_is_efi_data(phys_addr))
> return false;
> }
>
> @@ -765,8 +762,8 @@ pgprot_t __init early_memremap_pgprot_adjust(resource_size_t phys_addr,
> encrypted_prot = true;
>
> if (cc_platform_has(CC_ATTR_HOST_MEM_ENCRYPT)) {
> - if (early_memremap_is_setup_data(phys_addr, size) ||
> - memremap_is_efi_data(phys_addr, size))
> + if (early_memremap_is_setup_data(phys_addr) ||
> + memremap_is_efi_data(phys_addr))
> encrypted_prot = false;
> }
>
next prev parent reply other threads:[~2024-11-15 14:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 1:21 [PATCH 0/3] x86/ioremap: clean up the mess in xxx_is_setup_data Baoquan He
2024-11-15 1:21 ` [PATCH 1/3] x86/ioremap: introduce helper to check if physical address is in setup_data Baoquan He
2024-11-15 11:28 ` [tip: x86/mm] x86/ioremap: Introduce " tip-bot2 for Baoquan He
2024-11-15 14:22 ` [PATCH 1/3] x86/ioremap: introduce " Tom Lendacky
2024-11-15 23:25 ` Baoquan He
2024-11-15 1:21 ` [PATCH 2/3] x86/ioremap: use helper to implement xxx_is_setup_data() Baoquan He
2024-11-15 11:28 ` [tip: x86/mm] x86/ioremap: Use " tip-bot2 for Baoquan He
2024-11-15 14:24 ` [PATCH 2/3] x86/ioremap: use " Tom Lendacky
2024-11-16 8:36 ` Ingo Molnar
2024-11-16 13:28 ` Baoquan He
2024-11-15 1:21 ` [PATCH 3/3] x86/mm: clean up unused parameters of functions Baoquan He
2024-11-15 11:28 ` [tip: x86/mm] x86/mm: Clean " tip-bot2 for Baoquan He
2024-11-15 14:27 ` Tom Lendacky [this message]
2024-11-15 1:23 ` [PATCH 0/3] x86/ioremap: clean up the mess in xxx_is_setup_data Baoquan He
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=a3b36643-f9cd-79d1-241d-a7aaddee49b7@amd.com \
--to=thomas.lendacky@amd.com \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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
all inboxes | Powered by JetHome®