RE: [Xen-ia64-devel] Changes to virq/irq interface in xen-unstable

["Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>]

In case you can't find one, here's an rpm.

ftp://ftp.hpl.hp.com/pub/xen-ia64/udev-058-1.ia64.rpm

> -----Original Message-----
> From: Magenheimer, Dan (HP Labs Fort Collins) 
> Sent: Tuesday, November 08, 2005 9:43 PM
> To: 'Tian, Kevin'; xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-ia64-devel] Changes to virq/irq interface 
> in xen-unstable
> 
> > I'm still stuck on the environmental issue related 
> > possibly to udev or hotplug, which preventing "xm create"
> 
> Not sure if you saw this, which looks like a similar problem. 
> 
> http://lists.xensource.com/archives/html/xen-devel/2005-11/msg
> 00326.html 
> 
> If it is udev-related, maybe try installing a recent version
> of udev and rebooting?
> 
> 
> > -----Original Message-----
> > From: Tian, Kevin [mailto:kevin.tian@xxxxxxxxx] 
> > Sent: Tuesday, November 08, 2005 7:35 PM
> > To: Magenheimer, Dan (HP Labs Fort Collins); 
> > xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> > Subject: RE: [Xen-ia64-devel] Changes to virq/irq interface 
> > in xen-unstable
> > 
> > Yes, not many changes required for ia64 and some simple stubs 
> > are enough. Actually that's a good way to go. However 
> > currently I'm still stuck on the environmental issue related 
> > possibly to udev or hotplug, which preventing "xm create" 
> > executed correctly. Hope other guys interested in this issue 
> > can also make a try to see how quick we can solve it easily. 
> > ;-) Once it's solved, we can adapt to Keir's changes and then test.
> > 
> > Thanks,
> > Kevin
> > >-----Original Message-----
> > >From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
> > >[mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On 
> > Behalf Of Magenheimer,
> > >Dan (HP Labs Fort Collins)
> > >Sent: 2005å11æ9æ 1:33
> > >To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> > >Subject: [Xen-ia64-devel] Changes to virq/irq interface in 
> > xen-unstable
> > >
> > >Kevin, would you take a look at this?  The changes are
> > >probably not hard, but until multiple domains is up on
> > >tip, I can't test and don't want to break your work.
> > >
> > >Keir's changes are in xen-unstable cset 7699.
> > >
> > >Dan
> > >
> > >> -----Original Message-----
> > >> From: Keir Fraser [mailto:Keir.Fraser@xxxxxxxxxxxx]
> > >> Sent: Tuesday, November 08, 2005 8:08 AM
> > >> To: Magenheimer, Dan (HP Labs Fort Collins)
> > >> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> > >> Subject: Re: Please pull xen-ia64-unstable
> > >>
> > >>
> > >> On 7 Nov 2005, at 18:45, Magenheimer, Dan (HP Labs Fort
> > >> Collins) wrote:
> > >>
> > >> > Please pull
> > >> >
> > >> > http://xenbits.xensource.com/ext/xen-ia64-unstable.hg
> > >> >
> > >> > Merged up thru xen-unstable cset 7642.
> > >>
> > >> Okay, pulled through. I noticed that the event-channel
> > >> interfaces still
> > >> cause problems (bind_virq_to_irq in particular). I've had
> > >> another go at
> > >> rationalising the binding interface in light of this, so 
> > you now need
> > >> to implement:
> > >>   bind_evtchn_to_irq --- same as it ever was
> > >>   bind_virq_to_irqhandler --- replaces bind_virq_to_irq
> > >>   bind_ipi_to_irqhandler --- replaces bind_ipi_to_irq
> > >>   unbind_from_irqhandler --- common unbind function that replaces
> > >> unbind_evtchn_from_irqhandler, unbind_virq_from_irq and
> > >> unbind_ipi_from_irq
> > >>
> > >> This interface eliminates all evtchn-related ia64 ifdefs in
> > >> common code.
> > >>
> > >>   -- Keir
> > >>
> > >
> > >
> > >> -----Original Message-----
> > >> From: Keir Fraser [mailto:Keir.Fraser@xxxxxxxxxxxx]
> > >> Sent: Tuesday, November 08, 2005 8:48 AM
> > >> To: Magenheimer, Dan (HP Labs Fort Collins)
> > >> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> > >> Subject: Re: Please pull xen-ia64-unstable
> > >>
> > >>
> > >> On 8 Nov 2005, at 15:41, Magenheimer, Dan (HP Labs Fort
> > >> Collins) wrote:
> > >>
> > >> > Great, thanks!  Are these new interfaces checked into
> > >> > xen-unstable yet?  I can't find the changeset.
> > >>
> > >> They have to get through our automatic regression tests. 
> > Assuming all
> > >> goes well the changes should be pushed in less than an hour,
> > >>
> > >>   -- Keir
> > >>
> > >>
> > >
> > >_______________________________________________
> > >Xen-ia64-devel mailing list
> > >Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> > >http://lists.xensource.com/xen-ia64-devel
> > 
> 

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