This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-ia64-devel] consoles, iosapics, and device interrupts

To: "Williamson, Alex (Linux Kernel Dev)" <alex.williamson@xxxxxx>
Subject: RE: [Xen-ia64-devel] consoles, iosapics, and device interrupts
From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
Date: Mon, 21 Nov 2005 09:05:32 -0800
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx, Tristan Gingold <Tristan.Gingold@xxxxxxxx>
Delivery-date: Mon, 21 Nov 2005 17:06:03 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcXuvMYNDCCX75rLQ+6aTGkE+dDP1wAAHI5w
Thread-topic: [Xen-ia64-devel] consoles, iosapics, and device interrupts
> > I'm not an expert in this area but I think the difference
> > is that x86 uses legacy interrupts for serial ports so
> > console input is easier on Xen/x86.  Since many ia64
> > boxes do not have legacy interrupts for serial ports,
> > we need to differ from Xen/x86.  If, in order to be
> > functionally equivalent with Xen/x86, we need to
> > import huge amounts of ACPI code, I think we should
> > consider some other alternatives.
>    I agree, but lets not limit ourselves to consoles and interrupts,
> those are too trivial.  What about:
>       * Thermal management
>       * Power management (AC adapters to P-states to device power
>         states)
>       * Hotplug (memory, cpus, pci devices, pci root bridges, ACPI
>         container devices)
> For some of these, dom0 can manage the ACPI part of it.  However, can
> dom0 manage physical devices?  Maybe the I/O devices, but physical
> memory and CPUs need to stay hidden (don't they?).  This is sounding
> more like something that needs to move to xen-devel.

You are correct, there are some fundamental architectural
decisions here that would best be discussed in xen-devel.
Please couch the discussion in terms of how it should work
post-3.0, not how it works today.


Xen-ia64-devel mailing list