From: "H. Peter Anvin" <hpa@zytor.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
mingo@elte.hu, torvalds@linux-foundation.org, tglx@linutronix.de
Subject: Re: Ugly patches for stolen reservation
Date: Fri, 26 Jul 2013 13:28:13 -0700 [thread overview]
Message-ID: <51F2DBDD.8020709@zytor.com> (raw)
In-Reply-To: <20130726202418.GD21415@gmail.com>
On 07/26/2013 01:24 PM, Ingo Molnar wrote:
>
> Am I being too pedantic in expecting that we still mark it
> e820-reserved?
>
> This area really isnt an ordinary PCI resource such as a
> BAR or an MMIO region. It's truly system RAM (which cannot
> be moved/reallocated), used by graphics hardware, and the
> firmware should have marked it reserved.
>
> (The end result should be the same in any case, so this is
> a detail.)
>
I, too, would prefer to see it marked as reserved.
-hpa
WARNING: multiple messages have this Message-ID (diff)
From: "H. Peter Anvin" <hpa@zytor.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Jesse Barnes <jbarnes@virtuousgeek.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: Fri, 26 Jul 2013 13:28:13 -0700 [thread overview]
Message-ID: <51F2DBDD.8020709@zytor.com> (raw)
In-Reply-To: <20130726202418.GD21415@gmail.com>
On 07/26/2013 01:24 PM, Ingo Molnar wrote:
>
> Am I being too pedantic in expecting that we still mark it
> e820-reserved?
>
> This area really isnt an ordinary PCI resource such as a
> BAR or an MMIO region. It's truly system RAM (which cannot
> be moved/reallocated), used by graphics hardware, and the
> firmware should have marked it reserved.
>
> (The end result should be the same in any case, so this is
> a detail.)
>
I, too, would prefer to see it marked as reserved.
-hpa
next prev parent reply other threads:[~2013-07-26 20:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 2:14 Ugly patches for stolen reservation Jesse Barnes
2013-07-26 3:31 ` H. Peter Anvin
2013-07-26 15:33 ` Jesse Barnes
2013-07-26 20:24 ` Ingo Molnar
2013-07-26 20:28 ` H. Peter Anvin [this message]
2013-07-26 20:28 ` H. Peter Anvin
2013-07-26 20:45 ` [Intel-gfx] " Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2013-07-25 16:37 Jesse Barnes
2013-07-25 20:05 ` Ingo Molnar
2013-07-25 20:16 ` Jesse Barnes
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:31 ` Linus Torvalds
2013-07-26 0:48 ` H. Peter Anvin
2013-07-26 15:51 ` Jesse Barnes
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=51F2DBDD.8020709@zytor.com \
--to=hpa@zytor.com \
--cc=intel-gfx@lists.freedesktop.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 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.