From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: Xen supported LAPIC features Date: Tue, 8 Oct 2013 20:12:36 +0100 Message-ID: <52545924.3080209@citrix.com> References: <6777CD901FD53644B082307CD745FB83269D898A@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: <6777CD901FD53644B082307CD745FB83269D898A@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 08/10/13 20:03, Hoyer, David wrote: > I am working at getting VxWorks to boot as a guest OS on Xen/Debian as an SMP guest (HVM). I have run into a couple problems that I was hoping could be addressed by this group. None of the other groups seemed to discuss at a low enough level which is why I am starting here. > > I noticed that the LAPIC timer does not seem to be supported by Xen. Is this correct and if so, are there plans of supporting it? VxWorks defaults to LAPIC timer for the system timer so it would be beneficial to have that support in XEN if we are to be able to run with an unmodified VxWorks kernel. > > I also noticed that reading from address 0xfee00020 always returns 0 when it should be returning which core is running. I found a way around that by using a CPUID command but this begs the question of what else is not supported of the LAPIC commands. > > > David Hoyer > Which version of Xen are you running on? That sounds like a broken domain build; both of those should be working. Do you have your domain configuration and boot logs? ~Andrew