| Age | Commit message (Collapse) | Author |
|---|
|
Instead extend fusefs_node with the few required fields.
Tested by kirill@ with input from miod@
OK beck@
|
|
|
|
ok mpi@ miod@
|
|
ok deraadt
|
|
(corrected)
|
|
|
|
ok deraadt@
|
|
|
|
|
|
|
|
saves space on ramdisks that have option NFSCLIENT
initial diff from and ok miod@
|
|
'fine with me' hshoexer, ok bluhm@
|
|
you can basically plug rdomains together and route between them
over rport interfaces. people keep asking me if this is so you can
leak routes between rdomains, and the answer is yes.
this is like pair(4) but cheaper because it avoids all the mucking
around with putting an ethernet header on the mbuf just to take it
off again later, and is more efficient with address space because
it's a p2p ip interface.
it has a small tweak from mvs@
ok denis@ claudio@
|
|
`maxfiles' is atomically accessed integer which is lockless and
read-only accessed in file descriptors layer.
lim_startup() called during kernel bootstrap, no need to
atomic_load_int() within.
ok mpi
|
|
`maxprocess' and `maxthread' are atomically accessed integers.
ok mpi
|
|
This driver is not working yet, it's a copy of qwx(4) which bit-by-bit will be
adjusted to work on the newer generation of chips. Even though this is only a
minor bump over the previous generation, the changes are large enough that
bringup, debugging and long-term maintenance would suffer trying to squash them
into a single driver. This can be reconsidered once we have reached a stable
state.
|
|
|
|
Use gre condition in conf/files for compiling netinet/ip_gre.c only
if needed. Remove #if NGRE > 0 from ip_gre.c that caused ramdisk
build to compile an empty C file.
OK kn@ deraadt@; input jsg@
|
|
Several commands for basic platform initialization and launch of
SEV/SEV-ES enabled guests are implemented. These can be used by
e.g. vmd(8) later.
from hshoexer@; OK mlarkin@
|
|
code. Remove obsolete comment while here as pointed out by kettenis@.
ok kettenis@
|
|
Code that used it was removed in February.
|
|
|
|
These have been superseded by inlines from endian.h.
ok miod@ mpi@
|
|
OK deraadt@
|
|
|
|
ok deraadt@
|
|
|
|
|
|
Softdep has been a no-op for some time now, this removes it to get
it out of the way.
Flensing mostly done in Talinn, with some help from krw@
ok deraadt@
|
|
|
|
Syskaller has hit the assertion "dtlookup(unit) == NULL" by opening
dt(4) device in two parallel threads. Convert kassert into if
condition. Move check that device is not used after sleep points
in malloc. The list dtdev_list is protected by kernel lock which
is released during sleep.
Reported-by: syzbot+6d66c21f796c817948f0@syzkaller.appspotmail.com
OK miod@
|
|
an MD basis.
ok patrick@
|
|
This driver is not working yet. Scanning almost works but a lot more
work remains to be done. So far most of the porting work was done by
myself, with some help from mpi, patrick, and kettenis.
Obviously this driver remains disabled for now. Enable relevant lines
in the kernel config if you want to help out with development.
At present firmware files must be obtained manually and placed
in the directory /etc/firmware/qwx/WCN6855/hw2.1/
This will be improved later.
Thanks to the OpenBSD Foundation for supporting this effort.
|
|
From Mike Barcroft in FreeBSD. Added to FreeBSD in 2001, Linux in 2010.
Used in amdgpu.
ok deraadt@
|
|
Since revision 1.26 dt_ioctl_get_auxbase() is calling process_domem().
Build the latter function into kernel if pseudo device dt is enabled.
from Matthias Pitzl; OK claudio@
|
|
OK deraadt@
|
|
OK deraadt@
|
|
|
|
|
|
|
|
|
|
this makes #include "sec.h" and #if NSEC > 0 work in kernel code.
|
|
ok kn@ bluhm@
|
|
The OnChip System Fabric is mostly an implementation detail on a
bunch of Intel SoC platforms we usually don't care about, except
on some of these machines there are devices shared between the
kernel and the platform that need to coordinate. The iosf(4) driver
allows the kernel to talk via a mailbox interface to take and
release a semaphore that the hardware also uses to lock around
accesses to some components.
There are two ways to talk to the mailbox interface, one via mmio
ops on an INT33BD acpi device. The other is via magic pci conf space
operations on the pci host device. This provides a generic iosf
driver with attachment glue for both acpi and pci so either can be
used. According to linux, the pci ops are a lot more reliable and
less buggy, so if both acpi and pci are available we will prefer
the pci ops after they attach.
I found this because I got a Dell Wyse 3040, which is a cherry
trail/braswell system that has an acpitz(4) which talks to a tipmic(4)
device attached to dwiic(4) on acpi. This box almost always locked
up by the time it got to showing the console login prompt, and it
turns out one of the reasons for this is because acpitz was touching
the tipmic device at the same time the powerunit on the platform
was also trying to use it. The tipmic device lists the iosf mailbox
as a dependency, and the dwiic controller has a _SEM property, both
of which indicate we should use an iosf device to coordinate iic
ops when talking to the tipmic.
This adds the code, but doesn't wire it into dwiic or the build yet.
help from patrick@ jsg@ kettenis@
ok kettenis@ patrick@
|
|
|
|
|
|
|
|
ok deraadt@
|
|
|
|
|
