All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Juergen Gross <jgross@suse.com>
Subject: Re: ACPI NVS range conflicting with Dom0 page tables (or kernel image)
Date: Mon, 17 Jun 2024 16:03:01 +0200	[thread overview]
Message-ID: <ZnBCFgHltVqj2FDh@mail-itl> (raw)
In-Reply-To: <a5a8a016-2107-46fb-896b-2baaf66566d4@suse.com>

[-- Attachment #1: Type: text/plain, Size: 1908 bytes --]

On Mon, Jun 17, 2024 at 01:22:37PM +0200, Jan Beulich wrote:
> Hello,
> 
> while it feels like we had a similar situation before, I can't seem to be
> able to find traces thereof, or associated (Linux) commits.

Is it some AMD Threadripper system by a chance? Previous thread on this
issue:
https://lore.kernel.org/xen-devel/CAOCpoWdOH=xGxiQSC1c5Ueb1THxAjH4WiZbCZq-QT+d_KAk3SA@mail.gmail.com/

> With
> 
> (XEN)  Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x4000000
> ...
> (XEN)  Dom0 alloc.:   0000000440000000->0000000448000000 (619175 pages to be allocated)
> ...
> (XEN)  Loaded kernel: ffffffff81000000->ffffffff84000000
> 
> the kernel occupies the space from 16Mb to 64Mb in the initial allocation.
> Page tables come (almost) directly above:
> 
> (XEN)  Page tables:   ffffffff84001000->ffffffff84026000
> 
> I.e. they're just above the 64Mb boundary. Yet sadly in the host E820 map
> there is
> 
> (XEN)  [0000000004000000, 0000000004009fff] (ACPI NVS)
> 
> i.e. a non-RAM range starting at 64Mb. The kernel (currently) won't tolerate
> such an overlap (also if it was overlapping the kernel image, e.g. if on the
> machine in question s sufficiently much larger kernel was used). Yet with its
> fundamental goal of making its E820 match the host one I'm also in trouble
> thinking of possible solutions / workarounds. I certainly do not see Xen
> trying to cover for this, as the E820 map re-arrangement is purely a kernel
> side decision (forward ported kernels got away without, and what e.g. the
> BSDs do is entirely unknown to me).

In Qubes we have worked around the issue by moving the kernel lower
(CONFIG_PHYSICAL_START=0x200000):
https://github.com/QubesOS/qubes-linux-kernel/commit/3e8be4ac1682370977d4d0dc1d782c428d860282

Far from ideal, but gets it bootable...

-- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2024-06-17 14:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-17 11:22 ACPI NVS range conflicting with Dom0 page tables (or kernel image) Jan Beulich
2024-06-17 14:03 ` Marek Marczykowski-Górecki [this message]
2024-06-17 14:25   ` Jan Beulich
2024-06-24 14:07     ` Jürgen Groß
2024-08-06 14:12   ` Jürgen Groß
2024-08-06 15:21     ` Marek Marczykowski-Górecki
2024-08-06 15:24       ` Jürgen Groß
2024-08-07  7:37         ` Jan Beulich
2024-08-07 10:23         ` Marek Marczykowski-Górecki
2024-08-07 10:26           ` Jürgen Groß
2024-08-07 10:29             ` Marek Marczykowski-Górecki

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=ZnBCFgHltVqj2FDh@mail-itl \
    --to=marmarek@invisiblethingslab.com \
    --cc=jbeulich@suse.com \
    --cc=jgross@suse.com \
    --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 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.