From: Ingo Molnar <mingo@kernel.org>
To: Mike Rapoport <rppt@kernel.org>
Cc: x86@kernel.org, Andy Lutomirski <luto@kernel.org>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
Ning Sun <ning.sun@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, tboot-devel@lists.sourceforge.net
Subject: Re: [PATCH 2/4] x86/boot: split kernel resources setup into a helper function
Date: Thu, 5 Dec 2024 14:32:59 +0100 [thread overview]
Message-ID: <Z1Gri651igCkRVsx@gmail.com> (raw)
In-Reply-To: <20241203112525.591496-3-rppt@kernel.org>
* Mike Rapoport <rppt@kernel.org> wrote:
> From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
>
> Makes setup_arch a bit easier to comprehend.
>
> No functional changes.
>
> Signed-off-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> ---
> arch/x86/kernel/setup.c | 36 ++++++++++++++++++++++--------------
> 1 file changed, 22 insertions(+), 14 deletions(-)
>
> diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
> index 2383e73fc140..d299fe5bda25 100644
> --- a/arch/x86/kernel/setup.c
> +++ b/arch/x86/kernel/setup.c
> @@ -524,6 +524,23 @@ void __init reserve_standard_io_resources(void)
>
> }
>
> +static void __init setup_kernel_resources(void)
> +{
> + code_resource.start = __pa_symbol(_text);
> + code_resource.end = __pa_symbol(_etext)-1;
> + rodata_resource.start = __pa_symbol(__start_rodata);
> + rodata_resource.end = __pa_symbol(__end_rodata)-1;
> + data_resource.start = __pa_symbol(_sdata);
> + data_resource.end = __pa_symbol(_edata)-1;
> + bss_resource.start = __pa_symbol(__bss_start);
> + bss_resource.end = __pa_symbol(__bss_stop)-1;
> +
> + insert_resource(&iomem_resource, &code_resource);
> + insert_resource(&iomem_resource, &rodata_resource);
> + insert_resource(&iomem_resource, &data_resource);
> + insert_resource(&iomem_resource, &bss_resource);
> +}
> +
> static bool __init snb_gfx_workaround_needed(void)
> {
> #ifdef CONFIG_PCI
> @@ -842,15 +859,6 @@ void __init setup_arch(char **cmdline_p)
> root_mountflags &= ~MS_RDONLY;
> setup_initial_init_mm(_text, _etext, _edata, (void *)_brk_end);
>
> - code_resource.start = __pa_symbol(_text);
> - code_resource.end = __pa_symbol(_etext)-1;
> - rodata_resource.start = __pa_symbol(__start_rodata);
> - rodata_resource.end = __pa_symbol(__end_rodata)-1;
> - data_resource.start = __pa_symbol(_sdata);
> - data_resource.end = __pa_symbol(_edata)-1;
> - bss_resource.start = __pa_symbol(__bss_start);
> - bss_resource.end = __pa_symbol(__bss_stop)-1;
> -
> /*
> * x86_configure_nx() is called before parse_early_param() to detect
> * whether hardware doesn't support NX (so that the early EHCI debug
> @@ -894,11 +902,11 @@ void __init setup_arch(char **cmdline_p)
> tsc_early_init();
> x86_init.resources.probe_roms();
>
> - /* after parse_early_param, so could debug it */
> - insert_resource(&iomem_resource, &code_resource);
> - insert_resource(&iomem_resource, &rodata_resource);
> - insert_resource(&iomem_resource, &data_resource);
> - insert_resource(&iomem_resource, &bss_resource);
> + /*
> + * Add resources for kernel text and data to the iomem_resource
Missing full stop.
> + * Do it eafter parse_early_param, so could debug it
Typo...
Also, this sentence isn't proper English AFAICS.
Please do not submit write-only comments...
Thanks,
Ingo
next prev parent reply other threads:[~2024-12-05 13:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 11:25 [PATCH 0/4] x86/boot: a few cleanups Mike Rapoport
2024-12-03 11:25 ` [PATCH 1/4] x86/boot: move setting of memblock parameters to e820__memblock_setup() Mike Rapoport
2024-12-03 11:25 ` [PATCH 2/4] x86/boot: split kernel resources setup into a helper function Mike Rapoport
2024-12-05 13:32 ` Ingo Molnar [this message]
2024-12-03 11:25 ` [PATCH 3/4] x86/boot: split parsing of boot_params " Mike Rapoport
2024-12-05 13:31 ` Ingo Molnar
2024-12-03 11:25 ` [PATCH 4/4] x86/e820: drop E820_TYPE_RESERVED_KERN and related code Mike Rapoport
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=Z1Gri651igCkRVsx@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=ning.sun@intel.com \
--cc=peterz@infradead.org \
--cc=rppt@kernel.org \
--cc=tboot-devel@lists.sourceforge.net \
--cc=tglx@linutronix.de \
--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 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.