 Home |
Products |
Support |
Community |
News |
xen-devel
Re: [Xen-devel] Clock Interrupt not occurring. hypervisor_callback not b
| To: | "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [Xen-devel] Clock Interrupt not occurring. hypervisor_callback not being called. (more info) |
| 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= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| In-reply-to: | <eec2a0080603011504r598046c6vd0ff3935f9ea42b8@xxxxxxxxxxxxxx> |
| List-help: | <mailto:xen-devel-request@lists.xensource.com?subject=help> |
| List-id: | Xen developer discussion <xen-devel.lists.xensource.com> |
| List-post: | <mailto:xen-devel@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| References: | <eec2a0080603010817r36679464g2f5edebb09c13aa5@xxxxxxxxxxxxxx> <d174e1d14f1693090c8d70f7159179d2@xxxxxxxxxxxx> <eec2a0080603011504r598046c6vd0ff3935f9ea42b8@xxxxxxxxxxxxxx> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
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, Ivan 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 Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Xen-devel] Re: DomU not rebooting in 3.0.1, Ewan Mellor |
|---|---|
| Next by Date: | RE: [Xen-devel] Help? Red Hat fails, Suse/Debian both work fine, Akio Takebe |
| Previous by Thread: | Re: [Xen-devel] Clock Interrupt not occurring. hypervisor_callback not being called. (more info), Ivan Kelly |
| Next by Thread: | [Xen-devel] [PATCH] USB split driver, Harry Butterworth |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
