archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <>
To: David Gow <>
Cc: Shuah Khan <>,
	Brendan Higgins <>,
	Kees Cook <>,
Subject: Re: [PATCH linux-kselftest/test v2] lib/list-test: add a test for the 'list' doubly linked list
Date: Fri, 11 Oct 2019 14:55:19 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Fri, 11 Oct 2019 14:37:25 -0700 David Gow <> wrote:

> On Fri, Oct 11, 2019 at 2:05 PM Andrew Morton <> wrote:
> >
> > <looks at kunit>
> >
> > Given that everything runs at late_initcall time, shouldn't everything
> > be __init, __initdata etc so all the code and data doesn't hang around
> > for ever?
> >
> That's an interesting point. We haven't done this for KUnit tests to
> date, and there is certainly a possibility down the line that we may
> want to be able to run these tests in other circumstances. (There's
> some work being done to allow KUnit and KUnit tests to be built as
> modules here: for example.) Maybe
> it'd be worth having macros which wrap __init/__initdata etc as a way
> of futureproofing tests against such a change?
> Either way, I suspect this is something that should probably be
> considered for KUnit as a whole, rather than on a test-by-test basis.

Sure, a new set of macros for this makes sense.  Can be retrofitted any

There might be a way of loading all of list_test.o into a discardable
section at link time instead of sprinkling annotation all over the .c

  reply	other threads:[~2019-10-11 21:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-10 18:56 [PATCH linux-kselftest/test v2] lib/list-test: add a test for the 'list' doubly linked list David Gow
2019-10-11 21:05 ` Andrew Morton
2019-10-11 21:07 ` Andrew Morton
2019-10-11 21:37   ` David Gow
2019-10-11 21:55     ` Andrew Morton [this message]
2019-10-16 20:48       ` Brendan Higgins
2019-10-16 21:48       ` David Gow
2019-10-17  0:32         ` Andrew Morton
2019-10-18 21:24           ` shuah
2019-10-18 21:21 ` shuah

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:

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

  git send-email \ \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).