From: Jan Beulich <jbeulich@suse.com>
To: Juergen Gross <jgross@suse.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
xen-devel@lists.xenproject.org, x86@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] x86/xen: use clear_bss() for Xen PV guests
Date: Thu, 23 Jun 2022 11:51:42 +0200 [thread overview]
Message-ID: <117fd526-a241-2f01-47b5-e40e1803124b@suse.com> (raw)
In-Reply-To: <20220623094608.7294-2-jgross@suse.com>
On 23.06.2022 11:46, Juergen Gross wrote:
> --- a/arch/x86/xen/enlighten_pv.c
> +++ b/arch/x86/xen/enlighten_pv.c
> @@ -1183,15 +1183,19 @@ static void __init xen_domu_set_legacy_features(void)
> extern void early_xen_iret_patch(void);
>
> /* First C function to be called on Xen boot */
> -asmlinkage __visible void __init xen_start_kernel(void)
> +asmlinkage __visible void __init xen_start_kernel(struct start_info *si)
> {
> struct physdev_set_iopl set_iopl;
> unsigned long initrd_start = 0;
> int rc;
>
> - if (!xen_start_info)
> + if (!si)
> return;
>
> + clear_bss();
As per subsequent observation, this shouldn't really be needed: The
hypervisor (or tool stack for DomU-s) already does so. While I guess
we want to keep it to be on the safe side, maybe worth a comment?
Jan
next prev parent reply other threads:[~2022-06-23 9:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 9:46 [PATCH v2 0/3] x86: fix brk area initialization Juergen Gross
2022-06-23 9:46 ` [PATCH v2 1/3] x86/xen: use clear_bss() for Xen PV guests Juergen Gross
2022-06-23 9:51 ` Jan Beulich [this message]
2022-06-28 12:03 ` Juergen Gross
2022-06-23 9:46 ` [PATCH v2 2/3] x86: fix setup of brk area Juergen Gross
2022-06-29 17:14 ` Josh Poimboeuf
2022-06-30 6:55 ` Juergen Gross
2022-06-23 9:46 ` [PATCH v2 3/3] x86: fix .brk attribute in linker script Juergen Gross
2022-06-29 17:18 ` Josh Poimboeuf
2022-06-29 14:10 ` [PATCH v2 0/3] x86: fix brk area initialization Juergen Gross
2022-06-29 17:17 ` Boris Ostrovsky
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=117fd526-a241-2f01-47b5-e40e1803124b@suse.com \
--to=jbeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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®