On Thu, Jul 27, 2023 at 10:45:50PM -0500, Scott Cheloha wrote:
> On Wed, Jul 26, 2023 at 11:16:19AM -0500, Scott Cheloha wrote:
> > This is the next patch in the clock interrupt reorganization series.
> >
> > Now that statclock() is cleaned up we can turn to hardclock().
> >
> > [...]
> >
> > Th
On Wed, Jul 26, 2023 at 11:16:19AM -0500, Scott Cheloha wrote:
> This is the next patch in the clock interrupt reorganization series.
>
> Now that statclock() is cleaned up we can turn to hardclock().
>
> [...]
>
> This patch moves the setitimer(2) code out of hardclock(). The big
> idea is ide
This is the next patch in the clock interrupt reorganization series.
Now that statclock() is cleaned up we can turn to hardclock().
The goal of the next four patches is to eliminate the need for the
hardclock on secondary CPUs. Secondary CPUs don't need a hardclock.
hardclock() is only used on s
