From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: Xen supported LAPIC features Date: Wed, 9 Oct 2013 15:11:17 +0100 Message-ID: <52556405.7070604@citrix.com> References: <6777CD901FD53644B082307CD745FB83269D898A@SACEXCMBX02-PRD.hq.netapp.com> <52545924.3080209@citrix.com> <6777CD901FD53644B082307CD745FB83269D8A2C@SACEXCMBX02-PRD.hq.netapp.com> <52546C10.8020503@citrix.com> <6777CD901FD53644B082307CD745FB83269D9B23@SACEXCMBX02-PRD.hq.netapp.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <6777CD901FD53644B082307CD745FB83269D9B23@SACEXCMBX02-PRD.hq.netapp.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: "Hoyer, David" Cc: "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org 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? ~Andrew