[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: Thu, 2 Mar 2006 00:19:53 +0000
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 02 Mar 2006 00:20:27 +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=qmep43NuSQzjWQnu62745gKSM8xda81uyNvXDFq4f2VzPa2kuNJFydwPHpDaex/mNg6xfdt9EkNjvkx+NSapvqpG9go/FQul36BbwWJUUhGKVPmeUpyM3J27BoDvx67eOwoeIKOqp0b/pO92+Uy95q0PAgCThVOqoCqSbf6al48=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Problem solved and I am rather annoyed. When porting XEN_BLOCK_EVENTS
and XEN_UNBLOCK_EVENTS macros, i had removed the 'b' from movb
assuming it was an at&t asm thing, like the l on movl. silly mistake,
and i shall paddle myself sufficiently for it.
Thanks for all yer help,

On 3/1/06, Ivan Kelly <ivanbkelly@xxxxxxxxx> wrote:
> > 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 :/
> -ivan

Xen-devel mailing list



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