From: "H. Peter Anvin" <hpa@zytor.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: mingo@kernel.org, intel-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org, mingo@elte.hu, tglx@linutronix.de,
torvalds@linux-foundation.org
Subject: Re: Ugly patches for stolen reservation
Date: Thu, 25 Jul 2013 20:31:27 -0700 [thread overview]
Message-ID: <51F1ED8F.40703@zytor.com> (raw)
In-Reply-To: <rddfy5e894xuv6d47gu7hbuh.1374804892449@email.android.com>
On 07/25/2013 07:14 PM, Jesse Barnes wrote:
> To clarify: it'll either be marked reserved or not listed at all in e820, which is why I did this early, before any other e820 stuff like the "RAM buffer" are allocated, and before we could use the iomem resource (or maybe we could even early per Linus? I'll check).
>
> Jesse
If it is marked reserved or not listed at all it is much less of an
issue. Reserved is in fact the correct thing; not listed at all really
isn't very problematic in most cases.
-hpa
next parent reply other threads:[~2013-07-26 3:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <rddfy5e894xuv6d47gu7hbuh.1374804892449@email.android.com>
2013-07-26 3:31 ` H. Peter Anvin [this message]
2013-07-26 15:33 ` Ugly patches for stolen reservation Jesse Barnes
2013-07-26 20:24 ` Ingo Molnar
2013-07-26 20:28 ` H. Peter Anvin
2013-07-26 20:45 ` [Intel-gfx] " Daniel Vetter
2013-07-25 16:37 Jesse Barnes
2013-07-25 20:05 ` Ingo Molnar
2013-07-25 20:16 ` Jesse Barnes
2013-07-25 22:42 ` H. Peter Anvin
2013-07-25 23:17 ` Jesse Barnes
2013-07-26 0:49 ` H. Peter Anvin
2013-07-26 0:31 ` Linus Torvalds
2013-07-26 0:48 ` H. Peter Anvin
2013-07-26 15:51 ` Jesse Barnes
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=51F1ED8F.40703@zytor.com \
--to=hpa@zytor.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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