All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Patrick Colp <Patrick.Colp@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	"Han, Weidong" <weidong.han@intel.com>,
	Jun Koi <junkoi2004@gmail.com>
Subject: Re: Xen cannot boot with pvops dom0
Date: Tue, 30 Jun 2009 08:12:40 -0700	[thread overview]
Message-ID: <4A4A2B68.7050700@goop.org> (raw)
In-Reply-To: <4A434550.7070500@citrix.com>

On 06/25/09 02:37, Patrick Colp wrote:
> I don't think this is an issue with out the kernel was compiled. In
> fact, all of the ways mentioned will build the pvops kernel properly.
> I have run into a similar problem with the kernel trying to
> add/remove/modify ioapic stuff as well (and have tried to compile the
> kernel in every possible way, but still get the same problem).
>
> I have a feeling it is an issue with the pvops kernel ioapic code and
> have spent some time trying to track it down, but haven't found
> anything yet.

Those messages are just noise, and are harmless.  They're the kernel's
core drivers trying to take over various pieces of important hardware
that Xen already owns.  So far it has just been easier to let the kernel
try and fail to take over the interrupts than to try to suppress the
messages.

    J

  reply	other threads:[~2009-06-30 15:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-25  9:20 Xen cannot boot with pvops dom0 Han, Weidong
2009-06-25  9:29 ` Jun Koi
2009-06-25  9:37   ` Patrick Colp
2009-06-30 15:12     ` Jeremy Fitzhardinge [this message]
2009-07-01  7:32       ` Patrick Colp
2009-07-01 15:39         ` Jeremy Fitzhardinge
2009-07-02  8:01           ` Patrick Colp
2009-07-02 22:47         ` Jeremy Fitzhardinge
2009-07-03  8:09           ` Patrick Colp
2009-06-25  9:39   ` Han, Weidong
2009-06-25  9:46     ` Patrick Colp
2009-06-25  9:53       ` Han, Weidong
2009-06-25 10:02         ` Patrick Colp
2009-06-25 12:08           ` Christian Tramnitz
2009-06-25 15:18             ` Jiang, Yunhong
2009-06-26  9:38               ` Patrick Colp
2009-06-26 13:55                 ` Jiang, Yunhong
2009-06-30 15:10 ` Jeremy Fitzhardinge
2009-07-01  2:43   ` Han, Weidong
2009-07-01  2:58     ` Thomas DuBuisson
     [not found]   ` <715D42877B251141A38726ABF5CABF2C054570DEDB@pdsmsx503.ccr.corp.intel.com>
2009-07-01  5:29     ` Han, Weidong
2009-07-01 15:39       ` Jeremy Fitzhardinge

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=4A4A2B68.7050700@goop.org \
    --to=jeremy@goop.org \
    --cc=Patrick.Colp@citrix.com \
    --cc=junkoi2004@gmail.com \
    --cc=weidong.han@intel.com \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.