On Sat, Dec 10, 2022 at 10:24:52AM -0700, Theo de Raadt wrote:
> Scott Cheloha wrote:
>
> > On Sat, Dec 10, 2022 at 09:33:55AM -0700, Theo de Raadt wrote:
> > > Mark Kettenis wrote:
> > >
> > > > So really the question is whether we should register the "tick"
> > > > timecounter if we also
Scott Cheloha wrote:
> On Sat, Dec 10, 2022 at 09:33:55AM -0700, Theo de Raadt wrote:
> > Mark Kettenis wrote:
> >
> > > So really the question is whether we should register the "tick"
> > > timecounter if we also provide the "stick" or "sys_tick" timecounter.
> > >
> > > Personaly I think
On Sat, Dec 10, 2022 at 09:33:55AM -0700, Theo de Raadt wrote:
> Mark Kettenis wrote:
>
> > So really the question is whether we should register the "tick"
> > timecounter if we also provide the "stick" or "sys_tick" timecounter.
> >
> > Personaly I think the code we currently have is fine. If
Mark Kettenis wrote:
> So really the question is whether we should register the "tick"
> timecounter if we also provide the "stick" or "sys_tick" timecounter.
>
> Personaly I think the code we currently have is fine. If you make the
> sconscious decision to use "tick" on a system that provides
> Date: Sat, 10 Dec 2022 09:43:32 -0600
> From: Scott Cheloha
>
> On Sat, Dec 10, 2022 at 03:14:37PM +0100, Mark Kettenis wrote:
> > > Date: Fri, 9 Dec 2022 16:27:59 -0600
> > > From: Scott Cheloha
> > >
> > > The UltraSPARC IIe's %TICK register has a variable frequency. See
> > > section 2.3
On Sat, Dec 10, 2022 at 02:43:50PM +0100, Christian Weisgerber wrote:
> Scott Cheloha:
>
> > The UltraSPARC IIe's %TICK register has a variable frequency.
> > miod@ confirmed that the problem is real.
>
> Indeed, I remember clocking down the Blade 100 with apm(8).
>
> Somebody with access to
On Sat, Dec 10, 2022 at 03:14:37PM +0100, Mark Kettenis wrote:
> > Date: Fri, 9 Dec 2022 16:27:59 -0600
> > From: Scott Cheloha
> >
> > The UltraSPARC IIe's %TICK register has a variable frequency. See
> > section 2.3 in this document here:
> >
> >
> Date: Fri, 9 Dec 2022 16:27:59 -0600
> From: Scott Cheloha
>
> The UltraSPARC IIe's %TICK register has a variable frequency. See
> section 2.3 in this document here:
>
>
Scott Cheloha:
> The UltraSPARC IIe's %TICK register has a variable frequency.
> miod@ confirmed that the problem is real.
Indeed, I remember clocking down the Blade 100 with apm(8).
Somebody with access to the hardware might want to adapt the NetBSD
code that adds timecounter support for the