From owner-freebsd-testing@FreeBSD.ORG  Tue Jul 22 23:07:57 2014
Return-Path: <owner-freebsd-testing@FreeBSD.ORG>
Delivered-To: freebsd-testing@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 5B8D58E0
 for <freebsd-testing@freebsd.org>; Tue, 22 Jul 2014 23:07:57 +0000 (UTC)
Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com
 [IPv6:2607:f8b0:4001:c03::22d])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 2F79E2209
 for <freebsd-testing@freebsd.org>; Tue, 22 Jul 2014 23:07:57 +0000 (UTC)
Received: by mail-ie0-f173.google.com with SMTP id tr6so318048ieb.32
 for <freebsd-testing@freebsd.org>; Tue, 22 Jul 2014 16:07:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=TojNHiDJu0btrsuBeBNaliWtqZjKMxTisccSY64YUO8=;
 b=YaClK8v5XVfFgwm2/Pq20Ic/Yyr8xwTp4/xi5yDk0hrb/QjpH1LzoVIcl5QZxNavPN
 xtPozeilP/rB82ihfznI1oRk8xd67LOnV6YbAiLiDAlICuT69fITRKgkuq0vkgTkhhmy
 dBT9eJ0L3SjoA5cXJQD4UQyobT7VnF5UlcoVf82OWtKc950Zm7x1twaB/wjRBJl9RA2v
 DdTimZ9BxhMChEkvROeAQ0dzB1jnSlvyeUmf8+V+BhsiLKNknyxFCImIqDqtc/6hMzoI
 47S70/vzomMpK+AcxnclPdLPaJ56sZQLPmFhKrnlGKPB+Q12OBSEPDFT6rIzlHmaZ+81
 X+2w==
MIME-Version: 1.0
X-Received: by 10.50.66.133 with SMTP id f5mr21281711igt.38.1406070476695;
 Tue, 22 Jul 2014 16:07:56 -0700 (PDT)
Received: by 10.50.213.102 with HTTP; Tue, 22 Jul 2014 16:07:56 -0700 (PDT)
Date: Tue, 22 Jul 2014 16:07:56 -0700
Message-ID: <CAGHfRMC==6WRKwd13R7Yyjyu+_Oi_173TLTXPVk9ynH0G5qqxg@mail.gmail.com>
Subject: Location of test kernel drivers in tree?
From: Garrett Cooper <yaneurabeya@gmail.com>
To: "freebsd-testing@freebsd.org" <freebsd-testing@freebsd.org>
Content-Type: text/plain; charset=UTF-8
X-BeenThere: freebsd-testing@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Testing on FreeBSD <freebsd-testing.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-testing>, 
 <mailto:freebsd-testing-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-testing/>
List-Post: <mailto:freebsd-testing@freebsd.org>
List-Help: <mailto:freebsd-testing-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-testing>, 
 <mailto:freebsd-testing-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jul 2014 23:07:57 -0000

Hi all,
    I need to do some KPI verification and hook that into ATF / kyua.
Since we don't have RUMP [yet] from NetBSD, I would typically write a
simple, one-off test driver, hook it into the kernel build and have a
piece of C or shell code that pokes directly at the driver to get
access to kernel interfaces.
    I was wondering if it made sense to put all test drivers into
sys/tests/<module-name>/..., e.g.
sys/tests/test_memguard/{Makefile,test_memguard.c}, etc. Is there an
alternative approach that others use to solve this problem?
Thanks!
-Garrett