于 2014/4/14 21:50, Nicolas Pitre 写道:
> On Mon, 14 Apr 2014, Liu hua wrote:
>
>> Yes, it seems that FIX_KMAP_BEGIN and FIX_KMAP_END are not as important for
>> ARM than that for other architectures (MIPS PowerPC x86), whose
>> FIX_KMAP_BEGIN
>> is not 0. I will reminder this in my patch. Anyone wh
On Mon, 14 Apr 2014, Liu hua wrote:
> Yes, it seems that FIX_KMAP_BEGIN and FIX_KMAP_END are not as important for
> ARM than that for other architectures (MIPS PowerPC x86), whose FIX_KMAP_BEGIN
> is not 0. I will reminder this in my patch. Anyone who need them can get
> imformantion there.
>
>
于 2014/4/14 1:34, Nicolas Pitre 写道:
> On Sun, 13 Apr 2014, Liu hua wrote:
>
>> Hi Nicolas.
>>
>> Sure, your suggestion made my patch looks better. How about that :
>>
>> Thanks,
>> Liu Hua
>
> There is something else that bothers me.
>
>> +unsigned long idx = __virt_to_fix(vaddr);
>> +id
On Sun, 13 Apr 2014, Liu hua wrote:
> Hi Nicolas.
>
> Sure, your suggestion made my patch looks better. How about that :
>
> Thanks,
> Liu Hua
There is something else that bothers me.
> -
>
> Changes from v2:
> moved new codes to highmem.
On 2014/4/12 11:26, Nicolas Pitre wrote:
> On Fri, 11 Apr 2014, Liu Hua wrote:
>
>> In 32-bit ARM systems, the fixmap mapping region can support
>> no more than 14 CPUs(total: 896k; one CPU: 64K). And we can
>> configure NR_CPUS up to 32. So there is a mismatch.
>>
>> This patch moves fixmapping r
On Fri, 11 Apr 2014, Liu Hua wrote:
> In 32-bit ARM systems, the fixmap mapping region can support
> no more than 14 CPUs(total: 896k; one CPU: 64K). And we can
> configure NR_CPUS up to 32. So there is a mismatch.
>
> This patch moves fixmapping region downwards to region
> 0xffc0-0xffe0
In 32-bit ARM systems, the fixmap mapping region can support
no more than 14 CPUs(total: 896k; one CPU: 64K). And we can
configure NR_CPUS up to 32. So there is a mismatch.
This patch moves fixmapping region downwards to region
0xffc0-0xffe0 . Then the fixmap mapping region can
support up
7 matches
Mail list logo
