mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Yongtaek Lee <ytk.lee@samsung.com>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Nicolas Pitre <nicolas.pitre@linaro.org>
Subject: Re: Re: Re: [PATCH] ARM: fix bug which VMALLOC_START is lowwer than 0xf0000000
Date: Thu, 3 Sep 2015 10:10:44 +0100	[thread overview]
Message-ID: <20150903091044.GW21084@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1441269809-11688-1-git-send-email-ytk.lee@samsung.com>

On Thu, Sep 03, 2015 at 05:43:29PM +0900, Yongtaek Lee wrote:
> > So, if we go and apply your logic to a 1GB system we should resize the
> > vmalloc area to 0 bytes in order to avoid RAM truncation without
> > CONFIG_HIGHMEM?
> 
> As you already know, CONFIG_HIGHMEM option is necessary if RAM is
> more than 1GB. So no need to resize vmalloc area to 0. 

Wrong, there is no such "rule".

If we apply that rule, then if you have 1GB of RAM, it will fill from
0xc0000000 to 0xffffffff inclusive.  There will be _zero_ bytes of
vmalloc space.  There will be _zero_ bytes of IO mappings.  There won't
even be a vectors page, so the kernel _will_ crash on the first exception.
The "rule" you think exists doesn't because it is wrong.

-- 
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2015-09-03  9:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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  8:00 ` [PATCH] ARM: fix bug which VMALLOC_START is lowwer than 0xf0000000 Russell King - ARM Linux
2015-09-03  8:28   ` Yongtaek Lee
2015-09-03  8:34     ` Lucas Stach
2015-09-03  8:43       ` Yongtaek Lee
2015-09-03  9:10         ` Russell King - ARM Linux [this message]
2015-09-03 10:30           ` [PATCH] ARM: fix bug which lowmem size is limited to 760MB Yongtaek Lee
2015-09-04  1:24             ` Nicolas Pitre
2015-09-07 11:41               ` Arnd Bergmann
2015-09-07 15:34                 ` Nicolas Pitre
2015-09-07 15:45                   ` Arnd Bergmann
2015-09-07 15:49                     ` Nicolas Pitre
2015-09-07 19:40                 ` Nicolas Pitre
2015-09-08  0:10                   ` Russell King - ARM Linux
2015-09-08  2:01                     ` Nicolas Pitre
2015-09-08  8:03                       ` Russell King - ARM Linux
2015-09-08 14:58                         ` Nicolas Pitre
2015-09-03  9:07       ` Re: [PATCH] ARM: fix bug which VMALLOC_START is lowwer than 0xf0000000 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=20150903091044.GW21084@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.pitre@linaro.org \
    --cc=ytk.lee@samsung.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

all inboxes | Powered by JetHome®