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] CALL_FUNCTION broadcast vs. a set of cpus

To: "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] CALL_FUNCTION broadcast vs. a set of cpus
From: "Dong, Eddie" <eddie.dong@xxxxxxxxx>
Date: Wed, 31 Aug 2005 14:40:25 +0800
Delivery-date: Wed, 31 Aug 2005 06:38:35 +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: AcWtmKlpP/lfO0nfT1GBlpsOrkFGOAAW74hg
Thread-topic: CALL_FUNCTION broadcast vs. a set of cpus
        Current implementation of CALL_FUNCTION is broadcasting IPI to
all but self. For VMX domain, in some situation like vcpu migration, we
need call function to specified target processor only like VMCS register
dump. I am curious if you'd like to see an additional parameter
(cpu_mask) for smp_call_function and minor modification to
smp_call_function_interrupt to support this? Or do you prefer to add a
new function with similar function but targeting specified cpus?

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] CALL_FUNCTION broadcast vs. a set of cpus, Dong, Eddie <=