(2013/12/04 0:12), Vivek Goyal wrote:
On Tue, Dec 03, 2013 at 02:16:35PM +0900, HATAYAMA Daisuke wrote:
[..]
Even if copying partial pages into the 2nd kernel, we need to use ioremap()
once on them, and I think the ioremap() is exactly similar to
remap_pfn_range() for a single page. There
(2013/12/04 0:12), Vivek Goyal wrote:
On Tue, Dec 03, 2013 at 02:16:35PM +0900, HATAYAMA Daisuke wrote:
[..]
Even if copying partial pages into the 2nd kernel, we need to use ioremap()
once on them, and I think the ioremap() is exactly similar to
remap_pfn_range() for a single page. There
On Tue, Dec 03, 2013 at 02:16:35PM +0900, HATAYAMA Daisuke wrote:
[..]
> >Even if copying partial pages into the 2nd kernel, we need to use ioremap()
> >once on them, and I think the ioremap() is exactly similar to
> >remap_pfn_range() for a single page. There seems no difference on safeness
>
On Tue, Dec 03, 2013 at 10:18:16AM +0900, HATAYAMA Daisuke wrote:
> (2013/12/03 0:27), Vivek Goyal wrote:
> >On Thu, Nov 28, 2013 at 05:48:02PM +0900, HATAYAMA Daisuke wrote:
> >>Hello Vivek,
> >>
> >>Here is a patch set for mmap failure for /proc/vmcore.
> >>Could you try to use this on the
On Tue, Dec 03, 2013 at 10:18:16AM +0900, HATAYAMA Daisuke wrote:
(2013/12/03 0:27), Vivek Goyal wrote:
On Thu, Nov 28, 2013 at 05:48:02PM +0900, HATAYAMA Daisuke wrote:
Hello Vivek,
Here is a patch set for mmap failure for /proc/vmcore.
Could you try to use this on the problematic system?
On Tue, Dec 03, 2013 at 02:16:35PM +0900, HATAYAMA Daisuke wrote:
[..]
Even if copying partial pages into the 2nd kernel, we need to use ioremap()
once on them, and I think the ioremap() is exactly similar to
remap_pfn_range() for a single page. There seems no difference on safeness
between
(2013/12/03 10:18), HATAYAMA Daisuke wrote:
(2013/12/03 0:27), Vivek Goyal wrote:
On Thu, Nov 28, 2013 at 05:48:02PM +0900, HATAYAMA Daisuke wrote:
Hello Vivek,
Here is a patch set for mmap failure for /proc/vmcore.
Could you try to use this on the problematic system?
This patch doesn't copy
(2013/12/03 0:27), Vivek Goyal wrote:
On Thu, Nov 28, 2013 at 05:48:02PM +0900, HATAYAMA Daisuke wrote:
Hello Vivek,
Here is a patch set for mmap failure for /proc/vmcore.
Could you try to use this on the problematic system?
This patch doesn't copy partial pages to the 2nd kernel, only
ocate
page in new kernel, read *only* those bytes as reported by elf header
and fill rest of the page with zeros.
Thanks
Vivek
>
> >From c8323be2a2972dcb3f252598c39abfa23078 Mon Sep 17 00:00:00 2001
> From: HATAYAMA Daisuke
> Date: Thu, 28 Nov 2013 14:51:22 +0900
> Sub
remap_pfn_range() separately for respective
partial pages
Acording to the report by Vivek in
https://lkml.org/lkml/2013/11/13/439, on some specific systems, some
of the System RAM ranges don't end at page boundary and the later part
of the same page is used for some kind of ACPI data. As a result
(2013/12/03 0:27), Vivek Goyal wrote:
On Thu, Nov 28, 2013 at 05:48:02PM +0900, HATAYAMA Daisuke wrote:
Hello Vivek,
Here is a patch set for mmap failure for /proc/vmcore.
Could you try to use this on the problematic system?
This patch doesn't copy partial pages to the 2nd kernel, only
(2013/12/03 10:18), HATAYAMA Daisuke wrote:
(2013/12/03 0:27), Vivek Goyal wrote:
On Thu, Nov 28, 2013 at 05:48:02PM +0900, HATAYAMA Daisuke wrote:
Hello Vivek,
Here is a patch set for mmap failure for /proc/vmcore.
Could you try to use this on the problematic system?
This patch doesn't copy
.
>From c8323be2a2972dcb3f252598c39abfa23078 Mon Sep 17 00:00:00 2001
From: HATAYAMA Daisuke
Date: Thu, 28 Nov 2013 14:51:22 +0900
Subject: [PATCH] vmcore: call remap_pfn_range() separately for respective
partial pages
Acording to the report by Vivek in
https://lkml.org/lkml/2013/11/13/
.
From c8323be2a2972dcb3f252598c39abfa23078 Mon Sep 17 00:00:00 2001
From: HATAYAMA Daisuke d.hatay...@jp.fujitsu.com
Date: Thu, 28 Nov 2013 14:51:22 +0900
Subject: [PATCH] vmcore: call remap_pfn_range() separately for respective
partial pages
Acording to the report by Vivek in
https://lkml.org
14 matches
Mail list logo
