Re: [PATCH 1/3] xen: sync some headers with xen tree

2014-09-05 Thread Juergen Gross

On 09/04/2014 02:52 PM, Jan Beulich wrote:

On 04.09.14 at 14:38, <"jgr...@suse.com".non-mime.internet> wrote:

As the KEXEC and DUMPCORE related ELFNOTES are not relevant for the
kernel they are omitted from elfnote.h.


But the defines are still in the patch:


Oops, old header version. I'll correct it.


Juergen

--
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 1/3] xen: sync some headers with xen tree

2014-09-05 Thread Juergen Gross

On 09/04/2014 02:52 PM, Jan Beulich wrote:

On 04.09.14 at 14:38, jgr...@suse.com.non-mime.internet wrote:

As the KEXEC and DUMPCORE related ELFNOTES are not relevant for the
kernel they are omitted from elfnote.h.


But the defines are still in the patch:


Oops, old header version. I'll correct it.


Juergen

--
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 1/3] xen: sync some headers with xen tree

2014-09-04 Thread Jan Beulich
>>> On 04.09.14 at 14:38, <"jgr...@suse.com".non-mime.internet> wrote:
> As the KEXEC and DUMPCORE related ELFNOTES are not relevant for the
> kernel they are omitted from elfnote.h.

But the defines are still in the patch:

> @@ -153,6 +192,65 @@
>   */
>  #define XEN_ELFNOTE_SUPPORTED_FEATURES 17
>  
> +/*
> + * The number of the highest elfnote defined.
> + */
> +#define XEN_ELFNOTE_MAX XEN_ELFNOTE_SUPPORTED_FEATURES
> +
> +/*
> + * System information exported through crash notes.
> + *
> + * The kexec / kdump code will create one XEN_ELFNOTE_CRASH_INFO
> + * note in case of a system crash. This note will contain various
> + * information about the system, see xen/include/xen/elfcore.h.
> + */
> +#define XEN_ELFNOTE_CRASH_INFO 0x101
> +
> +/*
> + * System registers exported through crash notes.
> + *
> + * The kexec / kdump code will create one XEN_ELFNOTE_CRASH_REGS
> + * note per cpu in case of a system crash. This note is architecture
> + * specific and will contain registers not saved in the "CORE" note.
> + * See xen/include/xen/elfcore.h for more information.
> + */
> +#define XEN_ELFNOTE_CRASH_REGS 0x102
> +
> +
> +/*
> + * xen dump-core none note.
> + * xm dump-core code will create one XEN_ELFNOTE_DUMPCORE_NONE
> + * in its dump file to indicate that the file is xen dump-core
> + * file. This note doesn't have any other information.
> + * See tools/libxc/xc_core.h for more information.
> + */
> +#define XEN_ELFNOTE_DUMPCORE_NONE   0x200
> +
> +/*
> + * xen dump-core header note.
> + * xm dump-core code will create one XEN_ELFNOTE_DUMPCORE_HEADER
> + * in its dump file.
> + * See tools/libxc/xc_core.h for more information.
> + */
> +#define XEN_ELFNOTE_DUMPCORE_HEADER 0x201
> +
> +/*
> + * xen dump-core xen version note.
> + * xm dump-core code will create one XEN_ELFNOTE_DUMPCORE_XEN_VERSION
> + * in its dump file. It contains the xen version obtained via the
> + * XENVER hypercall.
> + * See tools/libxc/xc_core.h for more information.
> + */
> +#define XEN_ELFNOTE_DUMPCORE_XEN_VERSION0x202
> +
> +/*
> + * xen dump-core format version note.
> + * xm dump-core code will create one XEN_ELFNOTE_DUMPCORE_FORMAT_VERSION
> + * in its dump file. It contains a format version identifier.
> + * See tools/libxc/xc_core.h for more information.
> + */
> +#define XEN_ELFNOTE_DUMPCORE_FORMAT_VERSION 0x203
> +
>  #endif /* __XEN_PUBLIC_ELFNOTE_H__ */
>  
>  /*

Jan

--
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 1/3] xen: sync some headers with xen tree

2014-09-04 Thread Juergen Gross
To be able to use an initially unmapped initrd with xen the following
header files must be synced to a newer version from the xen tree:

include/xen/interface/elfnote.h
include/xen/interface/xen.h

As the KEXEC and DUMPCORE related ELFNOTES are not relevant for the
kernel they are omitted from elfnote.h.

Signed-off-by: Juergen Gross 
---
 include/xen/interface/elfnote.h | 102 ++-
 include/xen/interface/xen.h | 272 
 2 files changed, 348 insertions(+), 26 deletions(-)

diff --git a/include/xen/interface/elfnote.h b/include/xen/interface/elfnote.h
index 6f4eae3..5501e7a 100644
--- a/include/xen/interface/elfnote.h
+++ b/include/xen/interface/elfnote.h
@@ -3,6 +3,24 @@
  *
  * Definitions used for the Xen ELF notes.
  *
+ * Permission is hereby granted, free of charge, to any person obtaining a copy
+ * of this software and associated documentation files (the "Software"), to
+ * deal in the Software without restriction, including without limitation the
+ * rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
+ * sell copies of the Software, and to permit persons to whom the Software is
+ * furnished to do so, subject to the following conditions:
+ *
+ * The above copyright notice and this permission notice shall be included in
+ * all copies or substantial portions of the Software.
+ *
+ * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+ * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+ * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+ * AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+ * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+ * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
+ * DEALINGS IN THE SOFTWARE.
+ *
  * Copyright (c) 2006, Ian Campbell, XenSource Ltd.
  */
 
