From: jays.lee@samsung•com (Jungseok Lee)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v4 2/7] arm64: Decouple page size from level of translation tables
Date: Wed, 30 Apr 2014 11:44:13 +0900 [thread overview]
Message-ID: <007d01cf641e$122f9b20$368ed160$@samsung.com> (raw)
In-Reply-To: <20140429144052.GJ17007@arm.com>
On Tuesday, April 29, 2014 11:41 PM, Catalin Marinas wrote:
> Jungseok,
Hi, Catalin
> On Tue, Apr 29, 2014 at 05:59:20AM +0100, Jungseok Lee wrote:
> > +choice
> > + prompt "Level of translation tables"
> > + default ARM64_3_LEVELS if ARM64_4K_PAGES
> > + default ARM64_2_LEVELS if ARM64_64K_PAGES
> > + help
> > + Allows level of translation tables.
> > +
> > +config ARM64_2_LEVELS
> > + bool "2 level"
> > + depends on ARM64_64K_PAGES
> > + help
> > + This feature enables 2 levels of translation tables.
> > +
> > +config ARM64_3_LEVELS
> > + bool "3 level"
> > + depends on ARM64_4K_PAGES
> > + help
> > + This feature enables 3 levels of translation tables.
> > +
> > +endchoice
>
> As I mentioned previously
> (http://www.spinics.net/linux/lists/arm-kernel/msg319552.html), just expose options for the VA space
> bits rather than the number of levels.
> You can still keep the number of levels config options but not visible in menuconfig (though I think
> you could also hide them in some header and avoid config altogether). The VA bits config options can
> be:
>
> VA_BITS_39 if 4K (3 levels)
> VA_BITS_42 if 64K (2 levels)
> VA_BITS_47 if 16K (3 levels)
> VA_BITS_48 if 4K || 16K || 64K (4/4/3 levels depending on page size)
>
> That's more meaningful to people configuring the kernel.
Okay, I will revise VA_BITS config as hiding the number of levels.
Best Regards
Jungseok Lee
prev parent reply other threads:[~2014-04-30 2:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 4:59 [PATCH v4 2/7] arm64: Decouple page size from level of translation tables Jungseok Lee
2014-04-29 14:40 ` Catalin Marinas
2014-04-30 2:44 ` Jungseok Lee [this message]
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='007d01cf641e$122f9b20$368ed160$@samsung.com' \
--to=jays.lee@samsung$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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