fined reference to `nf_defrag_ipv6_enable'
"
So this patch change the Kconfig as ipv4 does.
Signed-off-by: Liu Hua
---
net/netfilter/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/netfilter/Kconfig b/net/netfilter/Kconfig
index f70e34a..34f54a8 100644
reference to `nf_defrag_ipv6_enable'
So this patch change the Kconfig as ipv4 does.
Signed-off-by: Liu Hua sdu@huawei.com
---
net/netfilter/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/netfilter/Kconfig b/net/netfilter/Kconfig
index f70e34a..34f54a8 100644
this problem.
link:lkml.org/lkml/2014/8/4/18
Signed-off-by: Liu Hua
---
kernel/irq/chip.c | 8
1 file changed, 8 insertions(+)
diff --git a/kernel/irq/chip.c b/kernel/irq/chip.c
index 6f1c7a5..3328a45 100644
--- a/kernel/irq/chip.c
+++ b/kernel/irq/chip.c
@@ -710,10 +710,18 @@ void
this problem.
link:lkml.org/lkml/2014/8/4/18
Signed-off-by: Liu Hua sdu@huawei.com
---
kernel/irq/chip.c | 8
1 file changed, 8 insertions(+)
diff --git a/kernel/irq/chip.c b/kernel/irq/chip.c
index 6f1c7a5..3328a45 100644
--- a/kernel/irq/chip.c
+++ b/kernel/irq/chip.c
@@ -710,10
Hi all,
For arm32 platform. I want to know whether or not a mechanism in kernel can
snapshot tasks and cpus
information as the follow. If not, such a mechanism can be accepted by kernel.
...
TASK: [pid 1], [tgid 1], [linuxrc] [state S] [policy 0] [cpu 3]
EIP address: [<401945a4>]
Hi all,
For arm32 platform. I want to know whether or not a mechanism in kernel can
snapshot tasks and cpus
information as the follow. If not, such a mechanism can be accepted by kernel.
...
/module list
task info
TASK: [pid 1], [tgid 1], [linuxrc] [state S] [policy 0] [cpu 3]
EIP
dma_mapping_error takes two parameters, but some of examples
in Documentation/DMA-API-HOWTO.txt just takes one. So correct
it.
Signed-off-by: Liu Hua
---
Documentation/DMA-API-HOWTO.txt | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/DMA-API-HOWTO.txt b
dma_mapping_error takes two parameters, but some of examples
in Documentation/DMA-API-HOWTO.txt just takes one. So correct
it.
Signed-off-by: Liu Hua sdu@huawei.com
---
Documentation/DMA-API-HOWTO.txt | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/DMA
On 2014/8/6 17:46, Marc Zyngier wrote:
> Hi Liu,
>
> On 06/08/14 09:43, Liu hua wrote:
>> 于 2014/8/4 17:43, Marc Zyngier 写道:
>>> Hi Liu,
>>>
>>> On 04/08/14 05:17, Liu Hua wrote:
>>>> When using kdump on ARM platform, if kernel panics in inte
于 2014/8/4 17:43, Marc Zyngier 写道:
> Hi Liu,
>
> On 04/08/14 05:17, Liu Hua wrote:
>> When using kdump on ARM platform, if kernel panics in interrupt handler
>> (maybe PPI), the capture kernel can not recive certain interrupt, and
>> fails to boot.
>>
>> O
于 2014/8/4 17:43, Marc Zyngier 写道:
Hi Liu,
On 04/08/14 05:17, Liu Hua wrote:
When using kdump on ARM platform, if kernel panics in interrupt handler
(maybe PPI), the capture kernel can not recive certain interrupt, and
fails to boot.
On this situation, We have read register GICC_IAR
On 2014/8/6 17:46, Marc Zyngier wrote:
Hi Liu,
On 06/08/14 09:43, Liu hua wrote:
于 2014/8/4 17:43, Marc Zyngier 写道:
Hi Liu,
On 04/08/14 05:17, Liu Hua wrote:
When using kdump on ARM platform, if kernel panics in interrupt handler
(maybe PPI), the capture kernel can not recive certain
nflict with others, or it will at the future?
As Rob said "There's work in flight to support early_ioremap, early console,
and RO
text patching which all use the fixmap region." So if this patch will block
kernel's
new feature, Should we makes new patch to changes it, not revert it. Beca
in flight to support early_ioremap, early console,
and RO
text patching which all use the fixmap region. So if this patch will block
kernel's
new feature, Should we makes new patch to changes it, not revert it. Because
there are
arm platforms with more than 14 CPUs.
Thanks,
Liu Hua
-Kees
and arma15eb(GIC v2)
platforms. And the tests passed.
changes from V1:
- used for_each_set_bit instead of find_next_bit
- removed the GIC version indentifying codes.
- used one way to inactive GIC interupt states for all GIC version
Liu Hua (1):
GIC: introduce method to deactive interupts
-off-by: Liu Hua
---
drivers/irqchip/irq-gic.c | 26 ++
1 file changed, 26 insertions(+)
diff --git a/drivers/irqchip/irq-gic.c b/drivers/irqchip/irq-gic.c
index b2648fc..7708df1 100644
--- a/drivers/irqchip/irq-gic.c
+++ b/drivers/irqchip/irq-gic.c
@@ -351,12 +351,37
-off-by: Liu Hua sdu@huawei.com
---
drivers/irqchip/irq-gic.c | 26 ++
1 file changed, 26 insertions(+)
diff --git a/drivers/irqchip/irq-gic.c b/drivers/irqchip/irq-gic.c
index b2648fc..7708df1 100644
--- a/drivers/irqchip/irq-gic.c
+++ b/drivers/irqchip/irq-gic.c
and arma15eb(GIC v2)
platforms. And the tests passed.
changes from V1:
- used for_each_set_bit instead of find_next_bit
- removed the GIC version indentifying codes.
- used one way to inactive GIC interupt states for all GIC version
Liu Hua (1):
GIC: introduce method to deactive interupts
On 2014/7/11 20:35, Will Deacon wrote:
> [adding Marc]
>
> On Fri, Jul 11, 2014 at 07:46:15AM +0100, Liu Hua wrote:
>> For this version of GIC codes, kernel assumes that all the interrupt
>> status of GIC is inactive. So the kernel does not check this when
>> bootin
On 2014/7/11 20:35, Will Deacon wrote:
[adding Marc]
On Fri, Jul 11, 2014 at 07:46:15AM +0100, Liu Hua wrote:
For this version of GIC codes, kernel assumes that all the interrupt
status of GIC is inactive. So the kernel does not check this when
booting.
This is no problem on must
, but did not
find a simple way to deactive state of all interrupts. For GICv1,
I can only deal with one abnormal interrupt state one time. For
GICv2, I can deactive 32 one time.
So guys, Do you know a better way to do that?
Liu Hua (2):
irqchip: gic: introduce ICPIDR2 register interface
Peripheral ID2 Register provides a four-bit architecturally-defined
architecture revision field. So we can identify the GIC verison from
this register. It is useful sometimes.
Signed-off-by: Liu Hua
---
include/linux/irqchip/arm-gic.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include
-off-by: Liu Hua
---
drivers/irqchip/irq-gic.c | 57 +++
1 file changed, 57 insertions(+)
diff --git a/drivers/irqchip/irq-gic.c b/drivers/irqchip/irq-gic.c
index ddee133..d8620cf 100644
--- a/drivers/irqchip/irq-gic.c
+++ b/drivers/irqchip/irq-gic.c
-off-by: Liu Hua sdu@huawei.com
---
drivers/irqchip/irq-gic.c | 57 +++
1 file changed, 57 insertions(+)
diff --git a/drivers/irqchip/irq-gic.c b/drivers/irqchip/irq-gic.c
index ddee133..d8620cf 100644
--- a/drivers/irqchip/irq-gic.c
+++ b/drivers
Peripheral ID2 Register provides a four-bit architecturally-defined
architecture revision field. So we can identify the GIC verison from
this register. It is useful sometimes.
Signed-off-by: Liu Hua sdu@huawei.com
---
include/linux/irqchip/arm-gic.h | 1 +
1 file changed, 1 insertion
, but did not
find a simple way to deactive state of all interrupts. For GICv1,
I can only deal with one abnormal interrupt state one time. For
GICv2, I can deactive 32 one time.
So guys, Do you know a better way to do that?
Liu Hua (2):
irqchip: gic: introduce ICPIDR2 register interface
于 2014/6/26 8:57, Zhang, Yanmin 写道:
>
> On 2014/6/25 21:08, Liu hua wrote:
>> 于 2014/6/25 8:41, Zhang, Yanmin 写道:
>>> On 2014/6/20 18:47, Liu hua wrote:
>>>> On 2014/6/20 7:42, Luck, Tony wrote:
>>>>
>>>>>> BTW, I note that
于 2014/6/26 8:57, Zhang, Yanmin 写道:
On 2014/6/25 21:08, Liu hua wrote:
于 2014/6/25 8:41, Zhang, Yanmin 写道:
On 2014/6/20 18:47, Liu hua wrote:
On 2014/6/20 7:42, Luck, Tony wrote:
BTW, I note that extern struct pstore_info *psinfo locates in
fs/pstore/internal.h. So users out of directory
于 2014/6/25 8:41, Zhang, Yanmin 写道:
>
> On 2014/6/20 18:47, Liu hua wrote:
>> On 2014/6/20 7:42, Luck, Tony wrote:
>>
>>>> BTW, I note that "extern struct pstore_info *psinfo" locates in
>>>> fs/pstore/internal.h. So users out of directory
于 2014/6/25 8:41, Zhang, Yanmin 写道:
On 2014/6/20 18:47, Liu hua wrote:
On 2014/6/20 7:42, Luck, Tony wrote:
BTW, I note that extern struct pstore_info *psinfo locates in
fs/pstore/internal.h. So users out of directory fs/pstore/ can not use
pstore to
record messages. We do not want other
t; EXPORT_SYMBOL_GPL(pstore_alloc_ring_buffer);
>
> ... and you have to find/make some global header for the "extern" declaration.
I will make these RFC patch series according to our discussion. Thanks you very
to
valuable advice.
Thanks,
Liu Hua
>
> -Tony
>
&
very
to
valuable advice.
Thanks,
Liu Hua
-Tony
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org
uch again. if pstore can accept this feature, it will be a great
news for us.
we will drop our "KBOX" gradually, using pstore instead. If necessary, I will
try to send
patch series to do this. What do you think about it?
Thanks,
Liu Hua
> -Tony
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
struct.
Thanks very much again. if pstore can accept this feature, it will be a great
news for us.
we will drop our KBOX gradually, using pstore instead. If necessary, I will
try to send
patch series to do this. What do you think about it?
Thanks,
Liu Hua
-Tony
--
To unsubscribe from
We do not need to care other type messages to
overlap it.
we can allways get the latest messages of each type.
(3) Anyone in kernel or modules can use this mechanism, if they alloc a region.
Thanks,
Liu Hua
.
--
To unsubscribe from this list: send the line "unsubscribe linu
not need to care other type messages to
overlap it.
we can allways get the latest messages of each type.
(3) Anyone in kernel or modules can use this mechanism, if they alloc a region.
Thanks,
Liu Hua
.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel
h 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 t
.
See above.
Also, there is an error in the documentation below:
Signed-off-by: Liu Hua sdu@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
于 2014/5/6 20:15, Will Deacon 写道:
> On Sat, May 03, 2014 at 02:44:46PM +0100, Liu Hua wrote:
>> Hi Will or Russell,
>
> Hello,
>
>> With CONFIG_LPAE=y, memory in 32-bit ARM systems can exceed
>> 4G. So if we use kdump in such systems. The capture kernel
>
于 2014/5/6 20:15, Will Deacon 写道:
On Sat, May 03, 2014 at 02:44:46PM +0100, Liu Hua wrote:
Hi Will or Russell,
Hello,
With CONFIG_LPAE=y, memory in 32-bit ARM systems can exceed
4G. So if we use kdump in such systems. The capture kernel
should parse 64-bit elf header
On 2014/5/29 8:13, Simon Horman 写道:
> On Wed, May 28, 2014 at 09:49:56PM +0800, Liu Hua wrote:
>> This patch deales with sparse memory model.
>>
>> For ARM32 platforms, different vendors may define different
>> SECTION_SIZE_BITS, which we did not write to vmcore.
>&g
On 2014/5/29 8:13, Simon Horman 写道:
On Wed, May 28, 2014 at 09:49:56PM +0800, Liu Hua wrote:
This patch deales with sparse memory model.
For ARM32 platforms, different vendors may define different
SECTION_SIZE_BITS, which we did not write to vmcore.
For example:
1 arch/arm/mach-clps711x
On 2014/5/29 8:13, Simon Horman wrote:
> On Wed, May 28, 2014 at 09:49:56PM +0800, Liu Hua wrote:
>> This patch deales with sparse memory model.
>>
>> For ARM32 platforms, different vendors may define different
>> SECTION_SIZE_BITS, which we did not write to vmcore.
&
On 2014/5/29 8:13, Simon Horman wrote:
On Wed, May 28, 2014 at 09:49:56PM +0800, Liu Hua wrote:
This patch deales with sparse memory model.
For ARM32 platforms, different vendors may define different
SECTION_SIZE_BITS, which we did not write to vmcore.
For example:
1 arch/arm/mach
vmcores with different
SECTION_SIZE_BITS.
And if we enable LPAE, MAX_PHYSMEM_SIZE can alse
be variable.
This patch adds these SECTION_SIZE_BITS and MAX_PHYSMEM_SIZE
to vmcore. which makes user space tools more compatible.
BTW, makedumpfile has queued the related patch.
Signed-off-by: Liu Hua
vmcores with different
SECTION_SIZE_BITS.
And if we enable LPAE, MAX_PHYSMEM_SIZE can alse
be variable.
This patch adds these SECTION_SIZE_BITS and MAX_PHYSMEM_SIZE
to vmcore. which makes user space tools more compatible.
BTW, makedumpfile has queued the related patch.
Signed-off-by: Liu Hua sdu
o repost this patch set, then I'll accept it.
>
Ok, Thanks for you suggest. I will repost this patch. By now no one
relpy my kernel patch related to this issue, named "[RFC PATCH 1/2]
kdump: add sparse memory related values to vmcore". Didn't I cc
the right person or something el
memory related values to vmcore. Didn't I cc
the right person or something else?
BTW, For patch [PATCH] makedumpfile: ARM: get correct mem_map offset,
Did I explain my idea clearly ? If not, I would like repost one with
more details.
Thanks,
Liu Hua
Thanks
Atsushi Kumagai
This patch makes
arch/arm/mach-hisi/include/mach/memory.h
#define SECTION_SIZE_BITS 26
8 arch/arm/mach-sa1100/include/mach/memory.h
#define SECTION_SIZE_BITS 27
Perhaps we should find another way to let the userspace tools
to get the architecture-specific values.
Liu Hua
>
>
> Thanks
>
/include/mach/memory.h
#define SECTION_SIZE_BITS 27
Perhaps we should find another way to let the userspace tools
to get the architecture-specific values.
Liu Hua
Thanks
Atsushi Kumagai
This patch makes makedumpfile get these two values from
vmcore info, if existing. It makes
SECTION
size. We must recompile it. It is awaste of time.
So this patch add related values to vmcore to notify the
user space tools to deal with this situation.
Signed-off-by: Liu Hua
---
kernel/kexec.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/kernel/kexec.c b/kernel/kexec.c
index
to recompile the tools.
These patch series make kernel pass related infomation to
the user space tools, via vmcore. And makedumpfile can
get these when parsing vmcore. So the makdumpfile becomes
more compatible to vmcore with different section size.
Liu Hua (1):
kdump: add sparse memory related
to vmcores with different section size.
Signed-off-by: Liu Hua
---
makedumpfile.c | 17 +
makedumpfile.h | 2 ++
2 files changed, 19 insertions(+)
diff --git a/makedumpfile.c b/makedumpfile.c
index 6cf6e24..3cdf323 100644
--- a/makedumpfile.c
+++ b/makedumpfile.c
@@ -2111,6 +2111,8
to vmcores with different section size.
Signed-off-by: Liu Hua sdu@huawei.com
---
makedumpfile.c | 17 +
makedumpfile.h | 2 ++
2 files changed, 19 insertions(+)
diff --git a/makedumpfile.c b/makedumpfile.c
index 6cf6e24..3cdf323 100644
--- a/makedumpfile.c
+++ b/makedumpfile.c
to recompile the tools.
These patch series make kernel pass related infomation to
the user space tools, via vmcore. And makedumpfile can
get these when parsing vmcore. So the makdumpfile becomes
more compatible to vmcore with different section size.
Liu Hua (1):
kdump: add sparse memory related
SECTION
size. We must recompile it. It is awaste of time.
So this patch add related values to vmcore to notify the
user space tools to deal with this situation.
Signed-off-by: Liu Hua sdu@huawei.com
---
kernel/kexec.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/kernel/kexec.c b
On 2014/4/23 7:50, Nicolas Pitre wrote:
> On Tue, 22 Apr 2014, Russell King - ARM Linux wrote:
>
>> On Tue, Apr 15, 2014 at 07:06:05PM +0800, Liu Hua wrote:
>>> This patch series change fixmap mapping region to suppport 32 CPUs.
>>> Because the "top_pmd
function by commit 4b3bf7aef.
This patch adds check functions related to elf64 header.
Thanks,
Liu Hua
Signed-off-by: Liu Hua
---
arch/arm/include/asm/elf.h | 4 +++-
arch/arm/kernel/elf.c | 33 +
2 files changed, 36 insertions(+), 1 deletion(-)
diff --git a/arch
function by commit 4b3bf7aef.
This patch adds check functions related to elf64 header.
Thanks,
Liu Hua
Signed-off-by: Liu Hua sdu@huawei.com
---
arch/arm/include/asm/elf.h | 4 +++-
arch/arm/kernel/elf.c | 33 +
2 files changed, 36 insertions(+), 1 deletion
On 2014/4/23 7:50, Nicolas Pitre wrote:
On Tue, 22 Apr 2014, Russell King - ARM Linux wrote:
On Tue, Apr 15, 2014 at 07:06:05PM +0800, Liu Hua wrote:
This patch series change fixmap mapping region to suppport 32 CPUs.
Because the top_pmd covers 0xfffe - 0x(2M). And part
is used
platforms
Changes from v2:
---
- Removed two macros: FIX_KMAP_BEGIN and FIX_KMAP_END;
- Unchanged DMA mapping region related documentation;
Changes from v1:
---
- changed documentation for ARM linux memory layout.
- moved fixmap mapping region, not just extended.
Liu Hua
to 32 CPUs
Signed-off-by: Liu Hua
---
Documentation/arm/memory.txt | 2 +-
arch/arm/include/asm/fixmap.h | 16 ++--
arch/arm/include/asm/highmem.h | 1 +
arch/arm/mm/highmem.c | 27 +--
arch/arm/mm/mmu.c | 4
5 files changed, 29
a bugfix on fixmap mapping region.
Reviewed-by: Nicolas Pitre
Signed-off-by: Liu Hua
---
arch/arm/include/asm/fixmap.h | 5 ++---
arch/arm/mm/highmem.c | 6 +++---
2 files changed, 5 insertions(+), 6 deletions(-)
diff --git a/arch/arm/include/asm/fixmap.h b/arch/arm/include/asm/fixmap.h
index
于 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 rem
于 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 who need
a bugfix on fixmap mapping region.
Reviewed-by: Nicolas Pitre n...@linaro.org
Signed-off-by: Liu Hua sdu@huawei.com
---
arch/arm/include/asm/fixmap.h | 5 ++---
arch/arm/mm/highmem.c | 6 +++---
2 files changed, 5 insertions(+), 6 deletions(-)
diff --git a/arch/arm/include/asm/fixmap.h b
to 32 CPUs
Signed-off-by: Liu Hua sdu@huawei.com
---
Documentation/arm/memory.txt | 2 +-
arch/arm/include/asm/fixmap.h | 16 ++--
arch/arm/include/asm/highmem.h | 1 +
arch/arm/mm/highmem.c | 27 +--
arch/arm/mm/mmu.c | 4
5
from v2:
---
- Removed two macros: FIX_KMAP_BEGIN and FIX_KMAP_END;
- Unchanged DMA mapping region related documentation;
Changes from v1:
---
- changed documentation for ARM linux memory layout.
- moved fixmap mapping region, not just extended.
Liu Hua (2):
ARM
于 2014/4/14 19:37, Will Deacon 写道:
> On Thu, Mar 27, 2014 at 08:00:39AM +0000, Liu Hua wrote:
>> For vmcore generated by LPAE enabled kernel, user space
>> utility such as crash needs additional infomation to
>> parse.
>>
>> So this patch add arch_crash_save_vmcor
于 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.
&g
于 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);
+idx -= FIX_KMAP_BEGIN
于 2014/4/14 19:37, Will Deacon 写道:
On Thu, Mar 27, 2014 at 08:00:39AM +, Liu Hua wrote:
For vmcore generated by LPAE enabled kernel, user space
utility such as crash needs additional infomation to
parse.
So this patch add arch_crash_save_vmcoreinfo as what PAE enabled
i386 linux does
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.
>>
On 2014/4/12 22:32, Nicolas Pitre write:
> On Sat, 12 Apr 2014, Liu hua wrote:
>
>> Hi Nicolas,
>>
>> Your version is better. you tell me this in the former letters.
>> So I am very sorry to forget to check that.
>>
>> May be I should remake this secon
On 2014/4/12 22:32, Nicolas Pitre write:
On Sat, 12 Apr 2014, Liu hua wrote:
Hi Nicolas,
Your version is better. you tell me this in the former letters.
So I am very sorry to forget to check that.
May be I should remake this second patch to fit your change. What do
you think about
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 region
Hi Nicolas,
Your version is better. you tell me this in the former letters.
So I am very sorry to forget to check that.
May be I should remake this second patch to fit your change. What do
you think about that patch?
Liu Hua
On 2014/4/12 11:12, Nicolas Pitre wrote:
> On Fri, 11 Apr 2014,
Because commit e9da6e9905e6 has remove custom consistent dma
region. So the related variable and document should be removed
Signed-off-by: Liu Hua
---
Documentation/arm/memory.txt | 4
arch/arm/include/asm/memory.h | 2 --
2 files changed, 6 deletions(-)
diff --git a/Documentation/arm
to 32 CPUs.
Signed-off-by: Liu Hua
---
Documentation/arm/memory.txt | 2 +-
arch/arm/include/asm/fixmap.h | 4 ++--
arch/arm/include/asm/highmem.h | 1 +
arch/arm/mm/highmem.c | 10 +-
arch/arm/mm/mm.h | 7 +++
arch/arm/mm/mmu.c | 4
- changed documentation for ARM linux memory layout.
- moved fixmap mapping region, not just extended.
Liu Hua (2):
ARM : DMA : remove useless information about DMA
ARM : extend fixmap mapping region to support 32 CPUs
Documentation/arm/memory.txt | 8 ++--
arch/arm/include/asm/fixmap.h | 4
documentation for ARM linux memory layout.
- moved fixmap mapping region, not just extended.
Liu Hua (2):
ARM : DMA : remove useless information about DMA
ARM : extend fixmap mapping region to support 32 CPUs
Documentation/arm/memory.txt | 8 ++--
arch/arm/include/asm/fixmap.h | 4 ++--
arch
to 32 CPUs.
Signed-off-by: Liu Hua sdu@huawei.com
---
Documentation/arm/memory.txt | 2 +-
arch/arm/include/asm/fixmap.h | 4 ++--
arch/arm/include/asm/highmem.h | 1 +
arch/arm/mm/highmem.c | 10 +-
arch/arm/mm/mm.h | 7 +++
arch/arm/mm/mmu.c
Because commit e9da6e9905e6 has remove custom consistent dma
region. So the related variable and document should be removed
Signed-off-by: Liu Hua sdu@huawei.com
---
Documentation/arm/memory.txt | 4
arch/arm/include/asm/memory.h | 2 --
2 files changed, 6 deletions(-)
diff --git
Hi Nicolas,
Your version is better. you tell me this in the former letters.
So I am very sorry to forget to check that.
May be I should remake this second patch to fit your change. What do
you think about that patch?
Liu Hua
On 2014/4/12 11:12, Nicolas Pitre wrote:
On Fri, 11 Apr 2014, Liu
parameter.
Signed-off-by: Liu Hua
Tested-by: Satoru Takeuchi
Cc: sta...@vger.kernel.org # 3.4+
---
Documentation/sysctl/kernel.txt | 1 +
kernel/sysctl.c | 6 ++
2 files changed, 7 insertions(+)
diff --git a/Documentation/sysctl/kernel.txt b/Documentation/sysctl/kernel
.
Signed-off-by: Liu Hua sdu@huawei.com
Tested-by: Satoru Takeuchi satoru.takeu...@gmail.com
Cc: sta...@vger.kernel.org # 3.4+
---
Documentation/sysctl/kernel.txt | 1 +
kernel/sysctl.c | 6 ++
2 files changed, 7 insertions(+)
diff --git a/Documentation/sysctl/kernel.txt b
32-bit elf header.
Signed-off-by: Liu Hua
To: Simon Horman
Cc: Vivek Goyal
Cc:
Cc:
Cc:
---
kexec/arch/arm/crashdump-arm.c | 23 ---
kexec/kexec-iomem.c| 8
kexec/kexec.h | 4 ++--
3 files changed, 26 insertions(+), 9 deletions
For vmcore generated by LPAE enabled kernel, user space
utility such as crash needs additional infomation to
parse.
So this patch add arch_crash_save_vmcoreinfo as what PAE enabled
i386 linux does.
Signed-off-by: Liu Hua
To: Russell King
Cc: Stephen Warren
Cc: Will Deacon
Cc: Vijaya Kumar K
functions related of elf64 header.
Signed-off-by: Liu Hua
To: Russell King
Cc: Dan Aloni
Cc: Catalin Marinas
Cc:
Cc:
Cc:
---
arch/arm/include/asm/elf.h | 5 -
arch/arm/kernel/elf.c | 33 +
2 files changed, 37 insertions(+), 1 deletion(-)
diff --git a/arch
functions related of elf64 header.
Signed-off-by: Liu Hua sdu@huawei.com
To: Russell King li...@arm.linux.org.uk
Cc: Dan Aloni alo...@stratoscale.com
Cc: Catalin Marinas catalin.mari...@arm.com
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
Cc: ke...@lists.infradead.org
For vmcore generated by LPAE enabled kernel, user space
utility such as crash needs additional infomation to
parse.
So this patch add arch_crash_save_vmcoreinfo as what PAE enabled
i386 linux does.
Signed-off-by: Liu Hua sdu@huawei.com
To: Russell King li...@arm.linux.org.uk
Cc: Stephen
32-bit elf header.
Signed-off-by: Liu Hua sdu@huawei.com
To: Simon Horman ho...@verge.net.au
Cc: Vivek Goyal vgo...@redhat.com
Cc: ke...@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
Cc: linux-arm-ker...@lists.infradead.org
---
kexec/arch/arm/crashdump-arm.c | 23
于 2014/3/26 0:25, Satoru Takeuchi 写道:
> At Tue, 25 Mar 2014 16:58:58 +0800,
> Liu hua wrote:
>>
>> 于 2014/3/24 4:50, Satoru Takeuchi 写道:
>>> At Sun, 23 Mar 2014 15:54:04 +0800,
>>> Liu Hua wrote:
>>>>
>>>> As sysctl_hung_task_
于 2014/3/26 0:25, Satoru Takeuchi 写道:
At Tue, 25 Mar 2014 16:58:58 +0800,
Liu hua wrote:
于 2014/3/24 4:50, Satoru Takeuchi 写道:
At Sun, 23 Mar 2014 15:54:04 +0800,
Liu Hua wrote:
As sysctl_hung_task_timeout_sec is unsigned long, when this value is
larger then LONG_MAX/HZ, the function
于 2014/3/24 4:50, Satoru Takeuchi 写道:
> At Sun, 23 Mar 2014 15:54:04 +0800,
> Liu Hua wrote:
>>
>> As sysctl_hung_task_timeout_sec is unsigned long, when this value is
>> larger then LONG_MAX/HZ, the function schedule_timeout_interruptible in
>> watchdog will re
于 2014/3/24 4:50, Satoru Takeuchi 写道:
At Sun, 23 Mar 2014 15:54:04 +0800,
Liu Hua wrote:
As sysctl_hung_task_timeout_sec is unsigned long, when this value is
larger then LONG_MAX/HZ, the function schedule_timeout_interruptible in
watchdog will return immediately without sleep and with print
mapping region can support up to 30 CPUs.
There seems to be no easy way to support 32 CPUs by simply
changing memory layout on ARM Linux. So I also limit the
maximal CPU number one can configure.
Signed-off-by: Liu Hua
---
Documentation/arm/memory.txt | 4 ++--
arch/arm/Kconfig
mapping region can support up to 30 CPUs.
There seems to be no easy way to support 32 CPUs by simply
changing memory layout on ARM Linux. So I also limit the
maximal CPU number one can configure.
Signed-off-by: Liu Hua sdu@huawei.com
---
Documentation/arm/memory.txt | 4 ++--
arch/arm
the valid parameter.
Cc:
Signed-off-by: Liu Hua
---
kernel/hung_task.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/kernel/hung_task.c b/kernel/hung_task.c
index 6df6149..f992286 100644
--- a/kernel/hung_task.c
+++ b/kernel/hung_task.c
@@ -174,8 +174,12 @@ s
parameter.
Cc: sta...@vger.kernel.org
Signed-off-by: Liu Hua sdu@huawei.com
---
kernel/hung_task.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/kernel/hung_task.c b/kernel/hung_task.c
index 6df6149..f992286 100644
--- a/kernel/hung_task.c
+++ b/kernel/hung_task.c
1 - 100 of 112 matches
Mail list logo
