| #
4fe34605 |
| 26-Jul-2022 |
andvar <andvar@NetBSD.org> |
s/fucntion/function/ in comments.
|
| #
11850c9e |
| 03-Sep-2021 |
andvar <andvar@NetBSD.org> |
s/existant/existent/ in comments and messages, plus few more similar fixes.
|
| #
6e3ee785 |
| 13-Aug-2021 |
andvar <andvar@NetBSD.org> |
s/bacause/because/
|
| #
4bfe81d9 |
| 16-Jan-2019 |
fox <fox@NetBSD.org> |
Fixed issues with uvm_page_physunload_delete_end test case.
1. "avail_start" and "start" were different, resulting in unreachable code in
uvm_page_physunload(), where the condition check "avail_star
Fixed issues with uvm_page_physunload_delete_end test case.
1. "avail_start" and "start" were different, resulting in unreachable code in
uvm_page_physunload(), where the condition check "avail_start" < "end" fails.
The test has been fixed by setting "avail_start" and "start" to the same value.
2. If "start" is the address with end address being "start + 2", we can
unplug twice, the first paddr_t would be "start" and the second one would be
"start + 1". Modified the ATF_CHECK_EQ() to reflect these changes.
Reviewed by <cherry>
show more ...
|
| #
66ea64ec |
| 16-Jan-2019 |
fox <fox@NetBSD.org> |
Fixed issues with uvm_physseg_atboot_free_leak test case.
"\n" in ATF discriptions make it behave in weird ways, like saying "this
test is bogus.", fixed the issue by removing the "\n".
Reviewed by
Fixed issues with uvm_physseg_atboot_free_leak test case.
"\n" in ATF discriptions make it behave in weird ways, like saying "this
test is bogus.", fixed the issue by removing the "\n".
Reviewed by <cherry>
show more ...
|
| #
ff43743a |
| 16-Jan-2019 |
fox <fox@NetBSD.org> |
Fixed issues with uvm_physseg_plug test case.
There is a condition check which failed for VM_PHYSSEG_MAX == 2 (not for
1 or 3 and above), in case of 2, pgs == slab + npages1 + npages3, so we
need to
Fixed issues with uvm_physseg_plug test case.
There is a condition check which failed for VM_PHYSSEG_MAX == 2 (not for
1 or 3 and above), in case of 2, pgs == slab + npages1 + npages3, so we
need to change ">" check to ">=" check.
Reviewed by <cherry>
show more ...
|
| #
497a8f2b |
| 16-Jan-2019 |
fox <fox@NetBSD.org> |
Fixed the build failures caused by incompatible type comparisons when
VM_PHYSSEG is > 1.
Reviewed by <cherry>
|
| #
a85205fc |
| 18-Dec-2018 |
fox <fox@NetBSD.org> |
Fixed the build failures caused by incompatible type comparisons.
Reviewed by <cherry>
|
| #
32cded6c |
| 08-Feb-2018 |
dholland <dholland@NetBSD.org> |
Typos.
|
| #
e6ff351e |
| 22-Dec-2016 |
cherry <cherry@NetBSD.org> |
convention about function names for predicate checking:
s/uvm_physseg_valid()/uvm_physseg_valid_p()/
per. matt@
|
| #
07acf3c0 |
| 19-Dec-2016 |
cherry <cherry@NetBSD.org> |
This is a preview of the uvm_hotplug(9) api code.
This commit does not actually introduce the UVM_HOTPLUG option.
However it does provide developers a way to review, test and try out
the API.
To do
This is a preview of the uvm_hotplug(9) api code.
This commit does not actually introduce the UVM_HOTPLUG option.
However it does provide developers a way to review, test and try out
the API.
To do this, please go to tests/sys/uvm/ and build and run the tests
there. The tests also have a set of basic load tests, to get a measure
of the performance penalties due to enabling the UVM_HOTPLUG option.
In order to build the tests you need to have at least done the
following in $SRC/
cd $SRC; $NBMAKE do-distrib-dirs includes
cd $SRC/lib/csu; $NBMAKE all install || exit
cd $SRC/external/gpl3/gcc/lib/libgcc/libgcc_s; $NBMAKE all install || exit
cd $SRC/external/gpl3/gcc/lib/libgcc/libgcc; $NBMAKE all install || exit
cd $SRC/lib/libc; $NBMAKE includes all install || exit
cd $SRC/lib/libpthread; $NBMAKE all install || exit
cd $SRC/lib/libm; $NBMAKE all install || exit
cd $SRC/external/gpl3/gcc/lib/libstdc++-v3/; $NBMAKE all install || exit
Once the development environment has these userspace libraries, one
can simple build using $NBMAKE and finally test the kernel API using
atf-run|atf-report
show more ...
|