[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m2wq1uq944.wl@wide.ad.jp>
Date: Fri, 03 Apr 2015 10:43:55 +0900
From: Hajime Tazaki <tazaki@...e.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)
Thanks Rusty,
At Wed, 01 Apr 2015 11:59:39 +1030,
Rusty Russell wrote:
>
> Hajime Tazaki <tazaki@....wide.ad.jp> writes:
> > the issue here is the decision between 'no-ops' and
> > 'assert(false)' depends on the context. an auto-generated
> > mechanism needs some hand-written parameters I think.
>
> Yes, I used auto-generated (fprintf, abort) stubs for similar testing in
> pettycoin, where if it failed to link it would generate such stubs
> for undefined symbols.
>
> It's not a panacea, but it helps speed up rejiggin after code changes.
> Generating noop stubs can actually make that process slower, as you can
> get failures because you now need to do something in that stub.
is it the following ? it's really cool stuff !
https://github.com/rustyrussell/pettycoin/blob/master/test/mockup.sh
-- 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