From: Keir Fraser Subject: Re: conflicting sysctl numbers Date: Tue, 01 Dec 2009 07:20:35 +0000 Message-ID: References: <8EA2C2C4116BF44AB370468FBF85A777010FC16205@orsmsx504.amr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <8EA2C2C4116BF44AB370468FBF85A777010FC16205@orsmsx504.amr.corp.intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Kamble, Nitin A" , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org Thanks Nitin, I'll fix it. K. On 01/12/2009 01:41, "Kamble, Nitin A" wrote: > Keir, > =20 > I found there are two sysctls with conflicting same sysctl no in the code= . > This looks like a issue caused by merging code from different developers,= and > need fixing.=20 > =20 > xen/include/public/sysctl.h > =20 > #define XEN_SYSCTL_cpu_hotplug 11 > =8A > #define XEN_SYSCTL_lockprof_op 11 > =20 > =20 > Looks like this has come from changeset 20312: > =20 > Spinlock profiling (enable in build with lock_profile=3Dy) > =20 > Adds new tool xenlockprof to run from dom0. > =20 > From: Juergen Gross > Signed-off-by: Keir Fraser > =20 > =20 > Thanks & Regards, > Nitin > Linux Open Source Technology Center, Intel Corporation > ------------------------------------------------------ > =20 >=20