document scheduled removal as 14.0 as suggested.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Mar 23 2021
Document plan for removal as 14.0
In D29385#658103, @cem wrote:Please update the manual page (which refers to 2^32 now, despite the previously-wrong file comment mentioning 2^31) along with this change.
Updates random.9 man page
Jan 16 2020
I did a couple of experimentation, and bit 0x20 of io-reg 0x61 seems entirely controlled by the chipset "timer-8254" counter2 functionality. You can reset it to zero with "outb(0x43, 0xb0)" and check the effect on inb(0x61) . I don't think it is possible for ipmi/bmc to have any control over it, so it might not be a suitable bit to use to discriminate the possible origin of a NMI.
Sep 26 2019
Jun 6 2019
Thanks for review.
Minor mostly cosmetic improvements.
Jun 5 2019
Remove spurious comment.
Mar 26 2019
Just pushed style fixes.
- Style fixes.
Mar 23 2019
In D19648#420593, @jhb wrote:I'm curious which hypervisor you have tested this under and did you consider using one of the virtualized clocks if one was available? I know that there are some early patches to add kvmclock support to bhyve for example.
Updating D19648: Add/enable option to allow tsc as timecounter for VM