public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel•org>
To: Brendan Higgins <brendanhiggins@google•com>
Cc: "open list:DOCUMENTATION" <linux-doc@vger•kernel.org>,
	catalin.marinas@arm•com, jcmvbkbc@gmail•com, will@kernel•org,
	paulus@samba•org,
	"open list:KERNEL SELFTEST FRAMEWORK"
	<linux-kselftest@vger•kernel.org>,
	Frank Rowand <frowand.list@gmail•com>,
	Anton Ivanov <anton.ivanov@cambridgegreys•com>,
	linux-arch@vger•kernel.org, Richard Weinberger <richard@nod•at>,
	rppt@linux•ibm.com, Iurii Zaikin <yzaikin@google•com>,
	linux-xtensa@linux-xtensa•org, Kees Cook <keescook@chromium•org>,
	Arnd Bergmann <arnd@arndb•de>, Jeff Dike <jdike@addtoit•com>,
	linux-um <linux-um@lists•infradead.org>,
	linuxppc-dev@lists•ozlabs.org, David Gow <davidgow@google•com>,
	Shuah Khan <skhan@linuxfoundation•org>,
	Linux ARM <linux-arm-kernel@lists•infradead.org>,
	KUnit Development <kunit-dev@googlegroups•com>,
	chris@zankel•net, monstr@monstr•eu,
	Stephen Boyd <sboyd@kernel•org>,
	Greg KH <gregkh@linuxfoundation•org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Logan Gunthorpe <logang@deltatee•com>,
	Andrew Morton <akpm@linux-foundation•org>,
	Alan Maguire <alan.maguire@oracle•com>
Subject: Re: [PATCH v5 01/12] vmlinux.lds.h: add linker section for KUnit test suites
Date: Wed, 8 Jul 2020 04:31:28 +0000	[thread overview]
Message-ID: <20200708043128.GY4332@42.do-not-panic.com> (raw)
In-Reply-To: <CAFd5g47vu5vmrXnS0sLu+hdC2HmYz7GY82sE8rhcHfNkuC1NRw@mail.gmail.com>

On Fri, Jun 26, 2020 at 02:22:11PM -0700, Brendan Higgins wrote:
> On Fri, Jun 26, 2020 at 2:20 PM Kees Cook <keescook@chromium•org> wrote:
> >
> > On Fri, Jun 26, 2020 at 02:09:06PM -0700, Brendan Higgins wrote:
> > > Add a linker section where KUnit can put references to its test suites.
> > > This patch is the first step in transitioning to dispatching all KUnit
> > > tests from a centralized executor rather than having each as its own
> > > separate late_initcall.
> > >
> > > Co-developed-by: Iurii Zaikin <yzaikin@google•com>
> > > Signed-off-by: Iurii Zaikin <yzaikin@google•com>
> > > Signed-off-by: Brendan Higgins <brendanhiggins@google•com>
> > > Reviewed-by: Stephen Boyd <sboyd@kernel•org>
> > > ---
> > >  include/asm-generic/vmlinux.lds.h | 8 ++++++++
> > >  1 file changed, 8 insertions(+)
> > >
> > > diff --git a/include/asm-generic/vmlinux.lds.h b/include/asm-generic/vmlinux.lds.h
> > > index db600ef218d7d..4f9b036fc9616 100644
> > > --- a/include/asm-generic/vmlinux.lds.h
> > > +++ b/include/asm-generic/vmlinux.lds.h
> > > @@ -881,6 +881,13 @@
> > >               KEEP(*(.con_initcall.init))                             \
> > >               __con_initcall_end = .;
> > >
> > > +/* Alignment must be consistent with (kunit_suite *) in include/kunit/test.h */
> >
> > Nit on naming:
> >
> > > +#define KUNIT_TEST_SUITES                                            \
> >
> > I would call this KUNIT_TABLE to maintain the same names as other things
> > of this nature.
> >
> > > +             . = ALIGN(8);                                           \
> > > +             __kunit_suites_start = .;                               \
> > > +             KEEP(*(.kunit_test_suites))                             \
> > > +             __kunit_suites_end = .;
> > > +
> > >  #ifdef CONFIG_BLK_DEV_INITRD
> > >  #define INIT_RAM_FS                                                  \
> > >       . = ALIGN(4);                                                   \
> > > @@ -1056,6 +1063,7 @@
> > >               INIT_CALLS                                              \
> > >               CON_INITCALL                                            \
> > >               INIT_RAM_FS                                             \
> > > +             KUNIT_TEST_SUITES                                       \
> > >       }
> >
> > Nack: this must be in INIT_DATA, not in INIT_DATA_SECTION. Not all
> > architectures use the INIT_DATA_SECTION macro (e.g. arm64), but everything
> > uses INIT_DATA.
> 
> Oh, maybe that would eliminate the need for the other linkerscript
> patches? That would be nice.

