From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: RFC: New multiboot2 memory map entry type
Date: Fri, 25 Nov 2011 14:31:40 +0100 [thread overview]
Message-ID: <4ECF98BC.4050106@gmail.com> (raw)
In-Reply-To: <alpine.GSO.2.00.1111082122560.9801@oretfbsg>
On 09.11.2011 06:25, Seth Goldberg wrote:
> Hi,
>
> The multiboot2 spec currently says the following regarding memory map
> entries (tag type 6 in the multiboot2 info tag stack):
>
> +-------------------+
> u64 | base_addr |
> u64 | length |
> u32 | type |
> u32 | reserved |
> +-------------------+
>
> `size' contains the size of current entry including this field
> itself. It may be bigger than 24 bytes in future versions but is
> guaranteed to be `base_addr' is the starting physical address. `length'
> is the size of the memory region in bytes. `type' is the variety of
> address range represented, where a value of 1 indicates available RAM,
> value of 3 indicates usable memory holding ACPI information, value of 4
> indicates reserved memory which needs to be preserved on hibernation,
> value of 5 indicates a memory which is occupied by defective RAM
> modules and all other values currently indicated a reserved area.
> `reserved' is set to `0' by bootloader and must be ignored by the OS
> image.
>
>
> The proposal is to add an additional type (value = 6) that denotes
> runtime memory that some firmware marks as required to be mapped to
> take advantage of services after the end of boot (UEFI is the
> canonical example). Without this information, it's impossible for a
> multiboot2-compliant OS to set up proper mappings for this memory.
Fine with it. Can you supply the patch for texinfo and GRUB?
>
> --S
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
next prev parent reply other threads:[~2011-11-25 13:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 5:25 RFC: New multiboot2 memory map entry type Seth Goldberg
2011-11-25 13:31 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2011-12-24 4:31 ` Seth Goldberg
2011-12-24 6:37 ` Brendan Trotter
2011-12-24 7:45 ` Seth Goldberg
2012-01-03 19:29 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-01-03 20:26 ` Seth Goldberg
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=4ECF98BC.4050106@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).