Register a SA Forums Account here!
JOINING THE SA FORUMS WILL REMOVE THIS BIG AD, THE ANNOYING UNDERLINED ADS, AND STUPID INTERSTITIAL ADS!!!

You can: log in, read the tech support FAQ, or request your lost password. This dumb message (and those ads) will appear on every screen until you register! Get rid of this crap by registering your own SA Forums Account and joining roughly 150,000 Goons, for the one-time price of $9.95! We charge money because it costs us money per month for bills, and since we don't believe in showing ads to our users, we try to make the money back through forum registrations.
 
  • Post
  • Reply
pseudorandom name
May 6, 2007

SYSV Fanfic posted:

Just want to add that this check is the default behavior. You can disable these checks x86_64, and AArch64 and and Linux (probably windows too) uses the highest bits to tag memory regions. The tag bits extend from left to right, when the architecture grows the canonical area, it grows from right to left. It's going to be awhile before there is a risk of them overlapping.

Where does Linux do this on AMD64?

Adbot
ADBOT LOVES YOU

pseudorandom name
May 6, 2007

that's what I thought

pseudorandom name
May 6, 2007

My favorite bit of VESA trivia is that OS/2 would run BIOS routines in VM86 mode and record their IO port accesses and then just replay them without bothering to execute the real-mode BIOS.

pseudorandom name
May 6, 2007

It wasn't that the instruction was too difficult to use, it was that if that byte sequence appeared anywhere in the program it was possible for the CPU to for-real corrupt memory by speculatively executing it.

  • 1
  • 2
  • 3
  • 4
  • 5
  • Post
  • Reply