Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 3 Jan 2018 22:37:21 +0100
From:      Ed Schouten <ed@nuxi.nl>
To:        Konstantin Belousov <kostikbel@gmail.com>
Cc:        David Chisnall <theraven@freebsd.org>, Adrian Chadd <adrian.chadd@gmail.com>,  blubee blubeeme <gurenchan@gmail.com>, FreeBSD current <freebsd-current@freebsd.org>
Subject:   Re: Programmatically cache line
Message-ID:  <CABh_MK=2uvPoNCg7qL14yVuxo_%2BHVSvccLTBAnRAHNzqor--0g@mail.gmail.com>
In-Reply-To: <20180101103655.GF1684@kib.kiev.ua>
References:  <CALM2mEmWYz5nyqvxMJwMWoFOXnDTvWFrEug7UUha6xe7Um6ODw@mail.gmail.com> <20171230082812.GL1684@kib.kiev.ua> <CAJ-VmomxGJsn8eOtWoqevdW-spUPgcSGKEc7eR4xuXLP-E1XRA@mail.gmail.com> <08038E36-9679-4286-9083-FCEDD637ADCC@FreeBSD.org> <20180101103655.GF1684@kib.kiev.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
2018-01-01 11:36 GMT+01:00 Konstantin Belousov <kostikbel@gmail.com>:
>> >> On x86, the CPUID instruction leaf 0x1 returns the information in
>> >> %ebx register.
>> >
>> > Hm, weird. Why don't we extend sysctl to include this info?
>
> For the same reason we do not provide a sysctl to add two integers.

I strongly agree with Kostik on this one. Why add stuff to the kernel,
if userspace is already capable of extracting this? Adding that stuff
to sysctl has the downside that it will effectively introduce yet
another FreeBSDism, whereas something generic already exists.

-- 
Ed Schouten <ed@nuxi.nl>
Nuxi, 's-Hertogenbosch, the Netherlands



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CABh_MK=2uvPoNCg7qL14yVuxo_%2BHVSvccLTBAnRAHNzqor--0g>