public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: linux-kernel@vger.kernel.org, mingo@redhat.com, hpa@zytor.com,
	yinghai@kernel.org, tglx@linutronix.de, mikpe@it.uu.se,
	alex.shi@intel.com,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/urgent] x86: add boundary check for 32bit res before expand e820 resource to alignment
Date: Fri, 3 Jul 2009 08:56:32 +0200	[thread overview]
Message-ID: <20090703065632.GB32687@elte.hu> (raw)
In-Reply-To: <tip-4b05c392955458757790414bd7ba4280e1a515b0@git.kernel.org>


* tip-bot for Yinghai Lu <yinghai@kernel.org> wrote:

> Commit-ID:  4b05c392955458757790414bd7ba4280e1a515b0
> Gitweb:     http://git.kernel.org/tip/4b05c392955458757790414bd7ba4280e1a515b0
> Author:     Yinghai Lu <yinghai@kernel.org>
> AuthorDate: Thu, 2 Jul 2009 11:10:56 -0700
> Committer:  H. Peter Anvin <hpa@zytor.com>
> CommitDate: Thu, 2 Jul 2009 11:53:15 -0700
> 
> x86: add boundary check for 32bit res before expand e820 resource to alignment
> 
> Avoid incorrect address arithmetic, ascerbated by previous improper
> definition of the round_up() macro.
> 
> fix hang with HIGHMEM_64G and 32bit resource.
> according to hpa and Linus, use (resource_size_t)-1 to fend off big ranges.
> analyized by hpa
> 
> Alex found:
> for i386 machine the specjbb2005 still can not run with hugepage
> 
> -v2: it also fix hugepage problem
> 
> Reported-and-tested-by: Mikael Pettersson <mikpe@it.uu.se>
> Reported-and-Tested-by: Alex Shi <alex.shi@intel.com>
> Signed-off-by: Yinghai Lu <yinghai@kernel.org>
> Signed-off-by: H. Peter Anvin <hpa@zytor.com>

Peter, Yinghi - i zapped this and the other e820 patch from 
x86/urgent as Linus already applied slightly different versions 
upstream:

7c5371c: x86: add boundary check for 32bit res before expand e820 resource to alignment
4364467: x86: fix power-of-2 round_up/round_down macros

Mind checking what the differences are and queue up any deltas that 
might still be needed?

Thanks,

	Ingo

       reply	other threads:[~2009-07-03  6:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tip-4b05c392955458757790414bd7ba4280e1a515b0@git.kernel.org>
2009-07-03  6:56 ` Ingo Molnar [this message]
2009-07-03  7:01   ` [tip:x86/urgent] x86: add boundary check for 32bit res before expand e820 resource to alignment Yinghai Lu

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=20090703065632.GB32687@elte.hu \
    --to=mingo@elte.hu \
    --cc=alex.shi@intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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