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-devel

RE: [Xen-devel] domains not shutting down properly-theproblemisbackagain

To: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>, "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] domains not shutting down properly-theproblemisbackagain
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Sat, 3 Jan 2009 13:25:22 +1100
Cc:
Delivery-date: Fri, 02 Jan 2009 18:25:57 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D01550178@trantor>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AEC6C66638C05B468B556EA548C1A77D01550177@trantor><C583E3EB.20ADF%keir.fraser@xxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D01550178@trantor>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AclsEUiDJwnrGfQLQ6G5Bsw4GM+wzgAAL2RgAAIdJkkAHEzXYAAA9a8QAAD1UUAACaHcAAABmirxAAEexXAAAH2McAAAGpUAAAH94BAAAdTsvgABrLdgAASGj2IAE4Rj0AADO+3w
Thread-topic: [Xen-devel] domains not shutting down properly-theproblemisbackagain
> My dom0 kernel is http://xenbits.xensource.com/linux-2.6.18-xen.hg
> 
> The crash I had last night was just:
> 
> "
> void send_guest_global_virq(struct domain *d, int virq)
> {
>     unsigned long flags;
>     int port;
>     struct vcpu *v;
>     struct evtchn *chn;
> 
>     ASSERT(virq_is_global(virq));
> 
> if (virq == VIRQ_DOM_EXC)
>   printk("send_guest_global_virq\n");
> "
> 
> adding the last two lines above. There should be no reason for that to
> cause a crash that I can see, but as soon as I take those lines away
it
> all works. I have printk's in the function that calls
> send_guest_global_virq and they work just fine.

It turns out it wasn't those two lines, it was a debug statement a bit
further down, just after " port = v->virq_to_evtchn[virq];", with
v->virq_lock held. I'm guessing that printk can't execute with virq_lock
held?

So no crash anymore but the event isn't getting through...

James


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

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