On 17.06.2021 17:03, Anthony PERARD wrote: > On Thu, Jun 17, 2021 at 10:03:50AM +0200, Jan Beulich wrote: >> But it's not just XENMEM_maximum_gpfn that's affected; that's just the >> one pointing out the underlying issue. Plus if so, shouldn't we avoid >> returning values that are going to be truncated (and, as can be seen >> here, then get perhaps recognized as error codes up the call chain)? >> >>> For now, I'd agree with trying to undo the change in OVMF. >> >> Anthony, thoughts? > > I can map the shared_info page somewhere else, that fine. The hard part > is figuring out where. I can probably map it just after the guest RAM > (as described by the e820 from hvmloader or Xen).
Can't you put it (not necessarily immediately) next to the LAPIC page, for example? Or the IO-APIC one? Or somewhere in that area, which normally OSes won't use for placing BARs? Jan