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: Make meaning of max_cpu_index fie

To: xen-changelog@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-changelog] [xen-unstable] sysctl: Make meaning of max_cpu_index field clearer.
From: Xen patchbot-unstable <patchbot-unstable@xxxxxxxxxxxxxxxxxxx>
Date: Tue, 13 Jul 2010 10:25:30 -0700
Delivery-date: Tue, 13 Jul 2010 10:27:30 -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 1278956010 -3600
# Node ID e9331523d2d1dab1ef193eeaf21ddc22d8c5a925
# Parent  c41211b25b44a9df6ca9c62c22200a0df3be69a7
sysctl: Make meaning of max_cpu_index field clearer.

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

diff -r c41211b25b44 -r e9331523d2d1 xen/include/public/sysctl.h
--- a/xen/include/public/sysctl.h       Mon Jul 12 18:30:26 2010 +0100
+++ b/xen/include/public/sysctl.h       Mon Jul 12 18:33:30 2010 +0100
@@ -476,8 +476,8 @@ struct xen_sysctl_topologyinfo {
      * 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 in @max_cpu_index.
-     * If the actual @max_cpu_index is smaller than the array then the trailing
+     * 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.
     XEN_GUEST_HANDLE_64(uint32) cpu_to_core;

Xen-changelog mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-changelog] [xen-unstable] sysctl: Make meaning of max_cpu_index field clearer., Xen patchbot-unstable <=