xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
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: Wed, 9 Oct 2013 15:11:17 +0100	[thread overview]
Message-ID: <52556405.7070604@citrix.com> (raw)
In-Reply-To: <6777CD901FD53644B082307CD745FB83269D9B23@SACEXCMBX02-PRD.hq.netapp.com>

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

  reply	other threads:[~2013-10-09 14:11 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
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 [this message]
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=52556405.7070604@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).