All of lore.kernel.org
 help / color / mirror / Atom feed
From: sdu.liu@huawei.com (Liu hua)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/2] ARM : change fixmap mapping region to support 32 CPUs
Date: Tue, 10 Jun 2014 14:52:32 +0800	[thread overview]
Message-ID: <5396AB30.10607@huawei.com> (raw)
In-Reply-To: <alpine.LFD.2.11.1405301441210.17310@knanqh.ubzr>

On 2014/5/31 3:25, Nicolas Pitre Wrote:
> On Fri, 30 May 2014, Rob Herring wrote:
> 
>> There's work in flight to support early_ioremap, early console, and RO
>> text patching which all use the fixmap region.
>>
>> There's a couple of options to solve this:
>>
>> - Only support up to 16 cpus. It could be anywhere between 17-31, but
>> that seems somewhat unlikely. Are we really ever going to see 32-bit
>> 32 core systems?
> 
> I wouldn't rule that out.  I've seen 16-core ARM chips in 2008 (although 
> they didn't go into production).  Silly limitations like that always 
> come back to bite you.  And we have better alternatives.New

 Now our team is woring on arma15 with 16 CPUs.
> 
>> - Reduce KM_TYPE_NR from 16 to 15. Based on the comment for it, we
>> probably don't want to do that. Is increasing it to the default of 20
>> worthwhile? Some of the options here would allow doing that.
>> - Add 0xffe00000-0xfff00000 to the fixmap region. This would make
>> fixmap span 2 PMDs with the top PMD having a mixture of uses like we
>> had before.
> 
> That would be my preferred approach.  Note here it could be 
> 0xffe00000-0xfffe0000 to include the whole of the previous fixmap area 
> curently unused.
> 
>> - push the PCI i/o space down to 0xfec00000 and make fixmap 4MB. This
>> is a cleaner solution as the 2 PMDs are only used for fixmap. This may
>> require some static mapping adjustments on some platforms.
> 
> No need.  With the latest changes, the fixmap area is between 0xffc00000 
> and 0xffe00000 (there is apparently a mistake in 
> Documentation/arm/memory.txt).  So currently 0xff000000-0xffc00000 is 
> free, which makes the fixmap area far away from the PCI i/o area with 
> plenti of space in between.
> 
>> - Same as previous option, but convert the PCI i/o space to fixmap
>> entries. We don't really need all 2MB for PCI.
> 
> See above.
> 
>> Also, there is an error in the documentation below:
>>
>>>
>>> Signed-off-by: Liu Hua <sdu.liu@huawei.com>
>>> ---
>>>  Documentation/arm/memory.txt   |  2 +-
> 
> Yep, good that you spotted it as well.  I failed to catch it during my 
> review so I'll send a patch.
> 

Very sorry for the mistake and ignoreing this mail. Maybe I should imporve
my email client!

Thanks again for Nicolas.

Thanks,
Liu Hua
> 
> Nicolas
> 
> .
> 

WARNING: multiple messages have this Message-ID (diff)
From: Liu hua <sdu.liu@huawei.com>
To: Nicolas Pitre <nicolas.pitre@linaro.org>,
	Rob Herring <robherring2@gmail.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
	<wangnan0@huawei.com>, Laura Abbott <lauraa@codeaurora.org>,
	<peifeiyue@huawei.com>, Will Deacon <will.deacon@arm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	<vitalya@ti.com>, Santosh Shilimkar <santosh.shilimkar@ti.com>,
	<liusdu@126.co>, <cyril@ti.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	Rabin Vincent <rabin@rab.in>
Subject: Re: [PATCH v3 2/2] ARM : change fixmap mapping region to support 32 CPUs
Date: Tue, 10 Jun 2014 14:52:32 +0800	[thread overview]
Message-ID: <5396AB30.10607@huawei.com> (raw)
In-Reply-To: <alpine.LFD.2.11.1405301441210.17310@knanqh.ubzr>

On 2014/5/31 3:25, Nicolas Pitre Wrote:
> On Fri, 30 May 2014, Rob Herring wrote:
> 
>> There's work in flight to support early_ioremap, early console, and RO
>> text patching which all use the fixmap region.
>>
>> There's a couple of options to solve this:
>>
>> - Only support up to 16 cpus. It could be anywhere between 17-31, but
>> that seems somewhat unlikely. Are we really ever going to see 32-bit
>> 32 core systems?
> 
> I wouldn't rule that out.  I've seen 16-core ARM chips in 2008 (although 
> they didn't go into production).  Silly limitations like that always 
> come back to bite you.  And we have better alternatives.New

 Now our team is woring on arma15 with 16 CPUs.
> 
>> - Reduce KM_TYPE_NR from 16 to 15. Based on the comment for it, we
>> probably don't want to do that. Is increasing it to the default of 20
>> worthwhile? Some of the options here would allow doing that.
>> - Add 0xffe00000-0xfff00000 to the fixmap region. This would make
>> fixmap span 2 PMDs with the top PMD having a mixture of uses like we
>> had before.
> 
> That would be my preferred approach.  Note here it could be 
> 0xffe00000-0xfffe0000 to include the whole of the previous fixmap area 
> curently unused.
> 
>> - push the PCI i/o space down to 0xfec00000 and make fixmap 4MB. This
>> is a cleaner solution as the 2 PMDs are only used for fixmap. This may
>> require some static mapping adjustments on some platforms.
> 
> No need.  With the latest changes, the fixmap area is between 0xffc00000 
> and 0xffe00000 (there is apparently a mistake in 
> Documentation/arm/memory.txt).  So currently 0xff000000-0xffc00000 is 
> free, which makes the fixmap area far away from the PCI i/o area with 
> plenti of space in between.
> 
>> - Same as previous option, but convert the PCI i/o space to fixmap
>> entries. We don't really need all 2MB for PCI.
> 
> See above.
> 
>> Also, there is an error in the documentation below:
>>
>>>
>>> Signed-off-by: Liu Hua <sdu.liu@huawei.com>
>>> ---
>>>  Documentation/arm/memory.txt   |  2 +-
> 
> Yep, good that you spotted it as well.  I failed to catch it during my 
> review so I'll send a patch.
> 

Very sorry for the mistake and ignoreing this mail. Maybe I should imporve
my email client!

Thanks again for Nicolas.

Thanks,
Liu Hua
> 
> Nicolas
> 
> .
> 



  reply	other threads:[~2014-06-10  6:52 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-15 11:06 [PATCH v3 0/2] change ARM linux memory layout to support 32 CPUs Liu Hua
2014-04-15 11:06 ` Liu Hua
2014-04-15 11:06 ` [PATCH v3 1/2] ARM : fixmap : remove FIX_KMAP_BEGIN and FIX_KMAP_END Liu Hua
2014-04-15 11:06   ` Liu Hua
2014-04-15 11:06 ` [PATCH v3 2/2] ARM : change fixmap mapping region to support 32 CPUs Liu Hua
2014-04-15 11:06   ` Liu Hua
2014-04-15 15:06   ` Nicolas Pitre
2014-04-15 15:06     ` Nicolas Pitre
2014-05-30 15:33   ` Rob Herring
2014-05-30 15:33     ` Rob Herring
2014-05-30 18:02     ` Will Deacon
2014-05-30 18:02       ` Will Deacon
2014-05-30 19:25     ` Nicolas Pitre
2014-05-30 19:25       ` Nicolas Pitre
2014-06-10  6:52       ` Liu hua [this message]
2014-06-10  6:52         ` Liu hua
2014-08-06  2:51       ` Kees Cook
2014-08-06  2:51         ` Kees Cook
2014-08-06  3:11         ` Nicolas Pitre
2014-08-06  3:11           ` Nicolas Pitre
2014-08-06  3:40         ` Liu hua
2014-08-06  3:40           ` Liu hua
2014-08-06 16:37           ` Kees Cook
2014-08-06 16:37             ` Kees Cook
2014-08-06 17:21             ` Nicolas Pitre
2014-08-06 17:21               ` Nicolas Pitre
2014-08-06 17:28               ` Kees Cook
2014-08-06 17:28                 ` Kees Cook
2014-08-06 22:16                 ` Russell King - ARM Linux
2014-08-06 22:16                   ` Russell King - ARM Linux
2014-08-06 23:22                   ` Kees Cook
2014-08-06 23:22                     ` Kees Cook
2014-04-22 21:31 ` [PATCH v3 0/2] change ARM linux memory layout " Russell King - ARM Linux
2014-04-22 21:31   ` Russell King - ARM Linux
2014-04-22 23:50   ` Nicolas Pitre
2014-04-22 23:50     ` Nicolas Pitre
2014-05-04  2:34     ` Liu hua
2014-05-04  2:34       ` Liu hua

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=5396AB30.10607@huawei.com \
    --to=sdu.liu@huawei.com \
    --cc=linux-arm-kernel@lists.infradead.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 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.