| created | 2024-09-01T01:12:18Z |
|---|---|
| begin | 2024-08-27T00:00:00Z |
| end | 2024-08-28T00:00:00Z |
| path | src/sys |
| commits | 9 |
| date | 2024-08-27T09:16:03Z | |||
|---|---|---|---|---|
| author | bluhm | |||
| files | src/sys/arch/amd64/amd64/identcpu.c | log | diff | annotate |
| src/sys/arch/amd64/amd64/vmm_machdep.c | log | diff | annotate | |
| src/sys/arch/amd64/include/cpu.h | log | diff | annotate | |
| src/sys/arch/amd64/include/vmmvar.h | log | diff | annotate | |
| src/sys/dev/vmm/vmm.c | log | diff | annotate | |
| src/sys/dev/vmm/vmm.h | log | diff | annotate | |
| message |
Enable AMD SEV support in vmm(4). Bring the pieces for vmm(4) to support guests with SEV memory encryption on AMD CPUs. The corresponding vmd(8) changes will follow. Emulate cpuid 0x8000001f so the guest can discover SEV features. Allow vmd(8) to enable SEV on VM creation. Inform vmd(8) about the c-bit position and ASID assigned to each VCPU. Note that vmd(8) has to be rebuilt with the new header files. from hshoexer@; input dv@; OK mlarkin@ |
|||
| date | 2024-08-27T10:58:53Z | |||
|---|---|---|---|---|
| author | jsg | |||
| files | src/sys/dev/pci/drm/amd/amdgpu/amdgpu_drv.c | log | diff | annotate |
| src/sys/dev/pci/drm/radeon/radeon_drv.c | log | diff | annotate | |
| message | frambuffer -> framebuffer | |||
| date | 2024-08-27T12:31:18Z | |||
|---|---|---|---|---|
| author | sthen | |||
| files | src/sys/dev/usb/usbdevs | log | diff | annotate |
| message | add a few USB mice, to be used for quirks. ok bru miod | |||
| date | 2024-08-27T12:31:43Z | |||
|---|---|---|---|---|
| author | sthen | |||
| files | src/sys/dev/usb/usbdevs.h | log | diff | annotate |
| src/sys/dev/usb/usbdevs_data.h | log | diff | annotate | |
| message | sync | |||
| date | 2024-08-27T12:41:18Z | |||
|---|---|---|---|---|
| author | sthen | |||
| files | src/sys/dev/usb/usb_quirks.c | log | diff | annotate |
| message |
use UQ_ALWAYS_OPEN for various PixArt/Logitech USB mice. ok bru miod Some USB mice are known to have problems if the device isn't polled regularly (seems to be something in the firmware overflows). Symptoms are frequent disconnect/reconnect cycles unless either X or wsmoused are used. jcs and kurt figured out a related problem with the Surface Type Cover and added UQ_ALWAYS_OPEN in 2021 (similar to linux HID_QUIRK_ALWAYS_POLL and NetBSD UQ_ALWAYS_ON) which also works around the problem with these mice. I've added the list of vid/pid from NetBSD, plus the mouse which I've been having problems with which they didn't have. |
|||
| date | 2024-08-27T13:52:41Z | |||
|---|---|---|---|---|
| author | aisha | |||
| files | src/sys/net/pfvar.h | log | diff | annotate |
| message |
remove some dead code that wasn't cleaned up ok sashan |
|||
| date | 2024-08-27T18:44:12Z | |||
|---|---|---|---|---|
| author | sf | |||
| files | src/sys/dev/pv/if_vio.c | log | diff | annotate |
| src/sys/dev/pv/vioblk.c | log | diff | annotate | |
| src/sys/dev/pv/viocon.c | log | diff | annotate | |
| src/sys/dev/pv/viogpu.c | log | diff | annotate | |
| src/sys/dev/pv/viomb.c | log | diff | annotate | |
| src/sys/dev/pv/viornd.c | log | diff | annotate | |
| src/sys/dev/pv/vioscsi.c | log | diff | annotate | |
| src/sys/dev/pv/virtio.c | log | diff | annotate | |
| src/sys/dev/pv/virtiovar.h | log | diff | annotate | |
| message |
virtio: Remove some unused leftovers Some fields in struct virtqueue are unused. The maxsegsize argument to virtio_alloc_vq is unused. OK bluhm@ |
|||
| date | 2024-08-27T19:01:11Z | |||
|---|---|---|---|---|
| author | sf | |||
| files | src/sys/dev/fdt/virtio_mmio.c | log | diff | annotate |
| src/sys/dev/pci/virtio_pci.c | log | diff | annotate | |
| src/sys/dev/pv/virtiovar.h | log | diff | annotate | |
| message |
constify struct virtio_ops OK bluhm@ |
|||
| date | 2024-08-27T19:11:20Z | |||
|---|---|---|---|---|
| author | sf | |||
| files | src/sys/dev/pv/if_vio.c | log | diff | annotate |
| message |
vio: whitespace and message tweaks Fix whitespace. Other network drivers use a comma in the boot message. Make more clear what features are meant in an error message OK bluhm@ |
|||