I’ll post some links, but it’s a pretty busy week for me already, so give me some time.

An interrupt is an input that can be triggered to interrupt normal execution. It is used for e. g. hardware devices to signal the processor something has happened that requires timely processing, so that real-time behavior can be achieved (for variable definitions of real-time). Interrupts can also be triggered by software, and this explanation is a gross oversimplification, but that information is what is most likely relevant and interesting for your case at this point.

The commands you posted will sort the interrupts and output the one with the highest count (via head -1), thereby determining the interrupt that gets triggered the most. It will then disable that interrupt via the user-space interface to the ACPI interrupts.

One of the goals of ACPI is to provide a kind of general hardware abstraction without knowing the particular details about each and every hardware device. This is facilitated by offering (among other things), general purpose events - GPEs. One of these GPEs is being triggered a lot, and the processing of that interrupt is what causes your CPU spikes.

The changes you made will not persist after a reboot.

Since this is handled by kworker, you could try and investigate further via the workqueue tools: https://github.com/torvalds/linux/tree/master/tools/workqueue

In general, Linux will detect if excessive GPEs are generated (look for the term “GPE storm” in your kernel log) and stop handling the interrupts by switching to polling. If that happens, or if the interrupts are manually disabled, the system might not react to certain events in a timely manner. What that means for each particular case depends on what the interrupts are being responsible for - hard to tell without additional details.

I shudder to think OP’s post was written by an actual person…

This, however, is about diagnostics, i. e. annotating delete with a reason (message) to express developer intent when deleting a function, not about memory management.

Yeah, that’s the implication. Unfortunately, that is also misleading people into believing they might get a well-tested, nearly bug free game.

At 7h / day of just testing, 200k hours amount to approximately 110 years, given 260 working days per year.

Veilguard has been in development for around 9 years, so thats about 12 “years of testing per year”, so pretty much at least 12 people doing nothing else but testing (this assumes sane working conditions - hi EA!)

Given how long the game has been in development, what does that number even mean? How much of the stuff they wrote 9 years ago is still in place, given that players would expect the technological advancements available since 2015.

Also, it’s supposed to be released end of October, I believe? Or has it been postponed even further (again)? Anyway, why would they claim something like that before release? That will probably backfire.

Based on this comment*, I’ll migrate a large project to bazel now. I’ll report how it goes.

• disclaimer: the comment just pushed me over the edge

Same, but you were talking about NewPipe. I assume you use that on your phone.

And while you can disable the search history there, too, it often is convenient not to have to type the name of that thing you want to listen to while you’re driving, so many people leave it enabled.

They ask for your search history then

For years, Intel’s compiler, math library MKL and their profiler, VTune, really only worked well with their own CPUs. There was in fact code that decreased performance if it detected a non-Intel CPU in place:

https://www.agner.org/optimize/blog/read.php?i=49&v=f

That later became part of a larger lawsuit, but since Intel is not discriminating against AMD directly, but rather against all other non-Intel CPUs, the result of the lawsuit was underwhelming. In fact, it’s still a problem today:

https://www.extremetech.com/computing/302650-how-to-bypass-matlab-cripple-amd-ryzen-threadripper-cpus

https://medium.com/codex/fixing-intel-compilers-unfair-cpu-dispatcher-part-1-2-4a4a367c8919

Given that the MKL is a widely used library, people also indirectly suffer from this if they buy an AMD CPU and utilize software that links against that library.

As someone working in low-level optimization, that was/is a shitty situation. I still bought an AMD CPU after the latest fiasco a couple of weeks ago.

Crocodiles are reptiles, right?

They actually joke about it in the show, screaming “Aah, a crocodile”, and it’s just some woman working there. Same with the director being a lion, I believe.

The exhibit has turtles and penguins.

I’d also assume they just flew the thing near the hovering helicopter and triggered it remotely, that would do the trick.

Not really. A solid set for security Torx is available for like $20 from reputable brands. Naturally, you can get higher quality sets and sets that add other security bits, but you still won’t land in an unacceptable price range even for private use, let alone a pro shop.

https://streamable.com/emqc0v

I watched a few videos before I realized Bobby Fingers is Mr. Chrome, and it made me unreasonably happy.

I am on my 4th personal TUXEDO laptop, never had any issues. I actually started giving them to the devs at my company, no complaints so far.

They don’t offer my choice of OS, and I wouldn’t use a preinstalled OS anyway, so I can’t comment on that.

Oh look, its Fabio.

Given how political punk was right from the start, I wouldn’t call it “just a music movement”.

Generally all correct, here is a resource with a lot of in-depth information and additional links:

https://batteryuniversity.com/article/bu-808-how-to-prolong-lithium-based-batteries