Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757221AbcK3IBI (ORCPT ); Wed, 30 Nov 2016 03:01:08 -0500 Received: from mail-wm0-f67.google.com ([74.125.82.67]:32932 "EHLO mail-wm0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753043AbcK3IA5 (ORCPT ); Wed, 30 Nov 2016 03:00:57 -0500 Subject: Re: [PATCH 1/4] locking: Begin kselftests for ww_mutex To: Chris Wilson , linux-kernel@vger.kernel.org References: <1480335612-12069-1-git-send-email-nhaehnle@gmail.com> <20161130003548.22266-1-chris@chris-wilson.co.uk> Cc: Peter Zijlstra , Maarten Lankhorst From: =?UTF-8?Q?Nicolai_H=c3=a4hnle?= Message-ID: Date: Wed, 30 Nov 2016 09:00:47 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20161130003548.22266-1-chris@chris-wilson.co.uk> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2578 Lines: 71 On 30.11.2016 01:35, Chris Wilson wrote: > Signed-off-by: Chris Wilson > Cc: Peter Zijlstra > Cc: Maarten Lankhorst > Cc: Nicolai Hähnle > --- > kernel/locking/Makefile | 1 + > kernel/locking/test-ww_mutex.c | 137 +++++++++++++++++++++++++++++++++++++++++ > lib/Kconfig.debug | 10 +++ > 3 files changed, 148 insertions(+) > create mode 100644 kernel/locking/test-ww_mutex.c > > diff --git a/kernel/locking/Makefile b/kernel/locking/Makefile > index 6f88e352cd4f..760158d9d98d 100644 > --- a/kernel/locking/Makefile > +++ b/kernel/locking/Makefile > @@ -28,3 +28,4 @@ obj-$(CONFIG_RWSEM_GENERIC_SPINLOCK) += rwsem-spinlock.o > obj-$(CONFIG_RWSEM_XCHGADD_ALGORITHM) += rwsem-xadd.o > obj-$(CONFIG_QUEUED_RWLOCKS) += qrwlock.o > obj-$(CONFIG_LOCK_TORTURE_TEST) += locktorture.o > +obj-$(CONFIG_WW_MUTEX_SELFTEST) += test-ww_mutex.o > diff --git a/kernel/locking/test-ww_mutex.c b/kernel/locking/test-ww_mutex.c > new file mode 100644 > index 000000000000..e94b807e06c2 > --- /dev/null > +++ b/kernel/locking/test-ww_mutex.c > @@ -0,0 +1,137 @@ > +/* > + * Module-based API test facility for ww_mutexes > + * > + * This program is free software; you can redistribute it and/or modify > + * it under the terms of the GNU General Public License as published by > + * the Free Software Foundation; either version 2 of the License, or > + * (at your option) any later version. > + * > + * This program is distributed in the hope that it will be useful, > + * but WITHOUT ANY WARRANTY; without even the implied warranty of > + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the > + * GNU General Public License for more details. > + * > + * You should have received a copy of the GNU General Public License > + * along with this program; if not, you can access it online at > + * http://www.gnu.org/licenses/gpl-2.0.html. > + */ > + > +#include > +#include > +#include > +#include > +#include > + > +MODULE_LICENSE("GPL"); > +MODULE_AUTHOR("Intel Corporation"); > + > +static DEFINE_WW_CLASS(ww_class); > + > +struct test_mutex { > + struct work_struct work; > + struct ww_mutex mutex; > + struct completion ready, go, done; > + unsigned flags; > +#define TEST_AB_SPIN BIT(0) > +#define TEST_AB_TRY BIT(1) > +}; Is it common to put #defines inside structs like that? It looks odd to me. Apart from that, patches 1-4 all make sense to me. Thanks, Nicolai