From: Pratyush Anand <panand@redhat.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
david.vrabel@citrix.com, xen-devel@lists.xenproject.org,
kexec@lists.infradead.org
Cc: elena.ufimtseva@oracle.com, daniel.kiper@oracle.com
Subject: Re: [PATCH v1] Add in kexec -S for status, and add new Xen hypercall to support this.
Date: Tue, 15 Nov 2016 10:18:02 +0530 [thread overview]
Message-ID: <08458dc9-bb87-2e0d-0a45-0526e186b125@redhat.com> (raw)
In-Reply-To: <1479161573-12671-1-git-send-email-konrad.wilk@oracle.com>
On Tuesday 15 November 2016 03:42 AM, Konrad Rzeszutek Wilk wrote:
> Heya!
>
> I am cross-posting on two mailing lists:
> xen-devel@lists.xenproject.org
> kexec@lists.infradead.org
>
> as it may be easier to review and provide input then me going back and forth.
Hummmm..its confusing infact. Patch 1/2 does not belong to kexec-tools
repository. patch 2/2 is independent in itself, so send 2/2 individually
to kexec list and once it is getting acked, you can send only 1/2 to
xen-devel list.
>
> Anyhow the patches are to help with the various distro's poking in
> /sys/../kexec to figure out whether an kexec image is loaded.
>
> This can be done using the -S parameter now with the patch #2.
>
> Also I add an hypercall to Xen so that if kexec is running under Xen
> the same information can be retrieved (see patch #1).
~Pratyush
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2016-11-15 4:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 22:12 [PATCH v1] Add in kexec -S for status, and add new Xen hypercall to support this Konrad Rzeszutek Wilk
2016-11-14 22:12 ` [PATCH v1 1/2] xen/kexec: Find out whether an kexec type is loaded Konrad Rzeszutek Wilk
2016-11-15 9:36 ` Daniel Kiper
2016-11-15 10:51 ` David Vrabel
2016-11-14 22:12 ` [PATCH v1 2/2] kexec: Support -S paramter to return whether the kexec payload " Konrad Rzeszutek Wilk
2016-11-15 4:44 ` Pratyush Anand
2016-11-16 12:50 ` Simon Horman
2016-11-15 4:48 ` Pratyush Anand [this message]
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=08458dc9-bb87-2e0d-0a45-0526e186b125@redhat.com \
--to=panand@redhat.com \
--cc=daniel.kiper@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=elena.ufimtseva@oracle.com \
--cc=kexec@lists.infradead.org \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xenproject.org \
/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