From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: [PATCH] xen/spinlock: Use mnemonics for recursive spinlock sentinel values Date: Mon, 11 Jan 2016 15:35:48 +0000 Message-ID: <5693CBD4.60806@citrix.com> References: <1452350038-29323-1-git-send-email-andrew.cooper3@citrix.com> <5693C80C02000078000C5716@prv-mh.provo.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5693C80C02000078000C5716@prv-mh.provo.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: Tim Deegan , Doug Goldstein , Ian Campbell , Xen-devel List-Id: xen-devel@lists.xenproject.org On 11/01/16 14:19, Jan Beulich wrote: >>>> On 09.01.16 at 15:33, wrote: >> --- a/xen/common/spinlock.c >> +++ b/xen/common/spinlock.c >> @@ -246,7 +246,7 @@ int _spin_trylock_recursive(spinlock_t *lock) >> unsigned int cpu = smp_processor_id(); >> >> /* Don't allow overflow of recurse_cpu field. */ >> - BUILD_BUG_ON(NR_CPUS > 0xfffu); >> + BUILD_BUG_ON(NR_CPUS >= SPINLOCK_NO_CPU); > ">" (see also the reply to Doug's patch 1/2) So it is. As there is no bug, I will resubmit the cleanup when the NR_CPUS series is in to avoid causing patch conflicts. ~Andrew