All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Tanz <andreas.tanz@kvt.de>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: KVM on Via Nano (Isaiah) CPUs? <Virus checked>
Date: Fri, 20 Mar 2009 13:37:49 +0100	[thread overview]
Message-ID: <200903201337.49355.andreas.tanz@kvt.de> (raw)
In-Reply-To: <49C27EC0.1090108@redhat.com>

Am 19.03.2009 schrieb Avi Kivity:
> > [101324.097968] vmx->handle_exception 00 : giving some infos
> > [101324.097973] vmx->handle_exception 01 : vect_info: 0x0
> > [101324.097978] vmx->handle_exception 02 : intr_info: 0x80000b0d, is_page_fault()==0
> > [101324.097983] vmx->handle_exception 03 : irq_chip_in_kernel()==1
> > [101324.097988] vmx->handle_exception 04 : is_external_interrupt()==0
> > [101324.097993] vmx->handle_exception 0a : kvm_rip_read(vcpu) returned 0x3154
> > [101324.097998] vmx->handle_exception 0f : vcpu->arch.rmode.active: 0x1
> > [101324.098039] vmx->handle_exception 10 : handle_rmode_exception(vcpu, intr_info & INTR_INFO_VECTOR_MASK, error_code) returned 0x1
> > [101324.098050] returning from kvm_handle_exit, cause 3, retval = 1, exit_reason = 0
> > .... until kvm get's killed
> >   
> 
> The code in question is:
> 
>     3152:       fb                      sti   
>     3153:       55                      push   %bp
> 
> *** fault here ***
> 
>     3154:       89 e5                   mov    %sp,%bp
>     3156:       8b 7e 2a                mov    0x2a(%bp),%di
>     3159:       8b 46 28                mov    0x28(%bp),%ax
>     315c:       8b 4e 08                mov    0x8(%bp),%cx
>     315f:       81 ff 00 f8             cmp    $0xf800,%di
> 
> So it looks like we tried to inject the IDE interrupt (that's the first 
> point where it is possible to inject interrupts), but via fails to 
> inject the interrupt for some reason.
> 
> I'll need to think how to debug this further.
> 

Maybe the reason is elsewhere....
I'm unable to build any GCC 4.* (build crashes in stage 2 with a segfault when creating build/genoutput).
I think there are some Nano specific x86-64-quirks gcc doesn't know about...
Further it's impossible to build glibc in multilib mode (x86-64 together with x68-32).
I'll post this in gentoo's bugzilla....
Everything else compiles fine (with precompiled gcc and glibc)

  reply	other threads:[~2009-03-20 12:37 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
2009-03-19 17:05                 ` Andreas Tanz
2009-03-19 17:20                   ` Avi Kivity
2009-03-20 12:37                     ` Andreas Tanz [this message]
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=200903201337.49355.andreas.tanz@kvt.de \
    --to=andreas.tanz@kvt.de \
    --cc=avi@redhat.com \
    --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.