From: "Jan Beulich" <JBeulich@suse.com>
To: "Juergen Gross" <JGross@suse.com>
Cc: <david.vrabel@citrix.com>, <xen-devel@lists.xensource.com>,
<boris.ostrovsky@oracle.com>, <konrad.wilk@oracle.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] xen: sync some headers with xen tree
Date: Thu, 04 Sep 2014 13:52:30 +0100 [thread overview]
Message-ID: <54087CAE0200007800030D79@mail.emea.novell.com> (raw)
In-Reply-To: <1409834326-29287-2-git-send-email-jgross@suse.com>
>>> On 04.09.14 at 14:38, <"jgross@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 0x1000001
> +
> +/*
> + * 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 0x1000002
> +
> +
> +/*
> + * 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 0x2000000
> +
> +/*
> + * 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 0x2000001
> +
> +/*
> + * 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_VERSION 0x2000002
> +
> +/*
> + * 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 0x2000003
> +
> #endif /* __XEN_PUBLIC_ELFNOTE_H__ */
>
> /*
Jan
next prev parent reply other threads:[~2014-09-04 12:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 12:38 [PATCH 0/3] xen: remove memory limits from pv-domains Juergen Gross
2014-09-04 12:38 ` [PATCH 1/3] xen: sync some headers with xen tree Juergen Gross
2014-09-04 12:52 ` Jan Beulich [this message]
2014-09-05 8:06 ` Juergen Gross
2014-09-04 12:38 ` [PATCH 2/3] xen: eliminate scalability issues from initrd handling Juergen Gross
2014-09-04 12:52 ` David Vrabel
2014-09-04 14:29 ` Jan Beulich
2014-09-04 14:53 ` [Xen-devel] " David Vrabel
2014-09-05 8:04 ` Juergen Gross
2014-09-04 12:38 ` [PATCH 3/3] xen: eliminate scalability issues from initial mapping setup Juergen Gross
2014-09-04 12:59 ` David Vrabel
2014-09-04 13:02 ` [Xen-devel] " Andrew Cooper
2014-09-04 14:31 ` Jan Beulich
2014-09-04 14:43 ` Andrew Cooper
2014-09-05 7:55 ` Juergen Gross
2014-09-05 9:05 ` Andrew Cooper
2014-09-05 9:44 ` Juergen Gross
2014-09-04 15:13 ` David Vrabel
2014-09-05 8:03 ` Juergen Gross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54087CAE0200007800030D79@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=JGross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®