From: Eric DeVolder <eric.devolder@oracle.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: elena.ufimtseva@oracle.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 12:02:49 -0600 [thread overview]
Message-ID: <b2c64cde-d0e4-c8a9-ba70-c1774b072547@oracle.com> (raw)
In-Reply-To: <20170118174753.GE5089@citrix.com>
On 01/18/2017 11:47 AM, Wei Liu wrote:
> 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.
>
Wei,
I just sent those, subject line 'Followup corrections to kexec STATUS'
eric
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-01-18 18:02 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
2017-01-18 18:02 ` Eric DeVolder [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=b2c64cde-d0e4-c8a9-ba70-c1774b072547@oracle.com \
--to=eric.devolder@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=daniel.kiper@oracle.com \
--cc=elena.ufimtseva@oracle.com \
--cc=ian.jackson@eu.citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=wei.liu2@citrix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).