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


[Xen-devel] c/s 18470

To: <jinsong.liu@xxxxxxxxx>
Subject: [Xen-devel] c/s 18470
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Wed, 17 Sep 2008 08:43:20 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 17 Sep 2008 00:43:07 -0700
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
This changeset reverts two previous corrections, for reasons that escape

First, the domain map is again being confined to NR_CPUS, which I had
submitted a patch to fix recently (yes, I realize the code has a TODO in
there, but those really get forgotten about far too often).

Second, the platform hypercall was reverted back to require all
information to be passed to Xen in one chunk, whereas I recall that even
Intel folks (not sure if it was you) agreed that allowing incremental
information collection was more appropriate.

Could you clarify why these changes were necessary and if/when you
plan to address the resulting issues?

Thanks, Jan

Xen-devel mailing list

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