[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180410175105.eghfnktjq55vaxto@treble>
Date: Tue, 10 Apr 2018 12:51:05 -0500
From: Josh Poimboeuf <jpoimboe@...hat.com>
To: Miroslav Benes <mbenes@...e.cz>
Cc: Petr Mladek <pmladek@...e.com>,
Joe Lawrence <joe.lawrence@...hat.com>,
live-patching@...r.kernel.org, linux-kernel@...r.kernel.org,
lpechacek@...e.com, nstange@...e.de
Subject: Re: [PATCH] selftests/livepatch: introduce tests
On Tue, Apr 10, 2018 at 04:31:05PM +0200, Miroslav Benes wrote:
>
> > > > I love this. Nice work!
>
> Yes, it looks really good.
>
> > > > As you and Petr discussed, it would be nice to get rid of some of the
> > > > delays, and also the callback tests will be very important.
> > >
> > > I've got v2 WIP that minimizes the delays, cleans up build flags, and
> > > adds a basic shadow variable test.
> >
> > Sounds great.
> >
> > > Since these tests are based on top of Petr's current patchsets for
> > > atomic replace and shadow variables, it probably makes sense for those
> > > to merge first. I can post test results to his patchsets if that helps.
> >
> > Sounds good to me. We could synchronize the merge. But I think that it
> > will not be a big deal if we would merge the atomic replace slightly
> > earlier if the tests needed some more love.
>
> Well, it depends. Josh wants the patch first and then atomic replace. So
> we can merge selftests for all features we currently have and tests for
> atomic replace could go with it.
Well, I don't want to add additional work, if it's not needed. Joe's
selftests are coming along nicely. If the selftest patch is merged
shortly after Petr's set, that's fine with me. Or maybe Petr can just
add Joe's patch to the end of his set.
--
Josh
Powered by blists - more mailing lists