Lines Matching refs:in

13 operating system getting involved in between. Bios-bits has python integration
14 with grub so actual routines that executes bios components can be written in
16 There are several advantages to directly testing the bios in a real physical
17 machine or in a VM as opposed to indirectly discovering bios issues through the
21 complicated software component such as an operating system coming in between.
23 SMBIOS without being in the highest hardware privilege level, ring 0 for
24 example in case of x86. Since the OS executes from ring 0 whereas normal user
25 land software resides in unprivileged ring 3, operating system must be modified
26 in order to write our test routines that exercise and test the bios. This is
27 not possible in all cases. Lastly, test frameworks and routines are preferably
30 low level assembly machine language. Writing test routines in a low level
34 in 2011 <Plumbers_>`__ and `at Linux.conf.au in 2012 <Linux.conf.au_>`__.
36 For QEMU, we maintain a fork of bios bits in `gitlab`_, along with all
75    test failures. This is the script one would be interested in if they wanted
81    the entire log from bios bits and more information in case failure happens.
87    build directory (assuming that the sources are in ".."):
94    The above will run all acpi-bits functional tests (producing output in
97    You can inspect the log files in tests/functional/x86_64/test_acpi_bits.*/
98    for more information about the run or in order to diagnoze issues.
99    If you pass V=1 in the environment, more diagnostic logs will be put into
110    provided in the file itself.
115    the biosbits environment in the spawned VM. New additions of test cases can
116    be made in the appropriate test file. For example, new acpi tests can go
120    test that belongs to a test suite not already present in this directory. To
128    example, in order to change cpuid related tests, copy the following
145    The tests have an extension .py2 in order to indicate that: