From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Hoyer, David" <David.Hoyer@netapp.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen supported LAPIC features
Date: Tue, 8 Oct 2013 20:12:36 +0100 [thread overview]
Message-ID: <52545924.3080209@citrix.com> (raw)
In-Reply-To: <6777CD901FD53644B082307CD745FB83269D898A@SACEXCMBX02-PRD.hq.netapp.com>
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
next prev parent reply other threads:[~2013-10-08 19:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 19:03 Xen supported LAPIC features Hoyer, David
2013-10-08 19:12 ` Andrew Cooper [this message]
2013-10-08 19:37 ` Hoyer, David
2013-10-08 20:33 ` Andrew Cooper
2013-10-09 14:04 ` Hoyer, David
2013-10-09 14:11 ` Andrew Cooper
2013-10-09 15:55 ` Hoyer, David
2013-10-25 19:45 ` Hoyer, David
2013-10-26 0:19 ` Andrew Cooper
2013-10-26 14:36 ` Hoyer, David
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52545924.3080209@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=David.Hoyer@netapp.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).