WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

Re: [Xen-ia64-devel] Re: [PATCH] EFI mapping: avoid vhpt fault.

To: KUWAMURA Shin'ya <kuwa@xxxxxxxxxxxxxx>
Subject: Re: [Xen-ia64-devel] Re: [PATCH] EFI mapping: avoid vhpt fault.
From: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>
Date: Mon, 28 Jul 2008 18:21:10 +0900
Cc: simon@xxxxxxxxxxxxx, xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 28 Jul 2008 02:25:13 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20080728.174804.28799032.kuwa@xxxxxxxxxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20080728081030.GL13209%yamahata@xxxxxxxxxxxxx> <20080728.174804.28799032.kuwa@xxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.6i
On Mon, Jul 28, 2008 at 05:48:04PM +0900, KUWAMURA Shin'ya wrote:
> Hi,
> 
> On <20080728081030.GL13209%yamahata@xxxxxxxxxxxxx>,
>  Isaku Yamahata wrote:
> > 
> > At this moment, I'm not sure whether this patch is related to
> > the PV-on-HVM driver bug you're seeing.
> > Could you please also try this patch?
> 
> The hypervisor still crashes. I attaches the panic message.

Thank you.
I'll take closer look at this issue.

The interesting thing is isr.ni = 1 for all the panic cases.
It looks like that tlb miss occured and wrong value was written to
a register in tlb miss handler. But I'm not sure at this moment.

thanks,

> 
> The source code:
>                 tlbflush_update_time
>                         
> (&prev->domain->arch.last_vcpu[cpu].tlbflush_timestamp,
>                          tlbflush_current_time());
> 
>         if (is_idle_domain(next->domain))
>                 return;
> 
>         last_vcpu_id = next->domain->arch.last_vcpu[cpu].vcpu_id;
>         last_processor = next->arch.last_processor;
> 
>         next->domain->arch.last_vcpu[cpu].vcpu_id = next->vcpu_id;
>         next->arch.last_processor = cpu;
> 
>         if ((last_vcpu_id != next->vcpu_id &&
> f40000000405f0d0:       05 00 00 00 01 c0       [MLX]       nop.m 0x0
> f40000000405f0d6:       7f 00 00 00 00 c0                   movl 
> r22=0x7fffffff;;
> f40000000405f0dc:       f2 f7 ff 67 
> f40000000405f0e0:       19 00 00 00 01 00       [MMB]       nop.m 0x0
> f40000000405f0e6:       e0 00 80 10 20 00                   ld2 r14=[r32]
> f40000000405f0ec:       00 00 00 20                         nop.b 0x0;;
> f40000000405f0f0:       0a 30 38 20 87 38       [MMI]       cmp4.eq 
> p6,p7=r14,r16;;
> 
> Best regards,

> (XEN) ia64_fault, vector=0x18, ifa=0xf00000000433c080, 
> iip=0xf40000000405f0e0, ipsr=0x0000121008226018, isr=0x0000008000000030
> (XEN) General Exception: IA-64 Reserved Register/Field fault (data access).
> (XEN) d 0xf00000000411c080 domid 1
> (XEN) vcpu 0xf0000004f8f90000 vcpu 6
> (XEN) 
> (XEN) CPU 3
> (XEN) psr : 0000121008226018 ifs : 8000000000000710 ip  : [<f40000000405f0e1>]
> (XEN) ip is at flush_vtlb_for_context_switch+0x41/0x330
> (XEN) unat: 0000000000000000 pfs : 0000000000000006 rsc : 0000000000000003
> (XEN) rnat: 0000000000000000 bsps: 0000000000000000 pr  : 00000000a5558597
> (XEN) ldrs: 0000000000000000 ccv : 0000000000000000 fpsr: 0009804c0270033f
> (XEN) csd : 0000000000000000 ssd : 0000000000000000
> (XEN) b0  : f4000000040a6510 b6  : a000000200025100 b7  : 0000000000000000
> (XEN) f6  : 000000000000000000000 f7  : 000000000000000000000
> (XEN) f8  : 000000000000000000000 f9  : 000000000000000000000
> (XEN) f10 : 000000000000000000000 f11 : 000000000000000000000
> (XEN) r1  : a000000200250000 r2  : 0000000000000020 r3  : 0000000000000000
> (XEN) r8  : 0000000000000000 r9  : e000000008ccda70 r10 : 0000000000000000
> (XEN) r11 : a0000001007af3e8 r12 : e000000001dafba0 r13 : e000000001da8000
> (XEN) r14 : 0000000000000000 r15 : 000000000000000e r16 : 0000000000000000
> (XEN) r17 : 0000000000000000 r18 : 0000000000000000 r19 : 0000000000000000
> (XEN) r20 : 0000000000000000 r21 : 0000000000000000 r22 : 0000000000000000
> (XEN) r23 : 0000000000000000 r24 : 0000000000000000 r25 : 0000000000000000
> (XEN) r26 : 0000000000000000 r27 : 0000000000000000 r28 : 0000000000000000
> (XEN) r29 : 0000000000000000 r30 : 0000000000000000 r31 : 0000000000000000
> (XEN) 
> (XEN) Call Trace:
> (XEN)  [<f4000000040cbb50>] show_stack+0x80/0xa0
> (XEN)                                 sp=f0000004f8f916f0 bsp=f0000004f8f916d0
> (XEN)  [<f40000000408bce0>] ia64_fault+0x120/0x670
> (XEN)                                 sp=f0000004f8f918c0 bsp=f0000004f8f91698
> (XEN)  [<f4000000040c4300>] ia64_leave_kernel+0x0/0x300
> (XEN)                                 sp=f0000004f8f918c0 bsp=f0000004f8f91698
> (XEN) 
> (XEN) ****************************************
> (XEN) Panic on CPU 3:
> (XEN) Fault in Xen.
> (XEN) ****************************************
> (XEN) 
> (XEN) Reboot in five seconds...

> _______________________________________________
> Xen-ia64-devel mailing list
> Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-ia64-devel

-- 
yamahata

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel

<Prev in Thread] Current Thread [Next in Thread>