[PATCH v9 6/6] tests/guest-debug: introduce basic gdbstub tests
Alex Bennée
alex.bennee at linaro.org
Tue Dec 8 04:02:11 PST 2015
Peter Maydell <peter.maydell at linaro.org> writes:
> On 12 November 2015 at 16:20, Alex Bennée <alex.bennee at linaro.org> wrote:
>> From: Alex Bennée <alex at bennee.com>
>>
>> The aim of these tests is to combine with an appropriate kernel
>> image (with symbol-file vmlinux) and check it behaves as it should.
>> Given a kernel it checks:
>>
>> - single step
>> - software breakpoint
>> - hardware breakpoint
>> - access, read and write watchpoints
>>
>> On success it returns 0 to the calling process.
>>
>> I've not plumbed this into the "make check" logic though as we need a
>> solution for providing non-host binaries to the tests. However the test
>> is structured to work with pretty much any Linux kernel image as it
>> uses the basic kernel_init code which is common across architectures.
>
> Do these tests pass if you run them on the TCG QEMU, just out
> of interest?
You'll be glad to know they do.
> I'm not a great fan of tests that aren't in 'make check'
> because IME they just bitrot, but as you say we have no
> sensible approach for handling tests that need to run real
> guest code :-(
I was pondering if a git sub-project with large file support would work.
We could add pre-built binaries to the tree with appropriate meta-data
(src tree, version, config) to rebuild if required.
There would be some degree of trust implied in the original builder
though. Maybe a signed commit?
>
> thanks
> -- PMM
--
Alex Bennée
More information about the linux-arm-kernel
mailing list