Re: [PATCH v2 06/20] vmcore, procfs: introduce a flag to distinguish objects copied in 2nd kernel

2013-03-06 Thread Yanfei Zhang
2013/3/2 HATAYAMA Daisuke :
> The part of dump target memory is copied into the 2nd kernel if it
> doesn't satisfy mmap()'s page-size boundary requirement. To
> distinguish such copied object from usual old memory, a flag
> MEM_TYPE_CURRENT_KERNEL is introduced. If this flag is set, the object
> is considered being copied into buffer on the 2nd kernel.

Reviewed-by: Zhang Yanfei 

>
> Signed-off-by: HATAYAMA Daisuke 
> ---
>
>  include/linux/proc_fs.h |8 +++-
>  1 files changed, 7 insertions(+), 1 deletions(-)
>
> diff --git a/include/linux/proc_fs.h b/include/linux/proc_fs.h
> index 8307f2f..11dd592 100644
> --- a/include/linux/proc_fs.h
> +++ b/include/linux/proc_fs.h
> @@ -97,11 +97,17 @@ struct kcore_list {
> int type;
>  };
>
> +#define MEM_TYPE_CURRENT_KERNEL 0x1
> +
>  struct vmcore {
> struct list_head list;
> -   unsigned long long paddr;
> +   union {
> +   unsigned long long paddr;
> +   char *buf;
> +   };
> unsigned long long size;
> loff_t offset;
> +   unsigned int flag;
>  };
>
>  #ifdef CONFIG_PROC_FS
>
> --
> 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/
--
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/


Re: [PATCH v2 06/20] vmcore, procfs: introduce a flag to distinguish objects copied in 2nd kernel

2013-03-06 Thread Yanfei Zhang
2013/3/2 HATAYAMA Daisuke d.hatay...@jp.fujitsu.com:
 The part of dump target memory is copied into the 2nd kernel if it
 doesn't satisfy mmap()'s page-size boundary requirement. To
 distinguish such copied object from usual old memory, a flag
 MEM_TYPE_CURRENT_KERNEL is introduced. If this flag is set, the object
 is considered being copied into buffer on the 2nd kernel.

Reviewed-by: Zhang Yanfei zhangyan...@cn.fujitsu.com


 Signed-off-by: HATAYAMA Daisuke d.hatay...@jp.fujitsu.com
 ---

  include/linux/proc_fs.h |8 +++-
  1 files changed, 7 insertions(+), 1 deletions(-)

 diff --git a/include/linux/proc_fs.h b/include/linux/proc_fs.h
 index 8307f2f..11dd592 100644
 --- a/include/linux/proc_fs.h
 +++ b/include/linux/proc_fs.h
 @@ -97,11 +97,17 @@ struct kcore_list {
 int type;
  };

 +#define MEM_TYPE_CURRENT_KERNEL 0x1
 +
  struct vmcore {
 struct list_head list;
 -   unsigned long long paddr;
 +   union {
 +   unsigned long long paddr;
 +   char *buf;
 +   };
 unsigned long long size;
 loff_t offset;
 +   unsigned int flag;
  };

  #ifdef CONFIG_PROC_FS

 --
 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/
--
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/


[PATCH v2 06/20] vmcore, procfs: introduce a flag to distinguish objects copied in 2nd kernel

2013-03-04 Thread HATAYAMA Daisuke
The part of dump target memory is copied into the 2nd kernel if it
doesn't satisfy mmap()'s page-size boundary requirement. To
distinguish such copied object from usual old memory, a flag
MEM_TYPE_CURRENT_KERNEL is introduced. If this flag is set, the object
is considered being copied into buffer on the 2nd kernel.

Signed-off-by: HATAYAMA Daisuke 
---

 include/linux/proc_fs.h |8 +++-
 1 files changed, 7 insertions(+), 1 deletions(-)

diff --git a/include/linux/proc_fs.h b/include/linux/proc_fs.h
index 8307f2f..11dd592 100644
--- a/include/linux/proc_fs.h
+++ b/include/linux/proc_fs.h
@@ -97,11 +97,17 @@ struct kcore_list {
int type;
 };
 
+#define MEM_TYPE_CURRENT_KERNEL 0x1
+
 struct vmcore {
struct list_head list;
-   unsigned long long paddr;
+   union {
+   unsigned long long paddr;
+   char *buf;
+   };
unsigned long long size;
loff_t offset;
+   unsigned int flag;
 };
 
 #ifdef CONFIG_PROC_FS

--
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/


[PATCH v2 06/20] vmcore, procfs: introduce a flag to distinguish objects copied in 2nd kernel

2013-03-04 Thread HATAYAMA Daisuke
The part of dump target memory is copied into the 2nd kernel if it
doesn't satisfy mmap()'s page-size boundary requirement. To
distinguish such copied object from usual old memory, a flag
MEM_TYPE_CURRENT_KERNEL is introduced. If this flag is set, the object
is considered being copied into buffer on the 2nd kernel.

Signed-off-by: HATAYAMA Daisuke d.hatay...@jp.fujitsu.com
---

 include/linux/proc_fs.h |8 +++-
 1 files changed, 7 insertions(+), 1 deletions(-)

diff --git a/include/linux/proc_fs.h b/include/linux/proc_fs.h
index 8307f2f..11dd592 100644
--- a/include/linux/proc_fs.h
+++ b/include/linux/proc_fs.h
@@ -97,11 +97,17 @@ struct kcore_list {
int type;
 };
 
+#define MEM_TYPE_CURRENT_KERNEL 0x1
+
 struct vmcore {
struct list_head list;
-   unsigned long long paddr;
+   union {
+   unsigned long long paddr;
+   char *buf;
+   };
unsigned long long size;
loff_t offset;
+   unsigned int flag;
 };
 
 #ifdef CONFIG_PROC_FS

--
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/