On Thu, Mar 21, 2019 at 5:28 PM Frank Rowand <frowand.list@xxxxxxxxx> wrote: > > On 12/5/18 3:10 PM, Brendan Higgins wrote: > > On Tue, Dec 4, 2018 at 5:49 AM Rob Herring <robh@xxxxxxxxxx> wrote: > >> > >> On Tue, Dec 4, 2018 at 5:40 AM Frank Rowand <frowand.list@xxxxxxxxx> wrote: > >>> > >>> Hi Brendan, Rob, > >>> > >>> Pulling a comment from way back in the v1 patch thread: > >>> > >>> On 10/17/18 3:22 PM, Brendan Higgins wrote: > >>>> On Wed, Oct 17, 2018 at 10:49 AM <Tim.Bird@xxxxxxxx> wrote: > >>> > >>> < snip > > >>> > >>>> The test and the code under test are linked together in the same > >>>> binary and are compiled under Kbuild. Right now I am linking > >>>> everything into a UML kernel, but I would ultimately like to make > >>>> tests compile into completely independent test binaries. So each test > >>>> file would get compiled into its own test binary and would link > >>>> against only the code needed to run the test, but we are a bit of a > >>>> ways off from that. > >>> > >>> I have never used UML, so you should expect naive questions from me, > >>> exhibiting my lack of understanding. > >>> > >>> Does this mean that I have to build a UML architecture kernel to run > >>> the KUnit tests? > >> > >> In this version of the patch series, yes. > >> > >>> *** Rob, if the answer is yes, then it seems like for my workflow, > >>> which is to build for real ARM hardware, my work is doubled (or > >>> worse), because for every patch/commit that I apply, I not only have > >>> to build the ARM kernel and boot on the real hardware to test, I also > >>> have to build the UML kernel and boot in UML. If that is correct > >>> then I see this as a major problem for me. > >> > >> I've already raised this issue elsewhere in the series. Restricting > >> the DT tests to UML is a non-starter. > > > > > I have already stated my position elsewhere on the matter, but in > > summary: Ensuring most tests can run without external dependencies > > (hardware, VM, etc) has a lot of benefits and should be supported in > > nearly all cases, but such tests should also work when compiled to run > > on real hardware/VM; the tooling might not be as good in the latter > > case, but I understand that there are good reasons to support it > > nonetheless. > > And my needs are the exact opposite. My tests must run on real hardware, > in the context of the real operating system subsystems and drivers > potentially causing issues. Right, Rob pointed this out, and I fixed this in v4. To be clear, as of RFC v4 you can run KUnit tests on non-UML architectures, we tested it on x86 and ARM. > > It is useful if the tests can also run without that dependency. This, of course, is still the main intended use case, but there is nothing to stop you from using it on real hardware.
