Remix.run Logo
▲ cjbprime 4 hours ago

Wouldn't it be prudent for someone to patch even if they aren't running their code on an AVX512 system right this moment? They could be running on one.. next moment.

▲Banditoz 4 hours ago | parent [-]

Sure, but I think it brings it down from "patch immediately" severity, to just "bump the JDK with next service deploy" severity.

Or, do running machines often have their CPU changed from under them without much notice?

▲stackskipton 4 hours ago | parent | next [-]

Depends on the company and deployment method. As Ops person, I generally don't think much about rolling out different Kubernetes Nodes and what SKU I select. So yes, you could be running on one node type today and tomorrow I upgrade the nodes under you.

▲xmodem 3 hours ago | parent [-]

We’re using a second-tier cloud provider’s managed Kubernetes offering, and in investigating our level of exposure to this, I just learned that there is variance within a node pool on whether AVX-512 is available.

▲Sohcahtoa82 3 hours ago | parent | prev [-]

> Or, do running machines often have their CPU changed from under them without much notice?

I dunno about other cloud providers, but I know AWS can move your EC2 VM from one system to another transparently. There is a server ID you can get from the metadata, but unless you're checking it frequently, you can be moved without ever being aware.

▲PhilipRoman 3 hours ago | parent | next [-]

Question is if they expose it to the guest. Many (most?) cloud platforms will make the guest see the lowest common denominator, specifically to avoid angry customers when their working setup suddenly breaks.

In the case of transparent migration, I think it's basically a must. No JIT (or even libc probably) is going to support CPU features changing at runtime.

▲johnbellone 2 hours ago | parent | prev [-]

You’ll need to restart the guest.