From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/Sandy Bridge: reserve pages when integrated graphics is present
Date: Thu, 15 Nov 2012 08:14:06 -0800 [thread overview]
Message-ID: <20121115081406.1b19940b@jbarnes-desktop> (raw)
In-Reply-To: <20121115124711.GA31504@khazad-dum.debian.net>
On Thu, 15 Nov 2012 10:47:11 -0200
Henrique de Moraes Holschuh <hmh@hmh.eng.br> wrote:
> On Wed, 14 Nov 2012, Jesse Barnes wrote:
> > + unsigned long bad_ranges[] = {
> > + 0x20050000,
> > + 0x20110000,
> > + 0x20130000,
> > + 0x20138000,
> > + 0x40004000,
>
> Yikes. Can this be fixed through a microcode update? The kernel would
> still need the workaround anyway, but at least you would be able to be quite
> heavy-handed on it, and users could be warned of a better fix...
Note the array should be called "bad pages" since it's just each page
at that offset that we can't use. (In case you were worried we'd need
to exclude everything between each pair of addresses or something.)
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2012-11-15 16:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 20:43 [PATCH] x86/Sandy Bridge: reserve pages when integrated graphics is present Jesse Barnes
2012-11-14 21:19 ` Alan Cox
2012-11-14 21:55 ` Jesse Barnes
2012-11-14 23:24 ` Alan Cox
2012-11-14 23:11 ` [Intel-gfx] " Jesse Barnes
2012-11-15 12:47 ` Henrique de Moraes Holschuh
2012-11-15 16:13 ` Jesse Barnes
2012-11-15 16:14 ` Jesse Barnes [this message]
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=20121115081406.1b19940b@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=hmh@hmh.eng.br \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.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.