From: Tabi Timur-B04825 <B04825@freescale.com>
To: Li Yang-R58472 <r58472@freescale.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
Huang Changming-R66093 <r66093@freescale.com>,
Wood Scott-B07421 <B07421@freescale.com>
Subject: Re: [PATCH] powerpc/85xx: allow CONFIG_PHYS_64BIT to be selectable
Date: Fri, 24 Feb 2012 04:11:13 +0000 [thread overview]
Message-ID: <4F470DDD.2060803@freescale.com> (raw)
In-Reply-To: <94F013E7935FF44C83EBE7784D62AD3F0578D5BD@039-SN2MPN1-023.039d.mgd.msft.net>
Li Yang-R58472 wrote:
> It's a good point. Why can't we decide to use 32-bit/36-bit TLB at runti=
me even for e500v2?
That's not what PHYS_64BIT does. PHYS_64BIT determines whether=20
phys_addr_t is a u64 or a u32. This is something that must be determined=20
at compilation time.
>> Please remember that the Kconfig for the P1022DS already forced
>> PHYS_64BIT for all mpc85xx platforms. All we're doing is making it
>> possible to deselect PHYS_64BIT.
>
> I think it's a side-effect introduced by P1022DS support and need to be f=
ixed.
Exactly. That's what these patches do. And these patches have been=20
applied to the SDK. I'm just waiting for Kumar to apply them to his=20
repository.
> There was no mentioning of enforcing 36-bit for all mpc85xx platforms.
It's not enforcing, it's just the default. If you build with=20
mpc85xx_smp_defconfig, then you'll get a 36-bit kernel. But now you can=20
also use menuconfig to turn off PHYS_64BIT. Before these fixes, that was=20
not possible.
--=20
Timur Tabi
Linux kernel developer at Freescale=
next prev parent reply other threads:[~2012-02-24 4:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 19:53 [PATCH] powerpc/85xx: allow CONFIG_PHYS_64BIT to be selectable Timur Tabi
2012-02-23 6:25 ` Huang Changming-R66093
2012-02-23 12:24 ` Tabi Timur-B04825
2012-02-24 1:54 ` Huang Changming-R66093
2012-02-24 2:29 ` Li Yang-R58472
2012-02-24 2:45 ` Tabi Timur-B04825
2012-02-24 2:59 ` Li Yang-R58472
2012-02-24 3:01 ` Huang Changming-R66093
2012-02-24 3:04 ` Tabi Timur-B04825
2012-02-24 3:24 ` Huang Changming-R66093
2012-02-24 3:36 ` Tabi Timur-B04825
2012-02-24 3:40 ` Li Yang-R58472
2012-02-24 3:50 ` Tabi Timur-B04825
2012-02-24 4:02 ` Li Yang-R58472
2012-02-24 4:11 ` Tabi Timur-B04825 [this message]
2012-03-16 20:01 ` 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=4F470DDD.2060803@freescale.com \
--to=b04825@freescale.com \
--cc=B07421@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=r58472@freescale.com \
--cc=r66093@freescale.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 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.