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

["Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>]

> > 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.

Dan

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel