All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Eric DeVolder <eric.devolder@oracle.com>
Cc: elena.ufimtseva@oracle.com, wei.liu2@citrix.com,
	konrad.wilk@oracle.com, andrew.cooper3@citrix.com,
	daniel.kiper@oracle.com, ian.jackson@eu.citrix.com,
	xen-devel@lists.xen.org
Subject: Re: [PATCH v4] kexec: implement STATUS hypercall to check if image is loaded
Date: Wed, 18 Jan 2017 17:47:53 +0000	[thread overview]
Message-ID: <20170118174753.GE5089@citrix.com> (raw)
In-Reply-To: <1484761573-7606-1-git-send-email-eric.devolder@oracle.com>

On Wed, Jan 18, 2017 at 11:46:13AM -0600, Eric DeVolder wrote:
> The tools that use kexec are asynchronous in nature and do not keep
> state changes. As such provide an hypercall to find out whether an
> image has been loaded for either type.
> 
> Note: No need to modify XSM as it has one size fits all check and
> does not check for subcommands.
> 
> Note: No need to check KEXEC_FLAG_IN_PROGRESS (and error out of
> kexec_status()) as this flag is set only once by the first/only
> cpu on the crash path.
> 
> Note: In kexec_status(), the use of test_bit() can also return
> EPERM, so the return value from test_bit() must be checked to
> ensure that kexec_status() always returns 0, 1 or -1, per the
> public header description.
> 
> Note: This is just the Xen side of the hypercall, kexec-tools patch
> to come separately.
> 
> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> Signed-off-by: Eric DeVolder <eric.devolder@oracle.com>

Your v3 is already applied to staging.

Please submit a patch on top of staging branch.

Wei.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-01-18 17:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-18 17:46 [PATCH v4] kexec: implement STATUS hypercall to check if image is loaded Eric DeVolder
2017-01-18 17:47 ` Wei Liu [this message]
2017-01-18 18:02   ` Eric DeVolder

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=20170118174753.GE5089@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=daniel.kiper@oracle.com \
    --cc=elena.ufimtseva@oracle.com \
    --cc=eric.devolder@oracle.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.