All of lore.kernel.org
 help / color / mirror / Atom feed
From: <dinhngoc.tu@irit.fr>
To: "'Jan Beulich'" <jbeulich@suse.com>
Cc: <xen-devel@lists.xenproject.org>
Subject: RE: [PATCH v2] x86: Use low memory size directly from Multiboot
Date: Wed, 9 Feb 2022 16:36:47 +0100	[thread overview]
Message-ID: <000b01d81dca$d932e420$8b98ac60$@irit.fr> (raw)
In-Reply-To: <2bdd699a-9644-ee6c-c75d-c5577c836f62@suse.com>

> -----Original Message-----
> From: Jan Beulich <jbeulich@suse.com>
> Sent: Wednesday, 9 February 2022 16:23
> To: dinhngoc.tu@irit.fr
> Cc: xen-devel@lists.xenproject.org
> Subject: Re: [PATCH v2] x86: Use low memory size directly from Multiboot
> 
> On 09.02.2022 16:20, dinhngoc.tu@irit.fr wrote:
> > This change should only affect the particular case of booting with
> Multiboot2 without EFI (e.g. legacy BIOS or Kexec). Other cases like
> Multiboot 0.x, EFI booting (with or without MB2), or bootloaders that
> generate the BASIC_MEMINFO tag correctly shouldn't be affected.
> 
> How that? You're taking out the reading of the BDA value altogether, aren't
> you? This is certainly a change affecting other environments as well.
> 
> Jan

I missed that the BDA was used when booting on Multiboot 0.x as well. I can add a fallback to use the BDA when the bootloader doesn't provide low memory size in the MBI.



  reply	other threads:[~2022-02-09 15:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-09 11:00 [PATCH] x86: Use low memory size directly from Multiboot dinhngoc.tu
2022-02-09 11:25 ` Jan Beulich
2022-02-09 11:46   ` dinhngoc.tu
2022-02-09 13:12   ` [PATCH v2] " Tu Dinh Ngoc
2022-02-09 14:25     ` Jan Beulich
2022-02-09 15:20       ` dinhngoc.tu
2022-02-09 15:22         ` Jan Beulich
2022-02-09 15:36           ` dinhngoc.tu [this message]
2022-02-09 15:56     ` Roger Pau Monné

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='000b01d81dca$d932e420$8b98ac60$@irit.fr' \
    --to=dinhngoc.tu@irit.fr \
    --cc=jbeulich@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.