[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m2bnjfasbn.wl@sfc.wide.ad.jp>
Date: Fri, 27 Mar 2015 15:05:16 +0900
From: Hajime Tazaki <tazaki@....wide.ad.jp>
To: rusty@...tcorp.com.au
Cc: richard@....at, linux-arch@...r.kernel.org, arnd@...db.de,
corbet@....net, cl@...ux.com, penberg@...nel.org,
rientjes@...gle.com, iamjoonsoo.kim@....com,
akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org, netdev@...r.kernel.org,
linux-mm@...ck.org, jdike@...toit.com, mathieu.lacage@...il.com
Subject: Re: [RFC PATCH 00/11] an introduction of library operating system for Linux (LibOS)
Hi Rusty,
At Fri, 27 Mar 2015 14:01:22 +1030,
Rusty Russell wrote:
>
> Richard Weinberger <richard@....at> writes:
> > This also infers that arch/lib will be broken most of the time as
> > every time the networking stack references a new symbol it
> > has to be duplicated into arch/lib.
> >
> > But this does not mean that your idea is bad, all I want to say that
> > I'm not sure whether arch/lib is the right approach.
> > Maybe Arnd has a better idea.
>
> Exactly why I look forward to getting this in-tree. Jeremy Kerr and I
> wrote nfsim back in 2005(!) which stubbed around the netfilter
> infrastructure; with failtest and valgrind it found some nasty bugs. It
> was too much hassle to maintain out-of-tree though :(
we're aware of (and respected ;)) nfsim, and expanded the
idea with DCE: make test ARCH=lib gives a broad testsuite
for network stack.
# we also have
make {test-valgrind, test-fault-injection} ARCH=lib
but not well tested (of the options themselves) yet.
there are the overview of test facility in my slides (the
link is in my original cover letter email)
> I look forward to a flood of great bugfixes from this work :)
it has not been so much, but the following fix for xfrm
regression was detected by this framework (through jenkins
CI). git bisect is also easy (see tools/testing/libos/bisect.sh).
http://patchwork.ozlabs.org/patch/436351/
thanks for the comment.
-- Hajime
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists