From mboxrd@z Thu Jan  1 00:00:00 1970
From: greg@kroah.com (Greg KH)
Date: Fri, 20 Feb 2015 12:24:27 -0800
Subject: Kernel Mocking
In-Reply-To: <CAK7rcp_OPFLLo_7yykxppBShokqsqhwHpEa=7rYZ+7dpOBNnMw@mail.gmail.com>
References: <CAK7rcp_OPFLLo_7yykxppBShokqsqhwHpEa=7rYZ+7dpOBNnMw@mail.gmail.com>
Message-ID: <20150220202427.GA23293@kroah.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

On Fri, Feb 20, 2015 at 02:51:25PM -0500, Kenneth Adam Miller wrote:
> So, in userland development, the idea of mocking is used to isolate context
> management and machine configuration into a single class or set of functions
> that can be reused, and also facilitate testing much easier. Google mock is a
> great example.
> 
> Say I develop a kernel module, and I want that module to have some result X
> after some returned result, whatever that might be. Is there anything similar
> for kernel code??

Not really, sorry.  Running in the kernel means you don't have much room
for "simulation".  But you can use qemu, or other virtual machines and a
debugger to test your code if you really want to.

Good luck!

greg k-h