[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6a2e6371-97a5-397d-ca1a-247b610b49d3@suse.com>
Date: Thu, 25 May 2023 11:31:23 +0200
From: Jan Beulich <jbeulich@...e.com>
To: Ross Lagerwall <ross.lagerwall@...rix.com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
Juergen Gross <jgross@...e.com>,
Boris Ostrovsky <boris.ostrovsky@...cle.com>,
Peter Jones <pjones@...hat.com>,
Konrad Rzeszutek Wilk <konrad@...nel.org>,
linux-kernel@...r.kernel.org, xen-devel@...ts.xenproject.org
Subject: Re: [PATCH] iscsi_ibft: Fix finding the iBFT under Xen Dom 0
On 24.05.2023 18:05, Ross Lagerwall wrote:
> --- a/arch/x86/xen/setup.c
> +++ b/arch/x86/xen/setup.c
> @@ -772,8 +772,14 @@ char * __init xen_memory_setup(void)
> * UNUSABLE regions in domUs are not handled and will need
> * a patch in the future.
> */
I think this comment now wants to move ...
> - if (xen_initial_domain())
> + if (xen_initial_domain()) {
... here. And then likely you want a blank line ...
> xen_ignore_unusable();
... here.
> + /* Reserve 0.5 MiB to 1 MiB region so iBFT can be found */
> + xen_e820_table.entries[xen_e820_table.nr_entries].addr = 0x80000;
> + xen_e820_table.entries[xen_e820_table.nr_entries].size = 0x80000;
> + xen_e820_table.entries[xen_e820_table.nr_entries].type = E820_TYPE_RESERVED;
> + xen_e820_table.nr_entries++;
Surely this can be omitted when !CONFIG_ISCSI_IBFT_FIND?
Jan
Powered by blists - more mailing lists