From: Keir Fraser <keir@xen.org>
To: Ian Campbell <Ian.Campbell@citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Jan Beulich <JBeulich@suse.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH RFC] hvm: Allow triple fault to imply crash rather than reboot
Date: Mon, 04 Feb 2013 16:46:30 +0000 [thread overview]
Message-ID: <CD359666.59FAD%keir@xen.org> (raw)
In-Reply-To: <1359991569.7743.60.camel@zakaz.uk.xensource.com>
On 04/02/2013 15:26, "Ian Campbell" <Ian.Campbell@citrix.com> wrote:
> On Mon, 2013-02-04 at 14:25 +0000, Andrew Cooper wrote:
>> While the triple fault action on native hardware will result in a system
>> reset, any modern operating system can and will make use of less violent
>> reboot methods. As a result, the most likely cause of a triple fault is a
>> fatal software bug.
>>
>> This patch allows the toolstack to indicate that a triple fault should mean a
>> crash rather than a reboot. The default of reboot still remains the same.
>
> Just a random thought -- what about adding SHUTDOWN_triple_fault as an
> explicit thing, then the toolstack can decide what to do?
I kind of prefer that, although it will require changes to every toolstack.
An alternative would be to do that, *and* still have the new HVM_PARAM, so
that any SHUTDOWN_* code can be generated by a triple fault (including new
SHUTDOWN_triple_fault) -- but defaulting to SHUTDOWN_reboot so that the
default behaviour is still unchanged.
Or, in any case, I'm not dead against the existing patch, it just seems less
flexible than it could be. But maybe that flexibility is pointless.
-- Keir
>> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
>>
>> diff -r 5af4f2ab06f3 -r 6f8c532df545 xen/arch/x86/hvm/hvm.c
>> --- a/xen/arch/x86/hvm/hvm.c
>> +++ b/xen/arch/x86/hvm/hvm.c
>> @@ -1233,9 +1233,14 @@ void hvm_hlt(unsigned long rflags)
>> void hvm_triple_fault(void)
>> {
>> struct vcpu *v = current;
>> + struct domain * d = v->domain;
>> + u8 reason = d->arch.hvm_domain.params[HVM_PARAM_TRIPLE_FAULT_CRASH]
>> + ? SHUTDOWN_crash : SHUTDOWN_reboot;
>> +
>> gdprintk(XENLOG_INFO, "Triple fault on VCPU%d - "
>> - "invoking HVM system reset.\n", v->vcpu_id);
>> - domain_shutdown(v->domain, SHUTDOWN_reboot);
>> + "invoking HVM system %s.\n", v->vcpu_id,
>> + reason == SHUTDOWN_crash ? "crash" : "reboot");
>> + domain_shutdown(v->domain, reason);
>> }
>>
>> void hvm_inject_trap(struct hvm_trap *trap)
>> diff -r 5af4f2ab06f3 -r 6f8c532df545 xen/include/public/hvm/params.h
>> --- a/xen/include/public/hvm/params.h
>> +++ b/xen/include/public/hvm/params.h
>> @@ -142,6 +142,9 @@
>> #define HVM_PARAM_ACCESS_RING_PFN 28
>> #define HVM_PARAM_SHARING_RING_PFN 29
>>
>> -#define HVM_NR_PARAMS 31
>> +/* Boolean: Should a triple fault imply crash rather than reboot? */
>> +#define HVM_PARAM_TRIPLE_FAULT_CRASH 31
>> +
>> +#define HVM_NR_PARAMS 32
>>
>> #endif /* __XEN_PUBLIC_HVM_PARAMS_H__ */
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel
>
>
next prev parent reply other threads:[~2013-02-04 16:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 14:25 [PATCH RFC] hvm: Allow triple fault to imply crash rather than reboot Andrew Cooper
2013-02-04 14:46 ` Jan Beulich
2013-02-04 14:50 ` Andrew Cooper
2013-02-04 15:26 ` Ian Campbell
2013-02-04 16:46 ` Keir Fraser [this message]
2013-02-04 17:12 ` Andrew Cooper
2013-02-04 17:55 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2016-11-07 12:56 Xuquan (Quan Xu)
2016-11-07 13:12 ` Andrew Cooper
2016-11-07 13:18 ` Xuquan (Quan Xu)
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=CD359666.59FAD%keir@xen.org \
--to=keir@xen.org \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@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).