From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: [PATCH 1 of 4] CONFIG: remove CONFIG_SMP #ifdefs Date: Thu, 9 Feb 2012 11:51:39 +0000 Message-ID: <4F33B34B.30403@citrix.com> References: <101b0d7ebb00e1af8acf.1328719536@andrewcoop.uk.xensource.com> <4F32AF53.5070006@citrix.com> <4F33B3F10200007800071DAE@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4F33B3F10200007800071DAE@nat28.tlf.novell.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: Jan Beulich Cc: "xen-devel@lists.xensource.com" , "Keir (Xen.org)" List-Id: xen-devel@lists.xenproject.org On 09/02/12 10:54, Jan Beulich wrote: >>>> On 08.02.12 at 18:22, Andrew Cooper wrote: > Doing this in x86 code is perhaps fine; you shouldn't do this in common > code though (ia64, for example, allows [at least theoretically] to be > built non-SMP, even though particularly on that architecture this seems > to make very little sense). > > Jan Im some ways, that is the same as x86 !CONFIG_SMP support; theoretically sensible but we never use it. Is !SMP 'supported' for IA64 in any way? -- Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer T: +44 (0)1223 225 900, http://www.citrix.com