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] context switch bug ?

To: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-ia64-devel] context switch bug ?
From: Tristan Gingold <Tristan.Gingold@xxxxxxxx>
Date: Tue, 27 Sep 2005 12:52:08 +0200
Delivery-date: Tue, 27 Sep 2005 09:47:33 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <200509271005.33926.Tristan.Gingold@xxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
References: <516F50407E01324991DD6D07B0531AD572E602@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <200509271005.33926.Tristan.Gingold@xxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.5
> > I'm not sure if I'm misunderstanding, but the line
> > that is between context_switch and context_switch_finalize
> > is spin_UNLOCK_irq, which releases the lock, correct?
>
> Sure, but this is not run in the next domain, since a switch has just
> occured!

Sorry, I was not clear enough.  This is not true when a domain is started.

Tristan.

> > > Hi,
> > >
> > > while working on SMP, I think I hit a problem which may
> > > require a local
> > > redesign in context switching.
> > >
> > > In common/schedule.c(__enter_scheduler), the last lines are:
> > >
> > >     context_switch(prev, next);
> > >
> > >     spin_unlock_irq(&schedule_data[cpu].schedule_lock);
> > >
> > >     context_switch_finalise(next);
> > > }
> > >
> > > Unfortunatly, on ia64, context_switch does all the work and
> > > context_switch_finalise does nothing.  Therefore, the cpu-spin lock is
> > > still taken when the domain runs [even with one cpu].
> > > It is correct ?
> > >
> > > I will try to fix this issue tomorrow, and I will look on x86
> > > code.  However,
> > > if anymore has already think about this issue, please share!


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

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