Date: Tue, 19 Sep 2023 15:41:33 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Sebastian Huber <sebastian.huber@embedded-brains.de> Cc: hackers@freebsd.org Subject: Re: Remove timecounter tc_counter_mask member? Message-ID: <202309191541.38JFfXnb073412@critter.freebsd.dk> In-Reply-To: <d3e9e071-f4f9-40a9-b656-92a8853ddb08@embedded-brains.de> References: <bc1a7b28-5e7b-4ee6-aae8-f95adc65fc76@embedded-brains.de> <202309162044.38GKi7RZ022115@critter.freebsd.dk> <d3e9e071-f4f9-40a9-b656-92a8853ddb08@embedded-brains.de>
next in thread | previous in thread | raw e-mail | index | archive | help
-------- Sebastian Huber writes: > On 16.09.23 22:44, Poul-Henning Kamp wrote: > > Sebastian Huber writes: > > > >> the timecounter structure contains a tc_counter_mask which enables > >> support for time counters implementing less than 32-bits: > >> Is the sys/x86/isa/clock.c still used? Are there chips on the market > >> with 24-bit ACPI timers? > > ... and are there any FreeBSD platforms using narrow timecounters > > outside the src-tree ? > > > > My personal gut feeling, is that we can get away with it, once i386 > > is out of the picture. > > If it is in principle acceptable to remove the tc_counter_mask at some > point in time, would it make sense to issue a warning if a timecounter > is installed with a mask not equal to 0xffffffff? It would be a good a way to warn people... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202309191541.38JFfXnb073412>