| History log of /src/tests/sys/uvm/t_uvm_physseg.c |
| Revision | | Date | Author | Comments |
| 1.11 |
| 26-Jul-2022 |
andvar | s/fucntion/function/ in comments.
|
| 1.10 |
| 03-Sep-2021 |
andvar | s/existant/existent/ in comments and messages, plus few more similar fixes.
|
| 1.9 |
| 13-Aug-2021 |
andvar | s/bacause/because/
|
| 1.8 |
| 16-Jan-2019 |
fox | 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>
|
| 1.7 |
| 16-Jan-2019 |
fox | 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>
|
| 1.6 |
| 16-Jan-2019 |
fox | 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>
|
| 1.5 |
| 16-Jan-2019 |
fox | Fixed the build failures caused by incompatible type comparisons when
VM_PHYSSEG is > 1.
Reviewed by <cherry>
|
| 1.4 |
| 18-Dec-2018 |
fox | Fixed the build failures caused by incompatible type comparisons.
Reviewed by <cherry>
|
| 1.3 |
| 08-Feb-2018 |
dholland | branches: 1.3.2; 1.3.4;
Typos.
|
| 1.2 |
| 22-Dec-2016 |
cherry | branches: 1.2.2;
convention about function names for predicate checking:
s/uvm_physseg_valid()/uvm_physseg_valid_p()/
per. matt@
|
| 1.1 |
| 19-Dec-2016 |
cherry | 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
|
| 1.2.2.2 |
| 07-Jan-2017 |
pgoyette | Sync with HEAD. (Note that most of these changes are simply $NetBSD$
tag issues.)
|
| 1.2.2.1 |
| 22-Dec-2016 |
pgoyette | file t_uvm_physseg.c was added on branch pgoyette-localcount on 2017-01-07 08:56:56 +0000
|
| 1.3.4.1 |
| 10-Jun-2019 |
christos | Sync with HEAD
|
| 1.3.2.2 |
| 18-Jan-2019 |
pgoyette | Synch with HEAD
|
| 1.3.2.1 |
| 26-Dec-2018 |
pgoyette | Sync with HEAD, resolve a few conflicts
|
