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] [PATCH][RFC][TAKE4] the P2M/VP patches

Le Mardi 11 Avril 2006 11:23, Isaku Yamahata a écrit :
> On Tue, Apr 11, 2006 at 09:29:18AM +0100, Tristan Gingold wrote:
> > Le Mardi 11 Avril 2006 03:52, Isaku Yamahata a écrit :
> > > Thank you for testing.
> > >
> > > On Mon, Apr 10, 2006 at 03:52:52PM +0100, Tristan Gingold wrote:
> > > > Le Vendredi 07 Avril 2006 06:16, Isaku Yamahata a écrit :
> > > > > Hello.
> > > > > I attached the P2M/VP model patches take 4 for the change set
> > > > > 9492:2133fb78dba3cf6b6b88d1566fc5cc9de3039f43.
> > > > > Please comments/request/review.
> > > >
> > > > I am testing this on my FAME-C.
> > > > Currently it doesn't work: this is an infinite loop in an mpt driver.
> > > > I will check how it does handle DMA.
> > >
> > > It seems wrong dma address is used.
> > > My test environment is Tiger-2. Mpt driver is used.
> > > I encountered similar case before, but I don't remember clearly.
> >
> > In fact I think it is due to the bug below.
>
> It seems that the IOSAPIC area is not mapped to dom0.
After more reading, there is an inconsistency between memmap and MADT on our 
system!

Thanks,
Tristan.



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

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