Curious, did changing it as Kees suggest fix it for m68k?

  Luis

  reply	other threads:[~2020-07-08  4:33 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-26 21:09 [PATCH v5 00/12] kunit: create a centralized executor to dispatch all KUnit tests Brendan Higgins
2020-06-26 21:09 ` [PATCH v5 01/12] vmlinux.lds.h: add linker section for KUnit test suites Brendan Higgins
2020-06-26 21:20   ` Kees Cook
2020-06-26 21:22     ` Brendan Higgins
2020-07-08  4:31       ` Luis Chamberlain [this message]
2020-08-04 20:03         ` Brendan Higgins
2020-06-26 21:09 ` [PATCH v5 02/12] arch: arm64: " Brendan Higgins
2020-06-26 21:20   ` Kees Cook
2020-06-26 21:23     ` Brendan Higgins
2020-06-26 21:09 ` [PATCH v5 03/12] arch: microblaze: " Brendan Higgins
2020-06-26 21:09 ` [PATCH v5 04/12] arch: powerpc: " Brendan Higgins
2020-06-26 21:09 ` [PATCH v5 05/12] arch: um: " Brendan Higgins
2020-06-26 21:09 ` [PATCH v5 06/12] arch: xtensa: " Brendan Higgins
2020-06-26 21:30   ` Kees Cook
2020-06-26 21:09 ` [PATCH v5 07/12] kunit: test: create a single centralized executor for all tests Brendan Higgins
2020-06-26 21:29   ` Kees Cook
2020-08-04 20:06     ` Brendan Higgins
2020-06-26 21:09 ` [PATCH v5 08/12] init: main: add KUnit to kernel init Brendan Higgins
2020-06-26 21:33   ` Kees Cook
2020-07-08  4:38   ` Luis Chamberlain
2020-06-26 21:09 ` [PATCH v5 09/12] kunit: test: add test plan to KUnit TAP format Brendan Higgins
2020-06-26 21:35   ` Kees Cook
2020-08-04 20:10     ` Brendan Higgins
2020-06-26 21:09 ` [PATCH v5 10/12] kunit: Add 'kunit_shutdown' option Brendan Higgins
2020-06-26 21:40   ` Kees Cook
2020-08-04 20:18     ` Brendan Higgins
2020-06-26 21:09 ` [PATCH v5 11/12] Documentation: Add kunit_shutdown to kernel-parameters.txt Brendan Higgins
2020-06-26 21:09 ` [PATCH v5 12/12] Documentation: kunit: add a brief blurb about kunit_test_suite Brendan Higgins
2020-06-26 21:52 ` [PATCH v5 00/12] kunit: create a centralized executor to dispatch all KUnit tests Kees Cook
2020-08-04 20:01   ` Brendan Higgins

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200708043128.GY4332@42.do-not-panic.com \
    --to=mcgrof@kernel$(echo .)org \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=alan.maguire@oracle$(echo .)com \
    --cc=anton.ivanov@cambridgegreys$(echo .)com \
    --cc=arnd@arndb$(echo .)de \
    --cc=brendanhiggins@google$(echo .)com \
    --cc=catalin.marinas@arm$(echo .)com \
    --cc=chris@zankel$(echo .)net \
    --cc=davidgow@google$(echo .)com \
    --cc=frowand.list@gmail$(echo .)com \
    --cc=gregkh@linuxfoundation$(echo .)org \
    --cc=jcmvbkbc@gmail$(echo .)com \
    --cc=jdike@addtoit$(echo .)com \
    --cc=keescook@chromium$(echo .)org \
    --cc=kunit-dev@googlegroups$(echo .)com \
    --cc=linux-arch@vger$(echo .)kernel.org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-doc@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-kselftest@vger$(echo .)kernel.org \
    --cc=linux-um@lists$(echo .)infradead.org \
    --cc=linux-xtensa@linux-xtensa$(echo .)org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=logang@deltatee$(echo .)com \
    --cc=monstr@monstr$(echo .)eu \
    --cc=paulus@samba$(echo .)org \
    --cc=richard@nod$(echo .)at \
    --cc=rppt@linux$(echo .)ibm.com \
    --cc=sboyd@kernel$(echo .)org \
    --cc=skhan@linuxfoundation$(echo .)org \
    --cc=will@kernel$(echo .)org \
    --cc=yzaikin@google$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox