From: Avi Kivity <avi@qumranet.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: [PATCH] x86: handle double and triple faults for every exception
Date: Wed, 30 Apr 2008 12:51:04 +0300 [thread overview]
Message-ID: <48184108.7050000@qumranet.com> (raw)
In-Reply-To: <48183198.1050508@siemens.com>
Jan Kiszka wrote:
> Joerg Roedel wrote:
>
>> The current KVM x86 exception code handles double and triple faults only for
>> page fault exceptions. This patch extends this detection for every exception
>> that gets queued for the guest.
>>
>> Signed-off-by: Joerg Roedel <joerg.roedel@amd.com>
>> Cc: Jan Kiszka <jan.kiszka@siemens.com>
>> ---
>> arch/x86/kvm/x86.c | 31 +++++++++++++++++--------------
>> 1 files changed, 17 insertions(+), 14 deletions(-)
>>
>> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
>> index 578a0c1..c05aa32 100644
>> --- a/arch/x86/kvm/x86.c
>> +++ b/arch/x86/kvm/x86.c
>> @@ -144,9 +144,21 @@ void kvm_set_apic_base(struct kvm_vcpu *vcpu, u64 data)
>> }
>> EXPORT_SYMBOL_GPL(kvm_set_apic_base);
>>
>> +static void handle_multiple_faults(struct kvm_vcpu *vcpu)
>> +{
>> + if (vcpu->arch.exception.nr != DF_VECTOR) {
>> + vcpu->arch.exception.nr = DF_VECTOR;
>> + vcpu->arch.exception.error_code = 0;
>> + } else
>> + set_bit(KVM_REQ_TRIPLE_FAULT, &vcpu->requests);
>> +}
>> +
>> void kvm_queue_exception(struct kvm_vcpu *vcpu, unsigned nr)
>> {
>> - WARN_ON(vcpu->arch.exception.pending);
>> + if (vcpu->arch.exception.pending) {
>> + handle_multiple_faults(vcpu);
>> + return;
>> + }
>> vcpu->arch.exception.pending = true;
>> vcpu->arch.exception.has_error_code = false;
>> vcpu->arch.exception.nr = nr;
>> @@ -157,25 +169,16 @@ void kvm_inject_page_fault(struct kvm_vcpu *vcpu, unsigned long addr,
>> u32 error_code)
>> {
>> ++vcpu->stat.pf_guest;
>> - if (vcpu->arch.exception.pending) {
>> - if (vcpu->arch.exception.nr == PF_VECTOR) {
>> - printk(KERN_DEBUG "kvm: inject_page_fault:"
>> - " double fault 0x%lx\n", addr);
>> - vcpu->arch.exception.nr = DF_VECTOR;
>> - vcpu->arch.exception.error_code = 0;
>> - } else if (vcpu->arch.exception.nr == DF_VECTOR) {
>> - /* triple fault -> shutdown */
>> - set_bit(KVM_REQ_TRIPLE_FAULT, &vcpu->requests);
>> - }
>> - return;
>> - }
>> vcpu->arch.cr2 = addr;
>> kvm_queue_exception_e(vcpu, PF_VECTOR, error_code);
>> }
>>
>> void kvm_queue_exception_e(struct kvm_vcpu *vcpu, unsigned nr, u32 error_code)
>> {
>> - WARN_ON(vcpu->arch.exception.pending);
>> + if (vcpu->arch.exception.pending) {
>> + handle_multiple_faults(vcpu);
>> + return;
>> + }
>> vcpu->arch.exception.pending = true;
>> vcpu->arch.exception.has_error_code = true;
>> vcpu->arch.exception.nr = nr;
>>
>
> And here is an add-on patch to fix reset-on-triple-fault:
>
>
> Clear the pending original exception when raising a triple fault. This
> allows to re-use the vcpu instance, e.g. after a reset which is
> typically issued as reaction on the triple fault.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>
> ---
> arch/x86/kvm/x86.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> Index: b/arch/x86/kvm/x86.c
> ===================================================================
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -149,8 +149,10 @@ static void handle_multiple_faults(struc
> if (vcpu->arch.exception.nr != DF_VECTOR) {
> vcpu->arch.exception.nr = DF_VECTOR;
> vcpu->arch.exception.error_code = 0;
> - } else
> + } else {
> set_bit(KVM_REQ_TRIPLE_FAULT, &vcpu->requests);
> + vcpu->arch.exception.pending = false;
> + }
> }
>
> void kvm_queue_exception(struct kvm_vcpu *vcpu, unsigned nr)
>
>
There's a bigger problem here. The exception queue is hidden state that
qemu and load and save.
--
Any sufficiently difficult bug is indistinguishable from a feature.
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
next prev parent reply other threads:[~2008-04-30 9:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 15:02 [PATCH] x86: handle double and triple faults for every exception Joerg Roedel
2008-04-30 8:45 ` Jan Kiszka
2008-04-30 9:48 ` Joerg Roedel
2008-04-30 9:51 ` Avi Kivity [this message]
2008-04-30 10:42 ` Jan Kiszka
2008-04-30 10:52 ` Avi Kivity
2008-04-30 15:59 ` Jan Kiszka
2008-04-30 17:09 ` Avi Kivity
2008-05-02 11:07 ` Avi Kivity
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=48184108.7050000@qumranet.com \
--to=avi@qumranet.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm-devel@lists.sourceforge.net \
/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.