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

Re: [Xen-devel] Xen supported LAPIC features

I wanted to follow up on this discussion just so that the community knows what 
I have discovered.

Previously I was running with Xen 4.2.2/Debian(sid) and vxWorks 6.9.3 and was 
having the problems previously described.   Based on some feedback, I decided 
to upgrade to vxWorks (their latest) and ran into some new yet 
different problems.   I debugged it down to an issue with how they were 
terminating early in the MP table scan if the MP tables did not have certain 
information in it.   When I removed the early termination and allowed it to 
resume in spite of this particular data being missing, it suddenly was able to 
boot up successfully using the loapic timer!  I am also no longer getting the 
error message that Andrew pointed out earlier.

Thanks for the help, Andrew.

-----Original Message-----
From: Andrew Cooper [mailto:andrew.cooper3@xxxxxxxxxx] 
Sent: Wednesday, October 09, 2013 9:11 AM
To: Hoyer, David
Cc: xen-devel@xxxxxxxxxxxxx
Subject: Re: [Xen-devel] Xen supported LAPIC features

On 09/10/13 15:04, Hoyer, David wrote:
> That message below only shows up when I kick off my domU (the vxWorks 
> kernel).   I bumped the counter as you mentioned below but that did not help. 
>   It will take awhile to see where the vxWorks kernel might be attempting the 
> register 3 operation on ioapic.  But since this works just fine when I run 
> the vxWorks kernel directly on HW, I am not inclined to believe there is a 
> big problem with the ioapic driver.

On Xen, as well as real hardware, you will read 0xffffffff from that attempted 
access.  Xen is merely also making a note that you have a buggy ioapic driver.  
My point was that, given you definitely have a buggy ioapic driver, are you 
certain you have no bugs in your lapic driver?


Xen-devel mailing list



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