All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: andreas.tanz@kvt.de
Cc: kvm@vger.kernel.org
Subject: Re: KVM on Via Nano (Isaiah) CPUs? <Virus checked>
Date: Thu, 19 Mar 2009 17:48:49 +0200	[thread overview]
Message-ID: <49C26961.6080002@redhat.com> (raw)
In-Reply-To: <200903191634.47628.andreas.tanz@kvt.de>

Andreas Tanz wrote:
> i modded handle_exception as you said : 
>
> 2711         printk(KERN_ERR "vmx->handle_exception 0f : vcpu->arch.rmode.active: 0x%x\n",vcpu->arch.rmode.active);
> 2712         int debug_handle_rmode_exception = handle_rmode_exception(vcpu, intr_info & INTR_INFO_VECTOR_MASK, error_code);
> 2713         printk(KERN_ERR "vmx->handle_exception 10 : handle_rmode_exception(vcpu, intr_info & INTR_INFO_VECTOR_MASK, error_code) returned 0x%x\n", debug_handle_rmode_exception
> 2714         if (vcpu->arch.rmode.active &&  debug_handle_rmode_exception) {
>   

This bit is broken.  The original code:

    if (vcpu->arch.rmode.active &&
        handle_rmode_exception(vcpu, intr_info & INTR_INFO_VECTOR_MASK,
                                error_code)) {

Only executes handle_rmode_exception() if rmode.active is true.  Your 
code executes it unconditionally.

You can write it as

    if (vcpu->arch.rmode.active &&
        (retval = handle_rmode_exception(vcpu, intr_info & 
INTR_INFO_VECTOR_MASK,
                                error_code))) {


Please check for other cases as well.  As it happens, the guest crashed 
immediately after entering protected mode (so rmode.active became false, 
triggering the bug).

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2009-03-19 15:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200903180902.29139.andreas.tanz@kvt.de>
     [not found] ` <200903181810.48603.andreas.tanz@kvt.de>
     [not found]   ` <49C20DEE.9040302@redhat.com>
2009-03-19 10:55     ` KVM on Via Nano (Isaiah) CPUs? <Virus checked> Andreas Tanz
2009-03-19 12:25       ` Avi Kivity
2009-03-19 15:10         ` Andreas Tanz
2009-03-19 15:19           ` Avi Kivity
2009-03-19 15:34             ` Andreas Tanz
2009-03-19 15:48               ` Avi Kivity [this message]
2009-03-19 17:05                 ` Andreas Tanz
2009-03-19 17:20                   ` Avi Kivity
2009-03-20 12:37                     ` Andreas Tanz
2009-03-22  8:53                       ` Avi Kivity
2009-03-22  9:03                     ` Avi Kivity
2009-03-23 13:39                       ` Andreas Tanz
2009-03-23 14:08                         ` Avi Kivity
2009-03-23 17:33                           ` Andreas Tanz
2009-03-23 18:41                             ` Avi Kivity
2009-03-23 20:36                               ` Avi Kivity
2009-03-25  9:45                                 ` Andreas Tanz
2009-03-23 18:50                             ` [PATCH] mm/memory.c:unmap_vmas(): fix NULL * deref john cooper
2009-05-08 19:16 KVM on Via Nano (Isaiah) CPUs? Craig Metz
2009-05-09  9:32 ` Avi Kivity
2009-05-12  6:48   ` KVM on Via Nano (Isaiah) CPUs? <Virus checked> Andreas Tanz
2009-05-12  6:50     ` 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=49C26961.6080002@redhat.com \
    --to=avi@redhat.com \
    --cc=andreas.tanz@kvt.de \
    --cc=kvm@vger.kernel.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 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.