All of lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: fix bug which lowmem size is limited to 760MB
Date: Mon, 07 Sep 2015 17:45:08 +0200	[thread overview]
Message-ID: <6035791.Tn8TYmTeXT@wuerfel> (raw)
In-Reply-To: <alpine.LFD.2.20.1509071128151.22877@knanqh.ubzr>

On Monday 07 September 2015 11:34:36 Nicolas Pitre wrote:
> 
> That shifts the risk to user space though.  But if there is a regression 
> there, it will manifest itself on all systems and not only with some 
> particular hardware.

I'd consider that a good thing, as it makes it easier to test when
you see the same behavior on systems with any memory size.

	Arnd

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Nicolas Pitre <nicolas.pitre@linaro.org>,
	Russell King <linux@arm.linux.org.uk>,
	Yongtaek Lee <ytk.lee@samsung.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: fix bug which lowmem size is limited to 760MB
Date: Mon, 07 Sep 2015 17:45:08 +0200	[thread overview]
Message-ID: <6035791.Tn8TYmTeXT@wuerfel> (raw)
In-Reply-To: <alpine.LFD.2.20.1509071128151.22877@knanqh.ubzr>

On Monday 07 September 2015 11:34:36 Nicolas Pitre wrote:
> 
> That shifts the risk to user space though.  But if there is a regression 
> there, it will manifest itself on all systems and not only with some 
> particular hardware.

I'd consider that a good thing, as it makes it easier to test when
you see the same behavior on systems with any memory size.

	Arnd

  reply	other threads:[~2015-09-07 15:45 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-03  2:24 [PATCH] ARM: fix bug which VMALLOC_START is lowwer than 0xf0000000 Yongtaek Lee
2015-09-03  2:24 ` Yongtaek Lee
2015-09-03  5:11 ` [PATCH] ARM: fix bug which lowmem size is limited to 760MB Yongtaek Lee
2015-09-03  5:11   ` Yongtaek Lee
2015-09-03  8:00 ` [PATCH] ARM: fix bug which VMALLOC_START is lowwer than 0xf0000000 Russell King - ARM Linux
2015-09-03  8:00   ` Russell King - ARM Linux
2015-09-03  8:28   ` Yongtaek Lee
2015-09-03  8:28     ` Yongtaek Lee
2015-09-03  8:34     ` Lucas Stach
2015-09-03  8:34       ` Lucas Stach
2015-09-03  8:43       ` Yongtaek Lee
2015-09-03  8:43         ` Re: " Yongtaek Lee
2015-09-03  9:10         ` Russell King - ARM Linux
2015-09-03  9:10           ` Re: " Russell King - ARM Linux
2015-09-03 10:30           ` [PATCH] ARM: fix bug which lowmem size is limited to 760MB Yongtaek Lee
2015-09-03 10:30             ` Yongtaek Lee
2015-09-04  1:24             ` Nicolas Pitre
2015-09-04  1:24               ` Nicolas Pitre
2015-09-07 11:41               ` Arnd Bergmann
2015-09-07 11:41                 ` Arnd Bergmann
2015-09-07 15:34                 ` Nicolas Pitre
2015-09-07 15:34                   ` Nicolas Pitre
2015-09-07 15:45                   ` Arnd Bergmann [this message]
2015-09-07 15:45                     ` Arnd Bergmann
2015-09-07 15:49                     ` Nicolas Pitre
2015-09-07 15:49                       ` Nicolas Pitre
2015-09-07 19:40                 ` Nicolas Pitre
2015-09-07 19:40                   ` Nicolas Pitre
2015-09-08  0:10                   ` Russell King - ARM Linux
2015-09-08  0:10                     ` Russell King - ARM Linux
2015-09-08  2:01                     ` Nicolas Pitre
2015-09-08  2:01                       ` Nicolas Pitre
2015-09-08  8:03                       ` Russell King - ARM Linux
2015-09-08  8:03                         ` Russell King - ARM Linux
2015-09-08 14:58                         ` Nicolas Pitre
2015-09-08 14:58                           ` Nicolas Pitre
2015-09-03  9:07       ` [PATCH] ARM: fix bug which VMALLOC_START is lowwer than 0xf0000000 Russell King - ARM Linux
2015-09-03  9:07         ` Russell King - ARM Linux

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=6035791.Tn8TYmTeXT@wuerfel \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.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.