From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Gary Hade <garyhade@us.ibm.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
Thomas Renninger <trenn@novell.com>
Subject: Re: [PATCH] x86/PCI: Ignore CPU non-addressable _CRS reserved memory resources
Date: Mon, 5 Dec 2011 11:06:09 -0800 [thread overview]
Message-ID: <20111205110609.7f4fa6e0@jbarnes-desktop> (raw)
In-Reply-To: <20111114234216.GA16000@us.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]
On Mon, 14 Nov 2011 15:42:16 -0800
Gary Hade <garyhade@us.ibm.com> wrote:
>
> From: Gary Hade <garyhade@us.ibm.com>
>
> This assures that a _CRS reserved host bridge window or
> window region is not used if it is not addressable by
> the CPU. The new code either trims the window to exclude
> the non-addressable portion or totally ignores the window
> if the entire window is non-addressable.
>
> The current code has been shown to be problematic with
> 32-bit non-PAE kernels on systems where _CRS reserves
> resources above 4GB.
>
> Signed-off-by: Gary Hade <garyhade@us.ibm.com>
> Reviewed-by: Bjorn Helgaas <bhelgaas@google.com>
> Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
> Cc: Bjorn Helgaas <bhelgaas@google.com>
> Cc: Thomas Renninger <trenn@novell.com>
> Cc: linux-kernel@vger.kernel.org
> Cc: stable@kernel.org
> ---
Applied to linux-next (don't want to send something this fundamental to
Linus at this late stage). It can land in stable if it turns out ok in
-rc1.
Thanks,
--
Jesse Barnes, Intel Open Source Technology Center
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2011-12-05 19:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 23:42 [PATCH] x86/PCI: Ignore CPU non-addressable _CRS reserved memory resources Gary Hade
2011-12-05 19:06 ` 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=20111205110609.7f4fa6e0@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=bhelgaas@google.com \
--cc=garyhade@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=stable@kernel.org \
--cc=trenn@novell.com \
/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).