From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [PATCH] vpmu: Is CONFIG_SMP used anymore? Date: Wed, 08 Feb 2012 05:57:28 +0000 Message-ID: References: <2192614.Ifr2rPImK0@amur> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <2192614.Ifr2rPImK0@amur> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Dietmar Hahn , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 08/02/2012 13:14, "Dietmar Hahn" wrote: > Hi, > > while locking at the vpmu stuff I found the following stuff: > > diff -r a55e0f9c7b4e xen/arch/x86/oprofile/nmi_int.c > --- a/xen/arch/x86/oprofile/nmi_int.c Wed Feb 08 12:28:47 2012 +0100 > +++ b/xen/arch/x86/oprofile/nmi_int.c Wed Feb 08 14:11:06 2012 +0100 > @@ -305,7 +305,7 @@ static int __init p4_init(char ** cpu_ty > } > > #ifndef CONFIG_SMP > - *cpu_type = "i386/p4", XENOPROF_CPU_TYPE_SIZE); > + *cpu_type = "i386/p4"; > model = &op_p4_spec; > return 1; > #else > > > Is CONFIG_SMP always switched on? It seems nobody tested without CONFIG_SMP. Correct. !CONFIG_SMP isn't configurable or supported. -- Keir > Thanks. > > Dietmar. >