| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Seems to fix the clang crashes I was seeing.
|
|
|
|
|
|
| |
pixman in xenocara build and hopefully helps with ports as well.
suggested by matthieu@
|
|
|
|
|
|
| |
from IPL_TTY to IPL_NONE.
From Benjamin Baier
|
|
|
|
| |
ok kettenis@
|
|
|
|
|
|
|
|
| |
it just means we won't know what to show in ifconfig media output,
but that's not a huge deal. there's still some more issues around
api versions and driver support that we're working on though.
ok sthen@ jmatthew@
|
|
|
|
|
|
|
|
|
| |
Get the list of Pstates from OPAL, and use special registers to
request a Pstate or check the current Pstate. The turbo Pstates are
higher than the cpu's nominal speed, but the OCC's firmware should
throttle down the cpu if it would overheat.
ok kettenis@
|
|
|
|
|
|
|
| |
openings outside of the one used at config_found() time. Adapters
should take care of their own data.
ok dlg@ for a sligthly different vioblk.c version.
|
| |
|
| |
|
|
|
|
|
|
|
| |
bootduid variable in the kernel. This makes it possible to specify the
boot disk in pettitboot menu entry (e.g. grub.cfg).
ok deraadt@
|
|
|
|
| |
the FPU yet.
|
| |
|
|
|
|
|
| |
set the MMU to hash mode such that the full TLB is available on POWER9
CPUs.
|
|
|
|
| |
ok dlg@ tobhe@
|
|
|
|
| |
ok dlg@ tobhe@
|
|
|
|
|
|
| |
"new" API.
ok dlg@ tobhe@
|
| |
|
|
|
|
|
|
|
|
| |
and change bits in the page table entries that doesn't seem to happen
reliably on the POWER9 CPU I'm looking at. So make our pmap not depend
on this and emulate these bits instead.
As far as I can determine Linux doesn't rely on the hardware bits either.
|
|
|
|
|
|
|
| |
malloc(9) in pppxopen(). We can avoid these races without rwlock. Also
we move malloc(9) out of rwlock.
ok mpi@
|
|
|
|
|
|
| |
prevent collecting entropy from pppx(4).
ok mpi@
|
|
|
|
| |
local change lost in 5.7 drm update
|
|
|
|
|
|
|
|
|
| |
Similar to "Spleen 5x8" it only contains the printable ASCII
characters (96 glyphes).
The font is 2-Clause BSD licensed and is my original creation.
OK patrick@
|
|
|
|
| |
like all the cool drivers do.
|
|
|
|
| |
like all the cool drivers do.
|
|
|
|
|
|
|
|
|
|
|
| |
also a trackstick or separate physical buttons, imt was claiming all
report ids of the ihidev device preventing the trackstick/buttons
from attaching as a separate ims device on other report ids.
Just claim the report ids that imt needs and let ims attach to
others it may find.
Fixes two Dell Latitude laptops and tested in snaps for a bit.
|
|
|
|
|
|
|
| |
"button type" usages, so assume some reasonable defaults rather than
failing to attach.
Fixes two Dell Latitude laptops and tested in snaps for a bit.
|
|
|
|
|
|
|
| |
blf_enc() takes a number of 64-bit blocks to encrypt, but using
sizeof(uint64_t) in the calculation triggers a warning from clang
10 because the actual data type is uint32_t. Pass BCRYPT_WORDS / 2
for the number of blocks like libc bcrypt(3) does. OK kettenis@
|
| |
|
|
|
|
|
|
| |
From Alex Deucher
fceff9423f428a62a20bb8fb8f66e6a9f906f12c in linux 5.7.y/5.7.8
d7a6634a4cfba073ff6a526cb4265d6e58ece234 in mainline linux
|
|
|
|
|
|
| |
From Alex Deucher
c337fc540bb99e476e33153a9196eba4749a707a in linux 5.7.y/5.7.8
beaf10efca64ac824240838ab1f054dfbefab5e6 in mainline linux
|
|
|
|
|
|
| |
From Nicholas Kazlauskas
fcb408a7282302bd8b8afc6ef8db42b4eece23ee in linux 5.7.y/5.7.8
6eb3cf2e06d22b2b08e6b0ab48cb9c05a8e1a107 in mainline linux
|
|
|
|
|
|
| |
From Ivan Mironov
13b2fe391cac70c7746e2cb68e73d99002f1cd00 in linux 5.7.y/5.7.8
7e89e4aaa9ae83107d059c186955484b3aa6eb23 in mainline linux
|
|
|
|
|
|
| |
From Rodrigo Vivi
95e961c6c23c35bb9f190f8d6bd13f1606de5a48 in linux 5.7.y/5.7.8
55fd7e0222ea01246ef3e6aae28b5721fdfb790f in mainline linux
|
|
|
|
|
|
| |
From Guchun Chen
18b1cf2968e1baa883dbdf6adef6213626beaa0f in linux 5.7.y/5.7.8
12c17b9d62663c14a5343d6742682b3e67280754 in mainline linux
|
|
|
|
|
|
| |
From Evan Quan
9c33bf981fab14ffbde2635d6e3d7d0818bac5a8 in linux 5.7.y/5.7.8
a9d82d2f91297679cfafd7e61c4bccdca6cd550d in mainline linux
|
|
|
|
|
|
| |
From John Clements
50a8cfb0e71644f2882dbfaf93150184094245bd in linux 5.7.y/5.7.8
61380faa4b4cc577df8a7ff5db5859bac6b351f7 in mainline linux
|
|
|
|
|
|
| |
From Chris Wilson
18ad3ad0b9b35370182ae4a7dbd89a77168df19e in linux 5.7.y/5.7.8
8e87e0139aff59c5961347ab1ef06814f092c439 in mainline linux
|
|
|
|
|
|
| |
From Stylon Wang
b903524c8a60a3e9d5eede7fc87f1012332b929f in linux 5.7.y/5.7.8
fa7041d9d2fc7401cece43f305eb5b87b7017fc4 in mainline linux
|
|
|
|
|
|
| |
From Stylon Wang
60c60af1adffdc4a34f4b13acc44a02ec33169b1 in linux 5.7.y/5.7.8
cbd14ae7ea934fd9d9f95103a0601a7fea243573 in mainline linux
|
|
|
|
| |
OK kettenis@, deraadt@, patrick@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When we recompute the scaling factor during tc_windup() there is an
opportunity for arithmetic overflow if the active timecounter's
adjfreq(2) adjustment is too large. If we limit the adjustment to
[-500000, +500000] ppm the statement in question cannot overflow.
In particular, we are concerned with the following bit of code:
scale = (u_int64_t)1 << 63;
scale += \
((th->th_adjustment + th->th_counter->tc_freq_adj) / 1024) * 2199;
scale /= th->th_counter->tc_frequency;
th->th_scale = scale * 2;
where scale is an int64_t. Overflow when we do:
scale += (...) / 1024 * 2199;
as th->th_counter->tc_freq_adj is currently unbounded.
th->th_adjustment is limited to [-5000ppm, 5000ppm].
To see that overflow is prevented with the new bounds, consider the
new edge case where th->th_counter->tc_freq_adj is 500000ppm and
th->th_adjustment is 5000ppm. Both are of type int64_t. We have:
int64_t th_adjustment = (5000 * 1000) << 32; /* 21474836480000000 */
int64_t tc_freq_adj = 500000000LL << 32; /* 2147483648000000000 */
scale = (u_int64_t)1 << 63; /* 9223372036854775808 */
scale += (th_adjustment + tc_freq_adj) / 1024 * 2199;
/* scale += 2168958484480000000 / 1024 * 2199; */
/* scale += 4657753620480000000; */
9223372036854775808 + 4657753620480000000 = 13881125657334775808,
which less than 18446744073709551616, so we don't have overflow.
On the opposite end, if th->th_counter->tc_freq_adj is -500000ppm and
th->th_adjustment is -5000ppm we would have -4657753620480000000.
9223372036854775808 - 4657753620480000000 = 4565618416374775808.
Again, no overflow.
500000ppm and -500000ppm are extreme adjustments. otto@ says ntpd(8)
would never arrive at them naturally, so we are not at risk of breaking
a working setup by imposing these restrictions.
Documentation input from kettenis@.
No complaints from otto@.
|
| |
|
|
|
|
| |
saves a few hundred bytes on both amd64 and sparc64
|
|
|
|
|
| |
RW page within allocateable space) were leaked. report from adam@grimm-co
ok millert
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The processor does not perform speculative reads and only one of its
execution pipes should issue memory accesses. As a result, loads should
happen in the correct order without barrier instructions.
Tested on CN5020, CN6120, CN7130 and CN7360.
This diff has been in use on the octeon-based mips64 bulk build cluster
for several months. Also tested in snaps for a while.
|
| |
|
|
|
|
| |
OK deraadt@
|
|
|
|
| |
ok deraadt@, pirofti@
|
|
|
|
|
|
|
|
|
| |
* We don't need TC_LAST
* Make internal functions static to avoid namespace pollution in libc.a
* Use a switch statement to harmonize with architectures providing
multiple timecounters
ok deraadt@, pirofti@
|