From: Kumar Gala <galak@kernel.crashing.org>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Kyle McMartin <kyle@mcmartin.ca>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Only show RESOURCES_64BIT on relevant architectures
Date: Mon, 29 Oct 2007 22:03:16 -0500 [thread overview]
Message-ID: <AFC1DED8-E331-420C-940E-9CF849630F0B@kernel.crashing.org> (raw)
In-Reply-To: <20071030024801.GA19417@linux-mips.org>
On Oct 29, 2007, at 9:48 PM, Ralf Baechle wrote:
> On Sun, Oct 28, 2007 at 04:15:49PM -0400, Kyle McMartin wrote:
>
>> +++ b/mm/Kconfig
>> @@ -172,6 +172,7 @@ config MIGRATION
>>
>> config RESOURCES_64BIT
>> bool "64 bit Memory and IO resources (EXPERIMENTAL)" if (!64BIT
>> && EXPERIMENTAL)
>> + depends on (MIPS || PPC32 || X86_PAE) || 64BIT
>
> On MIPS it would be a per platform thing. I'd prefer if
> RESOURCES_64BIT
> was enabled through reverse dependencies and never visible as a user
> option.
The same is true on PPC32. Its a per platform thing. However, I'm
not sure if we could hide it from the user. There are cases on the
same HW platform that you want to run with just 32-bit phys (for
performance).
- k
next prev parent reply other threads:[~2007-10-30 3:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-28 20:15 Kyle McMartin
2007-10-29 1:09 ` David Miller
2007-10-29 15:11 ` Kyle McMartin
2007-10-29 8:10 ` Russell King
2007-10-29 15:21 ` Kyle McMartin
2007-10-29 15:50 ` Russell King
2007-10-30 2:48 ` Ralf Baechle
2007-10-30 3:03 ` Kumar Gala [this message]
2007-10-30 8:37 ` Matthew Wilcox
2007-10-30 11:42 ` Ralf Baechle
2007-10-30 12:13 ` Matthew Wilcox
2007-10-30 14:14 ` Ralf Baechle
2007-10-30 20:00 ` Russell King
2007-10-30 14:19 ` Kumar Gala
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=AFC1DED8-E331-420C-940E-9CF849630F0B@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=kyle@mcmartin.ca \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@linux-mips.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
all inboxes | Powered by JetHome®