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

Re: [Xen-devel] Clock Interrupt not occurring. hypervisor_callback not being called. (more info)

  • To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
  • From: "Ivan Kelly" <ivanbkelly@xxxxxxxxx>
  • Date: Wed, 1 Mar 2006 23:04:43 +0000
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 01 Mar 2006 23:05:11 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=X4q1NvKWY8N3RqxS1Nxt1jG4tvsQ1XLrAlOsn1Ql+U1JOlCaMy+PIgsMgDO3zKHzfQkR9awY9EvnqtfhWGEcorNwJa7TeX/vzBppQkivN+DYBMuWC85Bs6QYErnNBYZ3w6NN1N6Y6gX/MNN5p/IeM04mgl0nmwSUDqaLvGpGruU=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

> This is certainly not happening or I think it would have been
> discovered and fixed by now. :-)
Im developing on 2.0.7. Could such a thing have existed back then? in
any case, it's something im doing wrong.
> When processing an upcall, you should clear bits in the opposite order.
This is the order i am clearing them in. It looks to me like upcall is
being called with no event_pending bit set, though i doubt this could
even be possible. maybe im clearing the bit accidently :/

Xen-devel mailing list



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