[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b6c4347d-bd03-0332-c4a9-9d2a11f17a6a@intel.com>
Date: Thu, 1 Jun 2023 10:08:41 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Ross Lagerwall <ross.lagerwall@...rix.com>,
linux-kernel@...r.kernel.org, xen-devel@...ts.xenproject.org
Cc: Jan Beulich <jbeulich@...e.com>,
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>
Subject: Re: [PATCH v2] iscsi_ibft: Fix finding the iBFT under Xen Dom 0
On 6/1/23 09:57, Dave Hansen wrote:
> On 5/30/23 08:01, Ross Lagerwall wrote:
>> Since firmware doesn't indicate the iBFT in the E820, add a reserved
>> region so that it gets identity mapped when running as Dom 0 so that it
>> is possible to search for it. Move the call to reserve_ibft_region()
>> later so that it is called after the Xen identity mapping adjustments
>> are applied.
Oh, and one more thing:
What is the end user visible effect of this problem and of your solution?
Do Xen Dom 0 systems fail to find their boot iSCSI volume and refuse to
boot? I take it after this patch that they can boot again.
Powered by blists - more mailing lists