@@ -18,12 +36,13 @@
  *
  * LEGACY indicated the fields in the legacy __xen_guest string which
  * this a note type replaces.
+ *
+ * String values (for non-legacy) are NULL terminated ASCII, also known
+ * as ASCIZ type.
  */
 
 /*
  * NAME=VALUE pair (string).
- *
- * LEGACY: FEATURES and PAE
  */
 #define XEN_ELFNOTE_INFO   0
 
@@ -137,10 +156,30 @@
 
 /*
  * Whether or not the guest supports cooperative suspend cancellation.
+ * This is a numeric value.
+ *
+ * Default is 0
  */
 #define XEN_ELFNOTE_SUSPEND_CANCEL 14
 
 /*
+ * The (non-default) location the initial phys-to-machine map should be
+ * placed at by the hypervisor (Dom0) or the tools (DomU).
+ * The kernel must be prepared for this mapping to be established using
+ * large pages, despite such otherwise not being available to guests.
+ * The kernel must also be able to handle the page table pages used for
+ * this mapping not being accessible through the initial mapping.
+ * (Only x86-64 supports this at present.)
+ */
+#define XEN_ELFNOTE_INIT_P2M  15
+
+/*
+ * Whether or not the guest can deal with being passed an initrd not
+ * mapped through its initial page tables.
+ */
+#define XEN_ELFNOTE_MOD_START_PFN 16
+
+/*
  * The features supported by this kernel (numeric).
  *
  * Other than XEN_ELFNOTE_FEATURES on pre-4.2 Xen, this note allows a
@@ -153,6 +192,65 @@
  */
 #define XEN_ELFNOTE_SUPPORTED_FEATURES 17
 
+/*
+ * The number of the highest elfnote defined.
+ */
+#define XEN_ELFNOTE_MAX XEN_ELFNOTE_SUPPORTED_FEATURES
+
+/*
+ * System information exported through crash notes.
+ *
+ * The kexec / kdump code will create one XEN_ELFNOTE_CRASH_INFO
+ * note in case of a system crash. This note will contain various
+ * information about the system, see xen/include/xen/elfcore.h.
+ */
+#define XEN_ELFNOTE_CRASH_INFO 0x101
+
+/*
+ * System registers exported through crash notes.
+ *
+ * The kexec / kdump code will create one XEN_ELFNOTE_CRASH_REGS
+ * note per cpu in case of a system crash. This note is architecture
+ * specific and will contain registers not saved in the "CORE" note.
+ * See xen/include/xen/elfcore.h for more information.
+ */
+#define XEN_ELFNOTE_CRASH_REGS 0x102
+
+
+/*
+ * xen dump-core none note.
+ * xm dump-core code will create one XEN_ELFNOTE_DUMPCORE_NONE
+ * in its dump file to indicate that the file is xen dump-core
+ * file. This note doesn't have any other information.
+ * See tools/libxc/xc_core.h for more information.
+ */
+#define XEN_ELFNOTE_DUMPCORE_NONE   0x200
+
+/*
+ * xen dump-core header note.
+ * xm dump-core code will create one XEN_ELFNOTE_DUMPCORE_HEADER
+ * in its dump file.
+ * See tools/libxc/xc_core.h for more information.
+ */
+#define XEN_ELFNOTE_DUMPCORE_HEADER 0x201
+
+/*
+ * xen dump-core xen version note.
+ * xm dump-core code will create one XEN_ELFNOTE_DUMPCORE_XEN_VERSION
+ * in its dump file. It contains the xen version obtained via the
+ * XENVER hypercall.
+ * See tools/libxc/xc_core.h for more information.
+ */
+#define 

