public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Linux Arch list <linux-arch@vger.kernel.org>
Subject: Re: [matthew@wil.cx: Re: Which architectures need 64-bit resources?]
Date: Tue, 07 Nov 2006 10:17:43 +1100	[thread overview]
Message-ID: <1162855063.28571.365.camel@localhost.localdomain> (raw)
In-Reply-To: <20061106222935.GQ27140@parisc-linux.org>


> Here's a proposed patch (which needs buy-in from the ARM, MIPS and
> PowerPC guys, plus anyone who knows about x86-32 machines with 64-bit
> IO).  Grepping the arch/*/configs/* doesn't show anyone else using it by
> default.

For the ppc bits:

Acked-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>

> I got the info for ARM from Vince Sanders, and made my best guess for
> MIPS & PPC.  This patch is entirely untested.
> 
> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
> index adb05de..d73cf59 100644
> --- a/arch/arm/Kconfig
> +++ b/arch/arm/Kconfig
> @@ -241,6 +241,7 @@ config ARCH_IXP23XX
>   	bool "IXP23XX-based"
>  	depends on MMU
>   	select PCI
> +	select RESOURCES_64BIT
>  	help
>  	  Support for Intel's IXP23xx (XScale) family of processors.
>  
> diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
> index 8a49884..f0205e0 100644
> --- a/arch/mips/Kconfig
> +++ b/arch/mips/Kconfig
> @@ -1556,6 +1556,7 @@ config SB1_PASS_2_1_WORKAROUNDS
>  config 64BIT_PHYS_ADDR
>  	bool "Support for 64-bit physical address space"
>  	depends on (CPU_R4X00 || CPU_R5000 || CPU_RM7000 || CPU_RM9000 || CPU_R10000 || CPU_SB1 || CPU_MIPS32 || CPU_MIPS64) && 32BIT
> +	select RESOURCES_64BIT
>  
>  config CPU_HAS_LLSC
>  	bool
> diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
> index 8b69104..29ab1e0 100644
> --- a/arch/powerpc/Kconfig
> +++ b/arch/powerpc/Kconfig
> @@ -227,10 +227,11 @@ config PTE_64BIT
>  config PHYS_64BIT
>  	bool 'Large physical address support' if E500
>  	depends on 44x || E500
> +	select RESOURCES_64BIT
>  	default y if 44x
>  	---help---
>  	  This option enables kernel support for larger than 32-bit physical
> -	  addresses.  This features is not be available on all e500 cores.
> +	  addresses.  This features is not available on all e500 cores.
>  
>  	  If in doubt, say N here.
>  
> diff --git a/lib/Kconfig b/lib/Kconfig
> index 734ce95..613942d 100644
> --- a/lib/Kconfig
> +++ b/lib/Kconfig
> @@ -92,9 +92,14 @@ config TEXTSEARCH_FSM
>  	tristate
>  
>  #
> -# plist support is select#ed if needed
> +# plist support is selected if needed
>  #
>  config PLIST
>  	boolean
>  
> +# 64-bit resources are selected by individual architectures
> +config RESOURCES_64BIT
> +	bool
> +	default 64BIT
> +
>  endmenu
> diff --git a/mm/Kconfig b/mm/Kconfig
> index db7c55d..089513f 100644
> --- a/mm/Kconfig
> +++ b/mm/Kconfig
> @@ -151,9 +151,3 @@ config MIGRATION
>  	  while the virtual addresses are not changed. This is useful for
>  	  example on NUMA systems to put pages nearer to the processors accessing
>  	  the page.
> -
> -config RESOURCES_64BIT
> -	bool "64 bit Memory and IO resources (EXPERIMENTAL)" if (!64BIT && EXPERIMENTAL)
> -	default 64BIT
> -	help
> -	  This option allows memory and IO resources to be 64 bit.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-arch" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> ----- End forwarded message -----


           reply	other threads:[~2006-11-06 23:17 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20061106222935.GQ27140@parisc-linux.org>]

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=1162855063.28571.365.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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