WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] Genapic

To: "Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx>, "Andi Kleen" <ak@xxxxxx>, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] Genapic
From: "Nakajima, Jun" <jun.nakajima@xxxxxxxxx>
Date: Wed, 18 May 2005 11:26:50 -0700
Cc: "Subrahmanian, Raj" <raj.subrahmanian@xxxxxxxxxx>, "Davis, Jason" <jason.davis@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, "Vessey, Bruce A" <Bruce.Vessey@xxxxxxxxxx>
Delivery-date: Wed, 18 May 2005 18:26:37 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcVbyqB1kbqS5ryTTu6Rk84K2nLwZQAAUR7gAADf3dAAAW+ykA==
Thread-topic: [Xen-devel] Genapic
Puthiyaparambil, Aravindh wrote:
> I am a little confused here. When you say XenLinux I am assuming you
> are talking about the Linux user kernels which have Xen patches. Why
> would we even turn on the mach specific features in the user kernels?
> 
Xen assumes particular mach specific featurs, such as timer, memory
reporting, IRQ, interrutp handling, which don't necessarily work with
such mach specific features as found on real machines.

> I would think that that the mach specific code needs to reside in the
> Xen hypervisor itself. It at the moment has unified apic.c/io_apic.c
> for x86_32 and x86_64 platforms. Don't we to add genapic code in
> there? Or am I wrong on this? Maybe I need more coffee :-)
I talked about the generic platform support, not genapic per se. We have
moved ACPI, PCI, and part of io_apic (which required apic.c) handling to
dom0 to do better platform detection and configuration. Xen still owns
IO APICs, and some operatons must be done by Xen.  

Jun

> 
> Aravindh
> 

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

<Prev in Thread] Current Thread [Next in Thread>