#
ecf1f782 |
|
14-May-2018 |
Brett Wilson <brettw@chromium.org> |
[test] Rename test-threads to thread-functions. The old naming meant that there were two threads.h and threads.cpp files in the threads test directory tree. The new naming makes it more clear that the file contains the functions used to run the backround threads for the tests. Change-Id: I320fdb73fd7ed5978a3279a4715ef083ecab185c
|
#
c43458c9 |
|
08-May-2018 |
Brett Wilson <brettw@chromium.org> |
[threads][utest] Convert threads test to C++. I want this in particular because I want to write a scoper object to register for the debug exception port. Otherwise, the tests will corrupt everything after them when they fail. Change-Id: I0626c44f548495e65a64b48e1ea8aaeb65af2f09
|
#
f3e2126c |
|
12-Sep-2017 |
Roland McGrath <mcgrathr@google.com> |
[zx] Magenta -> Zircon The Great Renaming is here! Change-Id: I3229bdeb2a3d0e40fb4db6fec8ca7d971fbffb94
|
#
6527edea |
|
05-Aug-2017 |
Mark Seaborn <mseaborn@google.com> |
[utest][threads] Add test for register values reported for a suspended thread This checks that all the register values are reported correctly. We launch a thread that sets all registers to test values and spins, then we suspend the thread and check its register state. This doesn't cover extended registers (FP, SSE/AVX, Neon, etc.), which aren't readable by mx_thread_read_state() yet. Change-Id: Ie9f31d8fdcd6f7692d5bd53eb350ffb318c705c1
|
#
79b42055 |
|
14-Jun-2017 |
Todd Eisenberger <teisenbe@google.com> |
[utest][threads] Improve discipline around thread handle access Previously code attempting to grab thread handles was potentially racy in some places. Also adds tests for mxr_thread_detached(). Change-Id: I272c87ab56397d99daabafcad6e12e80a84a2f65
|
#
70435694 |
|
19-Apr-2017 |
Yvonne Yip <yky@google.com> |
[utest] run magenta tests in groups Assign a group to magenta tests, and run tests in order of increasing complexity, and abort the test if a group failed. This is because if there is a bug in a core magenta facility, it could cause all higher level tests to fail. The current groups are: * "core": tests on kernel facilities * "ddk": ddk tests * "sys": general magenta system tests (default) * "fs": filesystem tests Set the group in the tests' rules.mk by setting the MODULE_USERTEST_GROUP variable. runtests accepts a list of groups to run. If none is specified, run all tests. Change-Id: Ia363d25f5c1c828a3d1a9abf586170bb90c679f7
|
#
16656ae0 |
|
05-Apr-2017 |
Brian Swetland <swetland@google.com> |
[build] flatten the build Previously we treated kernel/, system/, and third_party/ as overlays on a shared namespace. This required the concept of "canonical" module names, and a lot of complexity to ensure that things didn't collide and the build worked. This change gets rid of that, no longer passes -I to make, so that include directives from our *.mk files do not magically wildcard across various paths, etc. The most user-visible change is that everywhere where a module name is specified (MODULE_DEPS, MODULE_LIBS, etc), full module names like kernel/lib/io or system/ulib/mxio must be used instead of previously-allowed "short" names like lib/io and ulib/mxio. The build output still has a similar shape, but the first segment of the module path (kernel/, system/, or third_party/) is no longer elided under $(BUILDDIR) Change-Id: I525aba1da1c86eb7a86007bddc669f7eeebfedd5
|
#
12242caa |
|
07-Mar-2017 |
Brian Swetland <swetland@google.com> |
[build][musl] refer to musl libc as ulib/c This makes the build rules and the intermediate output files easier to understand, without having to modify the path where musl libc lives. The biggest observeable difference is the build intermediate files: $ ls build-magenta-pc-x86-64/ulib/c config-module.h libc.abi.h libc.abi.stamp libc.so libc.so.id libc.so.strip libc.a libc.abi.o libc.a.opts libc.so.abi libc.so.opts third_party which previously were at build-magenta-pc-x86/ulib/musl and named libmusl.* and the replacing of ulib/musl with ulib/c in the library dependencies of all the rules.mk files (the vast bulk of this change) Change-Id: If9c5d522099d2c9ac5bdb666b8e67a2eb3d316ee
|
#
24f6c9c0 |
|
09-Jan-2017 |
George Kulakowski <kulakowski@google.com> |
[tests][core] Don't link test-utils in core tests Change-Id: I65aea23dfc628230eb32af8dce0ecfbff30da938
|
#
bea41c57 |
|
01-Aug-2016 |
Travis Geiselbrecht <travisg@google.com> |
[kernel][magenta] switch thread/process creation syscalls to a two phase api -In both thread and process creation apis, require user space create the object first, then start it with additional args -For threads stack allocation is also moved to user space -Wire up the process/thread handles to be transferred through to new processes Change-Id: I43d447c86af1ab3199d8dcf29ff4fe3a384b6e65
|
#
66a201f1 |
|
16-Aug-2016 |
Brian Swetland <swetland@frotz.net> |
[system] align license and license banners with Fuchsia This adjusts the Magenta userspace code to match the prevailing license in Fuchsia (three-clause BSD), using the same banner and license text. Change-Id: I6b6d79435c5dbaa32027888874849e4f47aaa7be
|
#
f358d68e |
|
29-Jul-2016 |
Brian Swetland <swetland@google.com> |
[build] make musl-static the exception rather than musl-shared This makes the common uapp, ulib, or utest rules.mk much more comprehensible. Some day we'll eliminate the need for -static entirely, but that requires some deeper refactoring. Change-Id: Ifcdb635e5af7bf0b033632358164c3042e7e6d4a
|
#
33d4a51b |
|
29-Jul-2016 |
Brian Swetland <swetland@google.com> |
[build] make dynamic linking the default Now userapp/usertest modules are dynamic, and to build a static binary userapp-static or usertest-static are used. Change-Id: Ifd16f40a2bf23202ec17f3142f896abdec1c3271
|
#
1ba4b288 |
|
28-Jul-2016 |
Roland McGrath <mcgrathr@google.com> |
[uapp] [utest] Switch most uapp and utest builds to dynamic linking Nearly every uapp and utest that can be dynamically linked is now. The mxr-tls test is omitted because it's broken when dynamically linked; that will probably be moot after the forthcoming TLS revamp. A few test helper programs cannot use dynamic linking as written because they get run with a nonstandard bootstrap message that does not include the magic required for the dynamic linker's startup. I didn't touch anything using ulib/ddk because I didn't bother to figure out how that fits together. Change-Id: I93b08960d946e23cd4ac89216e6d32789f99405a
|
#
39b3f217 |
|
19-Jul-2016 |
Ankur Mittal <anmittal@google.com> |
[utest] Support categories This will produce single binary from mxr tests and also seperate binary for each test Change-Id: I9345fbeab5751dda356cfd47a766c09957211923
|