Branch: refs/heads/next
Home: https://github.com/siemens/jailhouse
Commit: f5a0a36601c27b7bf39f17bc3cac4e28f6434b85
https://github.com/siemens/jailhouse/commit/f5a0a36601c27b7bf39f17bc3cac4e28f6434b85
Author: Jan Kiszka <[email protected]>
Date: 2017-04-19 (Wed, 19 Apr 2017)
Changed paths:
M hypervisor/Makefile
Log Message:
-----------
core: Rework architecture subdir build
Avoid the recursive make invocation just to express the dependency of
the arch tree on the generated asm-defines.h. We can do better than
that.
The trick is to let the subdir depend on the asm-defines.h, and the
built-in.o on the subdir, with proper obj prefixes. But just like for
the generated files, do not create the dependency if we are cleaning up,
that would fail.
Rename the defines-file variable at this chance to something more
meaningful.
We can furthermore clean up the dependencies: asm-defines.h is for
assembly only, and that lives in the arch subdir. So there is no need to
make the CORE_OBJECTS depend on that header.
Signed-off-by: Jan Kiszka <[email protected]>
Commit: c3d2808fdb3bf0759fc46f2cfa98ab440b062288
https://github.com/siemens/jailhouse/commit/c3d2808fdb3bf0759fc46f2cfa98ab440b062288
Author: Henning Schild <[email protected]>
Date: 2017-04-19 (Wed, 19 Apr 2017)
Changed paths:
M driver/main.c
Log Message:
-----------
driver: create new function to undo firmware mapping
Replacing vunmap with a function that allows us to do more than
just vunmap whenever we free that memory. That prepares for a later
patch that exposes the hypervisor image via sysfs.
Signed-off-by: Henning Schild <[email protected]>
Tested-by: Ralf Ramsauer <[email protected]>
Signed-off-by: Jan Kiszka <[email protected]>
Commit: b336a2935dffd40649f660c65440c704fddfd3e4
https://github.com/siemens/jailhouse/commit/b336a2935dffd40649f660c65440c704fddfd3e4
Author: Henning Schild <[email protected]>
Date: 2017-04-19 (Wed, 19 Apr 2017)
Changed paths:
M driver/main.c
Log Message:
-----------
driver: keep the firmware mapped after "disable"
We used to unmap the firmware image right after "jailhouse disable".
Change that and keep the firmware mapped until we exit the module or
restart jailhouse. This way we can look into the firmware that just ran.
This will be used by later patches.
Signed-off-by: Henning Schild <[email protected]>
Tested-by: Ralf Ramsauer <[email protected]>
Signed-off-by: Jan Kiszka <[email protected]>
Commit: 6efdd17c8bf5aa197cd78e711dbb7e1f8425b648
https://github.com/siemens/jailhouse/commit/6efdd17c8bf5aa197cd78e711dbb7e1f8425b648
Author: Henning Schild <[email protected]>
Date: 2017-04-19 (Wed, 19 Apr 2017)
Changed paths:
M driver/main.c
M driver/main.h
M driver/sysfs.c
M driver/sysfs.h
Log Message:
-----------
driver: make the firware visisble in sysfs
Make the "used, dirty" firmware image visible in sysfs. The data segment
contains data that could be useful for all sorts of debugging tools.
This feature is introduced to extract code coverage information (gcov).
Signed-off-by: Henning Schild <[email protected]>
Tested-by: Ralf Ramsauer <[email protected]>
[Jan: remove conditionals from core_show - risk of deadlock]
Signed-off-by: Jan Kiszka <[email protected]>
Commit: 1f9d18422b210339f7f730dfdef50a2f320fbef1
https://github.com/siemens/jailhouse/commit/1f9d18422b210339f7f730dfdef50a2f320fbef1
Author: Henning Schild <[email protected]>
Date: 2017-04-19 (Wed, 19 Apr 2017)
Changed paths:
A hypervisor/arch/arm/include/asm/jailhouse_header.h
M hypervisor/arch/arm/include/asm/jailhouse_hypercall.h
A hypervisor/arch/arm64/include/asm/jailhouse_header.h
A hypervisor/arch/x86/include/asm/jailhouse_header.h
M hypervisor/arch/x86/include/asm/jailhouse_hypercall.h
M hypervisor/hypervisor.lds.S
M hypervisor/include/jailhouse/header.h
Log Message:
-----------
core: move JAILHOUSE_BASE into a generic header
Move it out to a header that can be included by a tool, without
pulling in too many hypervisor internals.
That will be used by the gcov tool so we do not need to include
the value in the hypervisor binary.
Signed-off-by: Henning Schild <[email protected]>
Tested-by: Ralf Ramsauer <[email protected]>
Signed-off-by: Jan Kiszka <[email protected]>
Commit: 6bd02b73d7b9ca1b3c46eb212f4165081e48e336
https://github.com/siemens/jailhouse/commit/6bd02b73d7b9ca1b3c46eb212f4165081e48e336
Author: Henning Schild <[email protected]>
Date: 2017-04-19 (Wed, 19 Apr 2017)
Changed paths:
M hypervisor/Makefile
M hypervisor/arch/arm-common/Kbuild
M hypervisor/arch/arm/Kbuild
M hypervisor/arch/x86/Kbuild
A hypervisor/gcov.c
M hypervisor/hypervisor.lds.S
A hypervisor/include/jailhouse/gcov.h
M hypervisor/include/jailhouse/header.h
M hypervisor/setup.c
Log Message:
-----------
hypervisor: introduce GCOV support
This introduces pretty minimal GCOV support. The hypervisor does not
need to understand much of that. It just needs to call the init
functions to gather the addresses of the gcov related data structures.
These are just linked together so something outside the hypervisor can
look at them later.
Signed-off-by: Henning Schild <[email protected]>
Tested-by: Ralf Ramsauer <[email protected]>
[Jan: Remove .gcno clean-files rule - done by kbuild]
Signed-off-by: Jan Kiszka <[email protected]>
Commit: 6462339477171b1d9459a18b934b0939f31b6947
https://github.com/siemens/jailhouse/commit/6462339477171b1d9459a18b934b0939f31b6947
Author: Henning Schild <[email protected]>
Date: 2017-04-19 (Wed, 19 Apr 2017)
Changed paths:
M .gitignore
M hypervisor/Makefile
M tools/Makefile
A tools/jailhouse-gcov-extract.c
Log Message:
-----------
tools: new tool to get gcov data out of dirty firmware
With the new feature to download the used firmware out of sysfs and
a way to get GCOV data into that. It is now time to extract this
information and generate .gcda files for higher level tools to work
with.
Instead of dealing with the details of that just use what the
compiler gives us when we link to its gcov lib.
Signed-off-by: Henning Schild <[email protected]>
[Jan: clean .gcda files, fix usage of error(),
fix signed/unsigned comparison]
Signed-off-by: Jan Kiszka <[email protected]>
Commit: 168e10006660b4232010c5ade104e41100e010f9
https://github.com/siemens/jailhouse/commit/168e10006660b4232010c5ade104e41100e010f9
Author: Henning Schild <[email protected]>
Date: 2017-04-19 (Wed, 19 Apr 2017)
Changed paths:
A Documentation/gcov.txt
M Documentation/hypervisor-configuration.md
Log Message:
-----------
Documentation: add GCOV code coverage documentation
Signed-off-by: Henning Schild <[email protected]>
Signed-off-by: Jan Kiszka <[email protected]>
Commit: c2d1e3a574acd8b23fc7a144961c8c5806422ffd
https://github.com/siemens/jailhouse/commit/c2d1e3a574acd8b23fc7a144961c8c5806422ffd
Author: Jan Kiszka <[email protected]>
Date: 2017-04-19 (Wed, 19 Apr 2017)
Changed paths:
M ci/build-all-configs.sh
Log Message:
-----------
ci: Parallelize the build
We have at least 2 cores per builder, use them all.
Signed-off-by: Jan Kiszka <[email protected]>
Compare:
https://github.com/siemens/jailhouse/compare/913dfb45604f...c2d1e3a574ac
--
You received this message because you are subscribed to the Google Groups
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.