| created | 2023-01-01T08:19:21Z |
|---|---|
| begin | 2022-12-26T00:00:00Z |
| end | 2022-12-27T00:00:00Z |
| path | src/sys |
| commits | 5 |
| date | 2022-12-26T04:09:14Z | |||
|---|---|---|---|---|
| author | asou | |||
| files | src/sys/dev/pv/vmt.c | log | diff | annotate |
| message | Add close vmt. | |||
| date | 2022-12-26T19:14:18Z | |||
|---|---|---|---|---|
| author | miod | |||
| files | src/sys/arch/macppc/dev/akbd_machdep.c | log | diff | annotate |
| message |
Update adb_polling in akbd_cnpollc rather than akbd_cngetc; repairs ddb input on adb machines. |
|||
| date | 2022-12-26T19:17:00Z | |||
|---|---|---|---|---|
| author | miod | |||
| files | src/sys/arch/macppc/dev/adb.c | log | diff | annotate |
| message |
send_adb_cuda() would assume the returned value of splhigh() is the macintr interrupt enable register; this used to be true more than 20 years ago but the interrupt code has changed a lot since, and it is nevertheless bad practice from md drivers to know to much about spl*() return values. The check should become a "spl >= IPL_TTY", but management of the adb_polling variable is good enough to need this at all. |
|||
| date | 2022-12-26T19:25:49Z | |||
|---|---|---|---|---|
| author | miod | |||
| files | src/sys/kern/vfs_subr.c | log | diff | annotate |
| message |
Replace two (void)copystr(..., NULL) with equivalent (void)strlcpy() calls. ok millert@ |
|||
| date | 2022-12-26T23:50:20Z | |||
|---|---|---|---|---|
| author | dv | |||
| files | src/sys/arch/amd64/amd64/vmm.c | log | diff | annotate |
| src/sys/arch/amd64/include/vmmvar.h | log | diff | annotate | |
| message |
vmd(8): provide a detailed e820 memory map. When booting guests with SeaBIOS, vmd(8) supplied details about the available guest memory via CMOS registers. Consequently, we've been carrying some patches in the ports tree to SeaBIOS to fetch this information like it's the 1990s. When a vm initializes memory ranges, we now track what each range represents. This information can be used to supply the e820 memory map to SeaBIOS via the fw_cfg interface allowing it to properly communicate memory ranges to a guest operating system. (This will also allow us to drop some patches from the port.) Given the ranges can now be marked with a purpose, this also allows vmm(4) to switch from hard-coded mmio ranges and instead let the information on the memory range dictate if vmm should be handling a page fault or sending to vmd for a memory assist. Tested by Mischa Peters and others. OK mlarkin@. |
|||