[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-ia64-devel] Bug in domain.c:construct_dom0()



Haavard,

I just worked around this in my tree yesterday (are you looking at
getting event channels working too?)... the problem is that shared_info
goes over a page boundary and thereby corrupts the domain structure,
if you reduce MAX_VIRT_CPUS it will fix the problem.

Matt


On Fri, Jun 03, 2005 at 05:42:34PM +0200, Haavard Bjerke wrote:
> In construct_dom0(), the variable d->event_channel[0].state is changed from 1 
> to 0, and this shouldn't happen.
> 
> This happens in these lines:
> 
> /* Mask all upcalls... */
> for ( i = 0; i < MAX_VIRT_CPUS; i++ )
>     d->shared_info->vcpu_data[i].evtchn_upcall_mask = 1;
> 
> 
> Adding this line before and after will show that d->event_channel[0].state is 
> changed:
> 
> printk("construct_dom0(): domain_id: %d, port: %d, state %d\n", d->domain_id, 
> 0, d->event_channel[0].state);
> 
> Note that I haven't pulled for a while, but I will do that shortly and notify 
> if things are better.
> 
> Håvard
> 
> _______________________________________________
> 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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.