linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shuah Khan <shuah.khan@hp.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Jacob Shin <jacob.shin@amd.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"x86@kernel.org" <x86@kernel.org>,
	Yinghai Lu <yinghai@kernel.org>,
	andreas.herrmann3@amd.com, borislav.petkov@amd.com,
	shuahkhan@gmail.com
Subject: Re: [PATCH 1/1] x86, e820: Remove direct mapping of reserved space for HT hole around 1TB
Date: Wed, 17 Oct 2012 09:30:52 -0600	[thread overview]
Message-ID: <1350487852.2741.13.camel@lorien2> (raw)
In-Reply-To: <507DAF3C.90903@zytor.com>

On Tue, 2012-10-16 at 12:02 -0700, H. Peter Anvin wrote:
> On 10/16/2012 11:26 AM, Jacob Shin wrote:
> > 
> > HPA, it would be great if we can first get this patch upstream, and also
> > into the stable trees .. and after that, we can work on getting Yinghai's
> > mm refactoring in ..
> > 
> 
> I'll be back from travels tomorrow, I'll look at it then.

For what its worth, I applied this patch to RHEL 6.3 based on 2.6.32.
kernel and my test system came with 1 terabyte memory.

https://lkml.org/lkml/2011/10/20/323

Thanks,
-- Shuah




  reply	other threads:[~2012-10-17 15:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6ec48b96-afab-4c8b-ab74-2c640c2a161b@blur>
     [not found] ` <8630fe28-0c1c-4f3a-90e1-df2d1b6615a6@blur>
2012-10-16 17:48   ` [PATCH 1/1] x86, e820: Remove direct mapping of reserved space for HT hole around 1TB Shuah Khan
2012-10-16 18:26     ` Jacob Shin
2012-10-16 19:02       ` H. Peter Anvin
2012-10-17 15:30         ` Shuah Khan [this message]
2012-10-17 18:25       ` H. Peter Anvin
2011-10-11 22:09 Jacob Shin
2011-10-11 23:44 ` H. Peter Anvin
2011-10-13  9:57   ` Andreas Herrmann
2011-10-13 15:52     ` H. Peter Anvin
2011-10-13 11:04 ` Andreas Herrmann
2011-10-14  5:45   ` Yinghai Lu
2012-10-16 16:47 ` Shuah Khan

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=1350487852.2741.13.camel@lorien2 \
    --to=shuah.khan@hp.com \
    --cc=andreas.herrmann3@amd.com \
    --cc=borislav.petkov@amd.com \
    --cc=hpa@zytor.com \
    --cc=jacob.shin@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=shuahkhan@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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 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).