Age | Commit message (Collapse) | Author |
|
Adapted from FreeBSD's test suite by attila () stalphonsos ! com.
Minor tweaks:
* make tests work properly with 'make obj' and setting VERBOSE
* add 10 tests checking some examples in our man page
* disable the dddd test for now since it loops forever
Besides dddd, the following five tests fail: dhhd dhhd2 wp3 wp4 wp5
Suggested fixes for these are on tech@
Many thanks to attila for doing the hard work!
|
|
will be enabled after committing in src/usr.bin/mandoc
|
|
for jumbo frame support.
|
|
|
|
handling ATAGS and cleanup the early boot code.
ok patrick@, tom@, jsg@
|
|
|
|
|
|
ok millert@ kettenis@
|
|
|
|
|
|
In the Netfront case it appears that by having scheduler decide when
to run the workload we don't need to involve additional mechanisms
to artificially limit resource availability to achieve better
performance under heavy load. On the contrary, by performing a
single pass through Rx and Tx completion rings and having scheduler
decide when to run the next attempt, we limit the amount of time
spent in the packet processing and achieve system responsiveness.
|
|
Handling receive and transmit for multiple networking interfaces
in a "shared interrupt" within normal interrupt vector code path
introduces too much delay from the hypervisor POV which prevents
it from injecting further completion event interrupts for Rx and
Tx queues.
Additionally, Netfront backend driver includes a mechanism to
detect Rx ring stalls and "turn the carrier off" when the guest
is not replenishing the ring (e.g. due to missing completion
interrupts) that relies on guest waking up periodically and making
sure that the Rx ring completion handling is progressing.
Having tried both task queue + timeout and interrupts + timeout
approaches, it appears that using the task queue is more flexible
and provides superior performance under heavy network load.
|
|
|
|
callers should probably check too, but checking here won't hurt.
possible panic reported by tim newsham.
ok kettenis
|
|
in some cases.
|
|
ok deraadt millert
|
|
|
|
|
|
|
|
from remi locherer
|
|
If a VM exits, terminate it and remove it from the list of
available VMs. That allows a VM with name `foo' to be restarted
after it has exited.
This changes structures shared between vmd and vmctl. You need to
rebuild vmctl also.
ok mlarkin@
|
|
(btw. hostated-hoststated-relayd's 10th birthday is on Dec 16.)
|
|
Found and tested by Michael Lechtermann
OK benno@
|
|
ok gilles@
|
|
we will run into translation faults.
ok tom@
|
|
Tested by and ok mglocker@
|
|
acpicpu(4) drivers to the right cpu(4).
ok mlarkin@, guenther@
|
|
calls. if we need a big space once, we'll likely need a big space again.
|
|
|
|
|
|
|
|
|
|
Too bad this highly critical bugfix will miss release.
okay deraadt@
|
|
that i misunderstood something when i wrote it;
found by guenther and naddy
|
|
|
|
|
|
|
|
Found by David Hill with clang.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ok kettenis@, patrick@
|
|
allowed you to pass a virtual address, which you received from an
early bootstrap mapping, as physical address to bus_space_map(9).
It breaks bus_space_map(9) for peripherals that are after 0xC0000000,
as it assumes that everything after that address cannot be a real
peripheral. But that's wrong. It does not make sense to pass a
virtual address to bus_space_map(9) anyway, so just get rid of this
whole "feature".
ok kettenis@
|
|
ok patrick@
|
|
|
|
removed from pmaps it currently is in. To check if a virtual address
pointing to that physical page has been mapped, the code uses
the l2pte_valid() function. Unfortunately there is a difference
between being valid and the PTE being zero. If a page is mapped
but has never been accessed, it will be non-zero but invalid.
In that case the PTE for that virtual address will not be zeroed
and the virtual address will be removed from the vm page struct.
The next time someone tries to map a page to that virtual address,
other pmap code will consider the virtual address to be already
mapped, even though that assumption is completely wrong.
To make sure this does not happen, check the PTE for zero. This way
the PTE will be zeroed correctly. The check for zero is how other
ARM pmap code also handles this issue.
ok kettenis@ tom@
|
|
ok beck deraadt guenther
|