All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: "Jan Beulich" <jbeulich@suse.com>,
	"Juergen Gross" <jgross@suse.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>
Cc: Patrick Plenefisch <simonpatp@gmail.com>,
	xen-devel@lists.xenproject.org,
	Jason Andryuk <jandryuk@gmail.com>
Subject: Re: E820 memory allocation issue on Threadripper platforms
Date: Sun, 10 Mar 2024 15:06:45 +0100	[thread overview]
Message-ID: <Ze2-dkQkn41WJ60v@mail-itl> (raw)
In-Reply-To: <Zap7uX3k0kfoMOoF@mail-itl>

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

On Fri, Jan 19, 2024 at 02:40:06PM +0100, Marek Marczykowski-Górecki wrote:
> On Thu, Jan 18, 2024 at 01:23:56AM -0500, Patrick Plenefisch wrote:
> > On Wed, Jan 17, 2024 at 3:46 AM Jan Beulich <jbeulich@suse.com> wrote:
> > > On 17.01.2024 07:12, Patrick Plenefisch wrote:
> > > > As someone who hasn't built a kernel in over a decade, should I figure
> > > out
> > > > how to do a kernel build with CONFIG_PHYSICAL_START=0x2000000 and report
> > > > back?
> > >
> > > That was largely a suggestion to perhaps allow you to gain some
> > > workable setup. It would be of interest to us largely for completeness.
> > >
> > 
> > Typo aside, setting the boot to 2MiB works! It works better for PV
> 
> Are there any downsides of running kernel with
> CONFIG_PHYSICAL_START=0x200000? I can confirm it fixes the issue on
> another affected system, and if there aren't any practical downsides,
> I'm tempted to change it the default kernel in Qubes OS.

I have the answer here: CONFIG_PHYSICAL_START=0x200000 breaks booting
Xen in KVM with OVMF. There, the memory map has:
(XEN)  0000000100000-00000007fffff type=7 attr=000000000000000f
(XEN)  0000000800000-0000000807fff type=10 attr=000000000000000f
(XEN)  0000000808000-000000080afff type=7 attr=000000000000000f
(XEN)  000000080b000-000000080bfff type=10 attr=000000000000000f
(XEN)  000000080c000-000000080ffff type=7 attr=000000000000000f
(XEN)  0000000810000-00000008fffff type=10 attr=000000000000000f
(XEN)  0000000900000-00000015fffff type=4 attr=000000000000000f

So, starting at 0x1000000 worked since type=4 (boot service data) is
available at that time already, but with 0x200000 it conflicts with
those AcpiNvs areas around 0x800000.

I'm cc-ing Jason since I see he claimed relevant gitlab issue. This
conflict at least gives easy test environment with console logged to a
file.

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

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

  parent reply	other threads:[~2024-03-10 14:07 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-11  2:29 E820 memory allocation issue on Threadripper platforms Patrick Plenefisch
2024-01-11  8:37 ` Jan Beulich
2024-01-11  9:19   ` Xenia Ragiadakou
2024-01-11 10:13   ` Juergen Gross
2024-01-16  0:22     ` Patrick Plenefisch
2024-01-16  9:33       ` Jan Beulich
2024-01-17  6:12         ` Patrick Plenefisch
2024-01-17  8:46           ` Jan Beulich
2024-01-17 10:13             ` Roger Pau Monné
2024-01-17 10:40               ` Jan Beulich
2024-01-17 12:54                 ` Roger Pau Monné
2024-06-24 12:40                   ` Branden Sherrell
2024-06-24 12:54                     ` Jan Beulich
2024-06-24 13:07                       ` Branden Sherrell
2024-06-24 13:40                         ` Jan Beulich
2024-06-24 16:17                           ` Branden Sherrell
2024-01-18  6:23             ` Patrick Plenefisch
2024-01-18  8:27               ` Roger Pau Monné
2024-01-18  8:34                 ` Patrick Plenefisch
2024-01-18  9:46                   ` Roger Pau Monné
2024-01-18 12:41                     ` ACPI VFCT table too short on PVH dom0 (was: Re: E820 memory allocation issue on Threadripper platforms) Roger Pau Monné
2024-01-19  7:44                       ` Patrick Plenefisch
2024-01-19  9:54                         ` Huang Rui
2024-01-19 15:32                           ` Deucher, Alexander
2024-01-21  1:27                           ` Patrick Plenefisch
2024-01-19 11:06                         ` Roger Pau Monné
2024-01-21  1:33                           ` Patrick Plenefisch
2024-01-24  1:27                             ` Patrick Plenefisch
2024-01-24  8:23                               ` Roger Pau Monné
2024-01-25  0:20                                 ` Patrick Plenefisch
2024-01-18 16:03                     ` E820 memory allocation issue on Threadripper platforms Patrick Plenefisch
2024-01-18  9:01               ` Jan Beulich
2024-01-19 13:40               ` Marek Marczykowski-Górecki
2024-01-19 13:50                 ` Jan Beulich
2024-01-19 14:31                   ` Marek Marczykowski-Górecki
2024-03-10 14:06                 ` Marek Marczykowski-Górecki [this message]
2024-03-12 21:07                   ` Jason Andryuk
2024-03-12 22:00                     ` Marek Marczykowski-Górecki
2024-01-17  8:46           ` Roger Pau Monné
2024-01-17 12:06         ` Marek Marczykowski-Górecki
2024-01-17 12:59           ` Roger Pau Monné
2024-01-17 13:40             ` Jan Beulich

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=Ze2-dkQkn41WJ60v@mail-itl \
    --to=marmarek@invisiblethingslab.com \
    --cc=jandryuk@gmail.com \
    --cc=jbeulich@suse.com \
    --cc=jgross@suse.com \
    --cc=roger.pau@citrix.com \
    --cc=simonpatp@gmail.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.