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-changelog] [xen-unstable] sysctl: Another clarification re. max_cpu

To: xen-changelog@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-changelog] [xen-unstable] sysctl: Another clarification re. max_cpu_index.
From: Xen patchbot-unstable <patchbot-unstable@xxxxxxxxxxxxxxxxxxx>
Date: Tue, 13 Jul 2010 10:25:31 -0700
Delivery-date: Tue, 13 Jul 2010 10:27:37 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-changelog-request@lists.xensource.com?subject=help>
List-id: BK change log <xen-changelog.lists.xensource.com>
List-post: <mailto:xen-changelog@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-changelog>, <mailto:xen-changelog-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-changelog>, <mailto:xen-changelog-request@lists.xensource.com?subject=unsubscribe>
Reply-to: xen-devel@xxxxxxxxxxxxxxxxxxx
Sender: xen-changelog-bounces@xxxxxxxxxxxxxxxxxxx
# HG changeset patch
# User Keir Fraser <keir.fraser@xxxxxxxxxx>
# Date 1278956358 -3600
# Node ID 9f08c4e82037415f0677da080470aac97d11d010
# Parent  e9331523d2d1dab1ef193eeaf21ddc22d8c5a925
sysctl: Another clarification re. max_cpu_index.

Signed-off-by: Keir Fraser <keir.fraser@xxxxxxxxxx>
 xen/include/public/sysctl.h |   12 ++++++------
 1 files changed, 6 insertions(+), 6 deletions(-)

diff -r e9331523d2d1 -r 9f08c4e82037 xen/include/public/sysctl.h
--- a/xen/include/public/sysctl.h       Mon Jul 12 18:33:30 2010 +0100
+++ b/xen/include/public/sysctl.h       Mon Jul 12 18:39:18 2010 +0100
@@ -468,17 +468,17 @@ struct xen_sysctl_topologyinfo {
      * IN: maximum addressable entry in the caller-provided arrays.
      * OUT: largest cpu identifier in the system.
      * If OUT is greater than IN then the arrays are truncated!
+     * If OUT is leass than IN then the array tails are not written by sysctl.
     uint32_t max_cpu_index;
-     * If not NULL, this array is filled with core/socket/node identifier for 
-     * each cpu.
+     * If not NULL, these arrays are filled with core/socket/node identifier
+     * for each cpu.
      * If a cpu has no core/socket/node information (e.g., cpu not present) 
-     * then the sentinel value ~0u is written.
-     * The size of this array is specified by the caller (@max_cpu_index+1).
-     * If the array has more than @max_cpu_index+1 elements then the trailing
-     * elements of the array will not be written by the sysctl.
+     * then the sentinel value ~0u is written to each array.
+     * The number of array elements written by the sysctl is:
+     *   min(@max_cpu_index_IN,@max_cpu_index_OUT)+1
     XEN_GUEST_HANDLE_64(uint32) cpu_to_core;
     XEN_GUEST_HANDLE_64(uint32) cpu_to_socket;

Xen-changelog mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-changelog] [xen-unstable] sysctl: Another clarification re. max_cpu_index., Xen patchbot-unstable <=