Age | Commit message (Collapse) | Author |
|
|
|
function has been fixed.
Functions passed to rtable_walk() must return EAGAIN if they delete an
entry from the tree, no matter if it is a leaf or not.
|
|
Previously the code was "too clever" and returned EAGAIN only for
cloning route assuming that other deletion did not modify the tree.
Analysed by and ok dlg@
|
|
state key is linked to a socket inp.
OK mpi@ henning@
|
|
anycast address.
This will allow us to split ip6_input() in two parts using a queue
in the middle.
ok jca@, florian@, bluhm@
|
|
to the end of the defer structure. solves sizing and alignment concerns.
|
|
For virtio devices, ignore the black/white-listing depending on the PCI
bridge. This enables MSI-X with qemu's old "82441FX" pci-bridge.
Suggested by kettenis@
|
|
in pmap_free_l1().
from aalm@ - thanks
ok patrick@
|
|
to store a field in an extra variable that is only accessed twice.
OK mpi@
|
|
least this is what Linux does and it fixes a hang on the Olimex A10s boards.
While there, also preserve the clock selection when reloading the timer.
ok patrick@, jsg@, tom@
|
|
|
|
didn't attach previously on OMAP4 with the static device configuration
and now do with the fdt. Like most of the other OMAP4 prcm cases
these don't do anything, hopefully we'll properly configure clocks with
data from the fdt at some point in the future.
Tested by abieber@ on PandaBoard-ES.
|
|
just use the pv_flags. ('Twas a copy-paste from arm's pmap_clean_page(),
which did need it.)
Also remove even less used flags variable from pmap_page_remove().
First part from a diff from aalm@ - thanks
ok kettenis@ "looks good" patrick@
|
|
OK mpi@ sashan@
|
|
Tx aggregation), instead of the maximum (63 frames). Tx aggregation should
already be disabled, so this change should be a no-op. It just avoids any
side effects in case the firmware happens to interpret the limit we set here.
ok mpi@
|
|
data frames above a certain length, but we were setting it for !data frames
above a certain length, which makes no sense at all. Found while comparing
our driver's Tx code to iwlwifi.
ok mpi@
|
|
frames the same number of times as Linux iwlwifi does.
|
|
be used to translate one memory address to another. Currently we just
pass the child's memory address to bus space map. If one of the parent
busses implements a ranges property, the child's address property is
not the real address. This change hooks up a bus space map function
that is aware of the ranges property and translates the addresses if
needed.
ok kettenis@
looks fine jsg@
|
|
device tree like we do on omap. Add preliminary support for the sun5i
variant which corresponds to the A13 and A10s SoCs.
ok patrick@
|
|
pinctrl-single,pins to handle mux settings and pad configuration.
The fdt data has offsets from the start of the pinmux address range so
the am335x specific pinmux offset from the scm base is added to the
offsets. This as not a new driver as sitaracm does manual table
driven pad configuration for gpio. If all the offsets in the
ti_padconf_devmap table were reduced by the am335x pinmux offset (0x800)
it may make sense to map only the pinmux memory region and not the
scm superset.
looks good kettenis@
|
|
|
|
ok kettenis@ on an earlier version
|
|
ok kettenis@
|
|
(reducing the number of XXXs in vmm)
|
|
This increases performance for interrupt heavy loads.
While suspend/resume support for MSI-X is missing, this is also missing for
virtio. So no new issue there.
Currently, qemu's old "82441FX" pci-bridge is still blacklisted for MSI. But
MSI-X is used if qemu is started with "-M q35".
|
|
|
|
They are unused and equivalent to disableintr() and setsr().
While here, clean up a few other leftovers.
|
|
s/names are this level/names at this level/
from aalm@ - thanks
|
|
ok jsg@
|
|
are handled during cpu hatch.
|
|
list storage size. Noticed when attempting to get vmm(4) to nest under
Hyper-V.
|
|
anyway due to a missing #include.
the code was originally intended to handle i386 SMP EISA machines with an
IOAPIC. Since the code never was compiled, and nobody has noticed or
complained for 12 years, I think things are probably fine.
|
|
|
|
clkbase to be set to 0 (if it wasn't all commented out anyway).
ok patrick@
|
|
ok krw@
|
|
"another leftover of the bean counter"
od tedu@ deraadt@
|
|
issues can be worked out, otherwise this driver will cause the
kernel to spin forever on certain chromebooks
|
|
|
|
This prevents from too small amaps being allocated by
forcing the allocation of a large number of slots.
Based on an analysis from Jesse Hertz and Tim Newsham.
ok kettenis@
|
|
program to call the mount/umount system calls. There is no way any user
can be expected to keep their system safe / reliable with this feature.
Ignore setting to =1, and after release we'll delete the sysctl entirely.
ok lots of people
|
|
destination as per RFC4213.
We're not in 1999 anymore, what was earlier a "stronger check than
RFC1933" is now a best practice. This matches the behavior of the
reject (R) routes added by default by netstart(8).
ok jca@, florian@, claudio@, bluhm@
|
|
PHYs based on device tree properties instead of the board ID. Untested as
I don't have the hardware.
ok jsg@, patrick@
|
|
removed from the table.
Currently the storage for L2 addresses is freed when an entry is
removed from the table. That means that we cannot access this
chunk of memory between RTM_DELETE and rtfree(9).
Note that this doesn't apply to MPLS because the associated storage
is currently released by the last rtfree(9).
ok mikeb@
|
|
The only way to ensure that the device does not do DMA for the timed out
request is a device reset.
Also increase the timeout to 15s
|
|
This describes more accurately what it is good for.
Also introduce a virtio_poll_intr macro.
|
|
For MSI-X (and also possibly for other transports), the interrupt
handler must do different things. Move it out of virtio.c and into
virtio_pci.
ARM part tested by patrick@
|
|
ok millert@ kettenis@
|
|
ok tedu@
|
|
permitted very big mallocs to panic the kernel.
reported by Tim Newsham
ok millert@
|
|
quirk: uint64 to int32 truncation can lead to false positives, and then
later in the array sizing code, very big mallocs panic the kernel.
add a check that the ident isn't larger than INT_MAX in the fd case.
reported by Tim Newsham
|