[PATCH 1/3] xen: sync some headers with xen tree

2014-09-04 Thread Juergen Gross
To be able to use an initially unmapped initrd with xen the following
header files must be synced to a newer version from the xen tree:

include/xen/interface/elfnote.h
include/xen/interface/xen.h

As the KEXEC and DUMPCORE related ELFNOTES are not relevant for the
kernel they are omitted from elfnote.h.

Signed-off-by: Juergen Gross jgr...@suse.com
---
 include/xen/interface/elfnote.h | 102 ++-
 include/xen/interface/xen.h | 272 
 2 files changed, 348 insertions(+), 26 deletions(-)

diff --git a/include/xen/interface/elfnote.h b/include/xen/interface/elfnote.h
index 6f4eae3..5501e7a 100644
--- a/include/xen/interface/elfnote.h
+++ b/include/xen/interface/elfnote.h
@@ -3,6 +3,24 @@
  *
  * Definitions used for the Xen ELF notes.
  *
+ * Permission is hereby granted, free of charge, to any person obtaining a copy
+ * of this software and associated documentation files (the Software), to
+ * deal in the Software without restriction, including without limitation the
+ * rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
+ * sell copies of the Software, and to permit persons to whom the Software is
+ * furnished to do so, subject to the following conditions:
+ *
+ * The above copyright notice and this permission notice shall be included in
+ * all copies or substantial portions of the Software.
+ *
+ * THE SOFTWARE IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+ * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+ * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+ * AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+ * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+ * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
+ * DEALINGS IN THE SOFTWARE.
+ *
  * Copyright (c) 2006, Ian Campbell, XenSource Ltd.
  */
 
@@ -18,12 +36,13 @@
  *
  * LEGACY indicated the fields in the legacy __xen_guest string which
  * this a note type replaces.
+ *
+ * String values (for non-legacy) are NULL terminated ASCII, also known
+ * as ASCIZ type.
  */
 
 /*
  * NAME=VALUE pair (string).
- *
- * LEGACY: FEATURES and PAE
  */
 #define XEN_ELFNOTE_INFO   0
 
@@ -137,10 +156,30 @@
 
 /*
  * Whether or not the guest supports cooperative suspend cancellation.
+ * This is a numeric value.
+ *
+ * Default is 0
  */
 #define XEN_ELFNOTE_SUSPEND_CANCEL 14
 
 /*
+ * The (non-default) location the initial phys-to-machine map should be
+ * placed at by the hypervisor (Dom0) or the tools (DomU).
+ * The kernel must be prepared for this mapping to be established using
+ * large pages, despite such otherwise not being available to guests.
+ * The kernel must also be able to handle the page table pages used for
+ * this mapping not being accessible through the initial mapping.
+ * (Only x86-64 supports this at present.)
+ */
+#define XEN_ELFNOTE_INIT_P2M  15
+
+/*
+ * Whether or not the guest can deal with being passed an initrd not
+ * mapped through its initial page tables.
+ */
+#define XEN_ELFNOTE_MOD_START_PFN 16
+
+/*
  * The features supported by this kernel (numeric).
  *
  * Other than XEN_ELFNOTE_FEATURES on pre-4.2 Xen, this note allows a
@@ -153,6 +192,65 @@
  */
 #define XEN_ELFNOTE_SUPPORTED_FEATURES 17
 
