Re: [v5] amd64: simplify TSC sync testing

2022-07-31 Thread Masato Asou
Hi, Scott. I tested v5 patch on my ESXi on Ryzen7. It works fine for me. $ sysctl -a | grep tsc kern.timecounter.hardware=tsc kern.timecounter.choice=i8254(0) acpihpet0(1000) tsc(2000) acpitimer0(1000) machdep.tscfreq=3593269150 machdep.invarianttsc=1 $ sysctl kern.timecounter kern.timecounter.ti

Re: [v5] amd64: simplify TSC sync testing

2022-07-31 Thread Masato Asou
Hi, Scott. Sorry, I missed v5 patch. I tested v5 patch on my Ryzen7 box. And I got failed message: $ sysctl -a | grep tsc kern.timecounter.choice=i8254(0) acpihpet0(1000) tsc(2000) acpitimer0(1000) machdep.tscfreq=3593259787 machdep.invarianttsc=1 $ sysctl kern.timecounter kern.timecounter.tick=1

Re: bioctl.8: noauto flag has no effect in bootloaders

2022-07-31 Thread Chris Cappuccio
Klemens Nanni [k...@openbsd.org] wrote: > Reading "at boot time" may come off as "in the bootloader" > -Do not automatically assemble this volume at boot time. > +Do not automatically assemble this volume at system startup time. I don't think this reads any different. If you want to be very clear

Re: [v4] amd64: simplify TSC sync testing

2022-07-31 Thread Masato Asou
Hi, Scott I tested your patch on my on ESXi on Ryzen7 box. It works fine for me. $ sysctl -a | grep tsc kern.timecounter.hardware=tsc kern.timecounter.choice=i8254(0) acpihpet0(1000) tsc(2000) acpitimer0(1000) machdep.tscfreq=3593261949 machdep.invarianttsc=1 $ sysctl kern.timecounter kern.timeco

Re: [v4] amd64: simplify TSC sync testing

2022-07-31 Thread Scott Cheloha
> On Jul 31, 2022, at 23:48, Masato Asou wrote: > > Hi, Scott > > I tested your patch on my Ryzen7 box. > And I got failed message: > > $ sysctl -a | grep tsc > kern.timecounter.choice=i8254(0) acpihpet0(1000) tsc(2000) > acpitimer0(1000) > machdep.tscfreq=3593244667 > machdep.invarianttsc=1 >

Re: [v4] amd64: simplify TSC sync testing

2022-07-31 Thread Masato Asou
Hi, Scott I tested your patch on my Ryzen7 box. And I got failed message: $ sysctl -a | grep tsc kern.timecounter.choice=i8254(0) acpihpet0(1000) tsc(2000) acpitimer0(1000) machdep.tscfreq=3593244667 machdep.invarianttsc=1 $ sysctl kern.timecounter kern.timecounter.tick=1 kern.timecounter.timeste

riscv64: trigger deferred timer interrupts from splx(9)

2022-07-31 Thread Scott Cheloha
Hi, I am unsure how to properly mask RISC-V timer interrupts in hardware at or above IPL_CLOCK. I think that would be cleaner than doing another timer interrupt deferral thing. But, just to get the ball rolling, here a first attempt at the timer interrupt deferral thing for riscv64. The motivat

mips64: trigger deferred timer interrupt from splx(9)

2022-07-31 Thread Scott Cheloha
Hi, Apparently mips64, i.e. octeon and loongson, has the same problem as powerpc/macppc and powerpc64. The timer interrupt is normally only logically masked, not physically masked in the hardware, when we're running at or above IPL_CLOCK. If we arrive at cp0_int5() when the clock interrupt is lo

Re: [v5] amd64: simplify TSC sync testing

2022-07-31 Thread Dave Voutila
Scott Cheloha writes: > Hi, > > At the urging of sthen@ and dv@, here is v5. > > Two major changes from v4: > > - Add the function tc_reset_quality() to kern_tc.c and use it > to lower the quality of the TSC timecounter if we fail the > sync test. > > tc_reset_quality() will choose a new

Re: interface media without netlock

2022-07-31 Thread Claudio Jeker
On Sun, Jul 31, 2022 at 12:24:01PM +0100, Stuart Henderson wrote: > On 2022/07/28 13:30, Alexander Bluhm wrote: > > Problem is that smtpd(8) periodically checks media status. > > Really?! I bet it is the other simple protocol daemon, snmpd(8) -- :wq Claudio

Re: interface media without netlock

2022-07-31 Thread Stuart Henderson
On 2022/07/28 13:30, Alexander Bluhm wrote: > Problem is that smtpd(8) periodically checks media status. Really?!

Re: Consistency and cleanup in /share/misc/airport

2022-07-31 Thread Thomas Wager
On Sat, 2022-07-30 at 22:44 +0100, Stuart Henderson wrote: > Due to the rule for this file mentioned in the header, I think you'll > need to find a developer who has been to the added airports that have > replaced the metro areas, i.e. KCK MFW QDV QSF, either that or just > remove them. You are ri