All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maarten Lankhorst <m.b.lankhorst@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
	Yinghai Lu <yinghai@kernel.org>, Jim Bos <jim876@xs4all.nl>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] x86, efi: Do not reserve boot services regions within reserved areas
Date: Tue, 14 Jun 2011 19:26:01 +0200	[thread overview]
Message-ID: <4DF799A9.8080109@gmail.com> (raw)
In-Reply-To: <1308071118.21026.16.camel@Joe-Laptop>

Op 14-06-11 19:05, Joe Perches schreef:
> On Tue, 2011-06-14 at 18:19 +0200, Maarten Lankhorst wrote:
>> Commit 916f676f8dc started reserving boot service code since some systems
>> require you to keep that code around until SetVirtualAddressMap is called.
> []
>> Signed-off-by: Maarten Lankhorst <m.b.lankhorst@gmail.com>
> Hello Maarten, just trivia.
>
>> diff --git a/arch/x86/platform/efi/efi.c b/arch/x86/platform/efi/efi.c
> []
>> +			memblock_dbg(PFX "Could not reserve boot area "
>> +				"[0x%llx-0x%llx)\n", start, start+size);
> I believe this should be:
>
> 			memblock_dbg(PFX "Could not reserve boot area 0x%llx-0x%llx)\n",
> 				     start, start + size - 1);
Erm, no. [x...y) means the range of x to y without including y.

Other efi code followed that convention, and the e820 code does the same, silently.

[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
...
[    0.000000] EFI: mem00: type=3, attr=0xf, range=[0x0000000000000000-0x0000000000008000) (0MB)

~Maarten

  reply	other threads:[~2011-06-14 17:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-14 16:19 [PATCH v2] x86, efi: Do not reserve boot services regions within reserved areas Maarten Lankhorst
2011-06-14 17:05 ` Joe Perches
2011-06-14 17:26   ` Maarten Lankhorst [this message]
2011-06-14 17:40     ` Joe Perches
2011-06-14 18:10 ` Yinghai Lu
2011-06-14 18:32   ` Maarten Lankhorst

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=4DF799A9.8080109@gmail.com \
    --to=m.b.lankhorst@gmail.com \
    --cc=jim876@xs4all.nl \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=yinghai@kernel.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.