+/*
+ * The number of the highest elfnote defined.
+ */
+#define XEN_ELFNOTE_MAX XEN_ELFNOTE_SUPPORTED_FEATURES
+
+/*
+ * System information exported through crash notes.
+ *
+ * The kexec / kdump code will create one XEN_ELFNOTE_CRASH_INFO
+ * note in case of a system crash. This note will contain various
+ * information about the system, see xen/include/xen/elfcore.h.
+ */
+#define XEN_ELFNOTE_CRASH_INFO 0x101
+
+/*
+ * System registers exported through crash notes.
+ *
+ * The kexec / kdump code will create one XEN_ELFNOTE_CRASH_REGS
+ * note per cpu in case of a system crash. This note is architecture
+ * specific and will contain registers not saved in the CORE note.
+ * See xen/include/xen/elfcore.h for more information.
+ */
+#define XEN_ELFNOTE_CRASH_REGS 0x102
+
+
+/*
+ * xen dump-core none note.
+ * xm dump-core code will create one XEN_ELFNOTE_DUMPCORE_NONE
+ * in its dump file to indicate that the file is xen dump-core
+ * file. This note doesn't have any other information.
+ * See tools/libxc/xc_core.h for more information.
+ */
+#define XEN_ELFNOTE_DUMPCORE_NONE   0x200
+
+/*
+ * xen dump-core header note.
+ * xm dump-core code will create one XEN_ELFNOTE_DUMPCORE_HEADER
+ * in its dump file.
+ * See tools/libxc/xc_core.h for more information.
+ */
+#define XEN_ELFNOTE_DUMPCORE_HEADER 0x201
+
+/*
+ * xen dump-core xen version note.
+ * xm dump-core code will create one XEN_ELFNOTE_DUMPCORE_XEN_VERSION
+ * in its dump file. It contains the xen version obtained via the
+ * XENVER hypercall.
+ * See tools/libxc/xc_core.h for more information.
+ */
+#define 

Re: [PATCH 1/3] xen: sync some headers with xen tree

2014-09-04 Thread Jan Beulich
 On 04.09.14 at 14:38, jgr...@suse.com.non-mime.internet wrote:
 As the KEXEC and DUMPCORE related ELFNOTES are not relevant for the
 kernel they are omitted from elfnote.h.

But the defines are still in the patch:

 @@ -153,6 +192,65 @@
   */
  #define XEN_ELFNOTE_SUPPORTED_FEATURES 17
  
 +/*
 + * The number of the highest elfnote defined.
 + */
 +#define XEN_ELFNOTE_MAX XEN_ELFNOTE_SUPPORTED_FEATURES
 +
 +/*
 + * System information exported through crash notes.
 + *
 + * The kexec / kdump code will create one XEN_ELFNOTE_CRASH_INFO
 + * note in case of a system crash. This note will contain various
 + * information about the system, see xen/include/xen/elfcore.h.
 + */
 +#define XEN_ELFNOTE_CRASH_INFO 0x101
 +
 +/*
 + * System registers exported through crash notes.
 + *
 + * The kexec / kdump code will create one XEN_ELFNOTE_CRASH_REGS
 + * note per cpu in case of a system crash. This note is architecture
 + * specific and will contain registers not saved in the CORE note.
 + * See xen/include/xen/elfcore.h for more information.
 + */
 +#define XEN_ELFNOTE_CRASH_REGS 0x102
 +
 +
 +/*
 + * xen dump-core none note.
 + * xm dump-core code will create one XEN_ELFNOTE_DUMPCORE_NONE
 + * in its dump file to indicate that the file is xen dump-core
 + * file. This note doesn't have any other information.
 + * See tools/libxc/xc_core.h for more information.
 + */
 +#define XEN_ELFNOTE_DUMPCORE_NONE   0x200
 +
 +/*
 + * xen dump-core header note.
 + * xm dump-core code will create one XEN_ELFNOTE_DUMPCORE_HEADER
 + * in its dump file.
 + * See tools/libxc/xc_core.h for more information.
 + */
 +#define XEN_ELFNOTE_DUMPCORE_HEADER 0x201
 +
 +/*
 + * xen dump-core xen version note.
 + * xm dump-core code will create one XEN_ELFNOTE_DUMPCORE_XEN_VERSION
 + * in its dump file. It contains the xen version obtained via the
 + * XENVER hypercall.
 + * See tools/libxc/xc_core.h for more information.
 + */
 +#define XEN_ELFNOTE_DUMPCORE_XEN_VERSION0x202
 +
 +/*
 + * xen dump-core format version note.
 + * xm dump-core code will create one XEN_ELFNOTE_DUMPCORE_FORMAT_VERSION
 + * in its dump file. It contains a format version identifier.
 + * See tools/libxc/xc_core.h for more information.
 + */
 +#define XEN_ELFNOTE_DUMPCORE_FORMAT_VERSION 0x203
 +
  #endif /* __XEN_PUBLIC_ELFNOTE_H__ */
  
  /*

Jan

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