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-devel] [RFC] Genapic in x86_64 Dom0

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] [RFC] Genapic in x86_64 Dom0
From: "Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx>
Date: Mon, 22 Aug 2005 12:14:14 -0400
Cc: "Koren, Bradley J" <Bradley.Koren@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Chris Wright <chrisw@xxxxxxxx>, "Magolan, John F" <John.Magolan@xxxxxxxxxx>, "Subrahmanian, Raj" <raj.subrahmanian@xxxxxxxxxx>, "Davis, Jason" <jason.davis@xxxxxxxxxx>, "Vessey, Bruce A" <Bruce.Vessey@xxxxxxxxxx>
Delivery-date: Mon, 22 Aug 2005 16:14:07 +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: AcWla7ZdunriOZAKRa+qKTyMFspEzgByGbqw
Thread-topic: [Xen-devel] [RFC] Genapic in x86_64 Dom0
> Isn't flat/clustered mostly a local APIC issue? In which case domain 0
> needn't care, as local APICs are entirely maintained by Xen.

Yes you are right. The way Chris has written xen_send_IPI_shortcut()
should take care of the clustered case too.

> As for IO APICs, although domain 0 writes the routing entries, Xen is
> responsible for stamping in appropriate destination fields, based on
> knowledge of physical CPU IDs and which domains are running on which
> physical CPUs. This code can be extended to handle writing
> clustering-compatible routing entries.

This sounds like a better idea and less work ;-) I will submit a patch.


Xen-devel mailing list

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