From: Arun Sharma <arun.sharma@intel.com>
To: "Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@unisys.com>
Cc: xen-devel@lists.xensource.com, "Vessey,
Bruce A" <Bruce.Vessey@unisys.com>,
"Subrahmanian, Raj" <raj.subrahmanian@unisys.com>
Subject: Re: [PATCH] pci-ioapic-0502.patch
Date: Wed, 04 May 2005 13:08:14 -0700 [thread overview]
Message-ID: <42792BAE.7040005@intel.com> (raw)
In-Reply-To: <EF8D308BE33AF54D8934DF26520252D301B258D3@USTR-EXCH5.na.uis.unisys.com>
Puthiyaparambil, Aravindh wrote:
> Arun,
>
> I tried the patch out on my dual proc x86_64 box running 32-bit SLES9. I
> was able to boot the system successfully and bring up a VM. The only
> thing which caught my eye was the following in the Dom0 boot.
>
> IOAPIC[0]: Invalid reference to IRQ 0
>
I'll take a look at this later today.
> I am not even sure if this is an error. I have attached the complete
> boot sequence.
>
> I noticed that the I/O APICs are still being initialized by Xen. Are you
> planning on moving this also to Dom0?
>
No. As the checkin comments say, ioapics are owned by Xen. dom0 knows
about it's existence, but accesses it using hypercalls.
-Arun
next prev parent reply other threads:[~2005-05-04 20:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-04 18:33 [PATCH] pci-ioapic-0502.patch Puthiyaparambil, Aravindh
2005-05-04 19:00 ` Keir Fraser
2005-05-04 20:08 ` Arun Sharma [this message]
2005-05-05 1:31 ` Arun Sharma
-- strict thread matches above, loose matches on Subject: below --
2005-05-02 22:35 Arun Sharma
2005-05-03 20:58 ` Anthony Liguori
2005-05-03 21:14 ` Arun Sharma
2005-05-03 21:24 ` Anthony Liguori
2005-05-03 21:43 ` Arun Sharma
2005-05-03 22:17 ` Anthony Liguori
2005-05-05 18:14 ` Patrick Scharrenberg
2005-05-05 18:36 ` Arun Sharma
2005-05-06 6:53 ` Patrick Scharrenberg
2005-05-06 20:41 ` Patrick Scharrenberg
2005-05-06 21:00 ` Keir Fraser
2005-05-06 21:17 ` Jonathan S. Shapiro
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=42792BAE.7040005@intel.com \
--to=arun.sharma@intel.com \
--cc=Bruce.Vessey@unisys.com \
--cc=aravindh.puthiyaparambil@unisys.com \
--cc=raj.subrahmanian@unisys.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.