From: Dave Hansen <dave.hansen@intel.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Kevin Hilman <khilman@linaro.org>,
Olof Johansson <olof@lixom.net>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] memblock: Add limit checking to memblock_virt_alloc
Date: Tue, 28 Jan 2014 14:55:51 -0800 [thread overview]
Message-ID: <52E83577.6040504@intel.com> (raw)
In-Reply-To: <CAE9FiQVGuN0f5xo9fbfsurmO3E=45A3m0oS75HYPV7BSEwrvsg@mail.gmail.com>
On 01/28/2014 02:47 PM, Yinghai Lu wrote:
> On Tue, Jan 28, 2014 at 2:08 PM, Dave Hansen <dave.hansen@intel.com> wrote:
>> On 01/28/2014 02:04 PM, Yinghai Lu wrote:
>>> In original bootmem wrapper for memblock, we have limit checking.
>>>
>>> Add it to memblock_virt_alloc, to address arm and x86 booting crash.
>>>
>> Do you have a git tree or cumulative set of patches that you'd like us
>> to all test? I'm happy to boot it on my system, I just want to make
>> sure I've got the same set that you're testing.
>
> This one should only affect on arm and x86 the 32 bit kernel with more
> then 4G RAM.
OK, let me rephrase.
Does anyone want me to test this on a 1TB 64-bit x86 system? If yes,
please tell me which patches you want me to test, and on top of which
kernel. I have three patches in this area, I think, but I don't want to
waste my time testing and reporting the wrong thing.
next prev parent reply other threads:[~2014-01-28 22:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 22:04 [PATCH] memblock: Add limit checking to memblock_virt_alloc Yinghai Lu
2014-01-28 22:08 ` Dave Hansen
2014-01-28 22:47 ` Yinghai Lu
2014-01-28 22:55 ` Dave Hansen [this message]
2014-01-29 1:50 ` Konrad Rzeszutek Wilk
2014-01-29 23:07 ` Tony Luck
2014-01-29 23:07 ` Tony Luck
2014-01-29 23:39 ` Yinghai Lu
2014-01-29 23:53 ` Yinghai Lu
2014-01-29 23:53 ` Yinghai Lu
2014-01-30 0:12 ` Tony Luck
2014-01-30 0:12 ` Tony Luck
2014-01-30 0:34 ` Andrew Morton
2014-01-30 0:46 ` Tony Luck
2014-01-30 0:46 ` Tony Luck
2014-01-30 0:34 ` Andrew Morton
2014-01-29 23:39 ` Yinghai Lu
2014-01-29 1:50 ` Konrad Rzeszutek Wilk
2014-01-28 22:08 ` Andrew Morton
2014-01-28 22:08 ` Olof Johansson
2014-01-29 1:25 ` Kevin Hilman
2014-01-30 4:46 ` Sachin Kamat
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=52E83577.6040504@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=khilman@linaro.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mingo@elte.hu \
--cc=olof@lixom.net \
--cc=santosh.shilimkar@ti.com \
--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 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.