From: Kevin Wolf <kwolf@suse.de>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [RESENT][PATCH 2/2] x86: Issue reset on triple faults
Date: Tue, 24 Jun 2008 10:18:40 +0200 [thread overview]
Message-ID: <4860ADE0.2030305@suse.de> (raw)
In-Reply-To: <485FC2BC.3040503@siemens.com>
Jan Kiszka schrieb:
> Jamie Lokier wrote:
>> It might be worth distinguishing between
>> triple-fault-used-by-guest-for-context-switch and triple faults which
>> trigger a normal reset, and log only the latter. There's a
>> standardish way of distinguishing them, which the BIOS should check.
Well, that's certainly possible somehow. But then you need to rename the
cpu_reset option to cpu_resets_suspected_to_be_errors. Let's keep it
simple and just log all of them.
>>> +#if !defined(CONFIG_USER_ONLY)
>>> + if (env->old_exception == EXCP08_DBLE) {
>>> + if (env->hflags & HF_SVMI_MASK)
>>> + helper_vmexit(SVM_EXIT_SHUTDOWN, 0);
>>> +
>>> + if (loglevel & CPU_LOG_RESET)
>>> + fprintf(logfile, "Triple fault\n");
>>> +
>>> + qemu_system_reset_request();
>>> + return EXCP_HLT;
>>> + }
>>> +#endif
>> When helper(SVM_EXIT_SHUTDOWN, 0) is called, should it still also call
>> qemu_system_reset_request()?
>
> helper_vmexit() is not expected to return (cpu_loop_exit).
Maybe a comment then?
Kevin
prev parent reply other threads:[~2008-06-24 8:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 15:15 [Qemu-devel] [RESENT][PATCH 2/2] x86: Issue reset on triple faults Jan Kiszka
2008-06-23 15:23 ` Jamie Lokier
2008-06-23 15:35 ` [Qemu-devel] " Jan Kiszka
2008-06-23 16:00 ` Jamie Lokier
2008-06-23 20:01 ` Natalia Portillo
2008-06-24 6:39 ` Jan Kiszka
2008-06-24 8:18 ` Kevin Wolf [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=4860ADE0.2030305@suse.de \
--to=kwolf@suse.de \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.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).