From: Jan Kiszka <jan.kiszka@siemens.com>
To: qemu-devel@nongnu.org
Cc: kwolf@suse.de
Subject: [Qemu-devel] Re: [RESENT][PATCH 2/2] x86: Issue reset on triple faults
Date: Mon, 23 Jun 2008 17:35:24 +0200 [thread overview]
Message-ID: <485FC2BC.3040503@siemens.com> (raw)
In-Reply-To: <20080623152348.GA16375@shareable.org>
Jamie Lokier wrote:
> Jan Kiszka wrote:
>> As discussed a few times on this list: A triple fault causes a system
>> reset on x86, and some guests make use of this. To keep the chance of
>> tracing unexpected resets, log them if CPU_LOG_RESET is set.
>
> 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.
You refer to setting some return address at some magic BIOS location?
Isn't this something the BIOS should handle, not QEMU?
>
>> +#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).
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2008-06-23 15:35 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 ` Jan Kiszka [this message]
2008-06-23 16:00 ` [Qemu-devel] " Jamie Lokier
2008-06-23 20:01 ` Natalia Portillo
2008-06-24 6:39 ` Jan Kiszka
2008-06-24 8:18 ` Kevin Wolf
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=485FC2BC.3040503@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=kwolf@suse.de \
--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).