Re:Why Raspberry Pi Isn't Vulnerable to Spectre or Meltdown
by astrange on Saturday January 06, 2018 @12:05AM
(#16083950)
Intel CPUs do already have PCID (PID-tagged page table cache) to make switching processes cheaper.
Re:Why Raspberry Pi Isn't Vulnerable to Spectre or Meltdown
by rbanffy on Saturday January 06, 2018 @04:44AM
(#16084584)
Shouldn't that protect against Spectre?
Re:Why Raspberry Pi Isn't Vulnerable to Spectre or Meltdown
by krylon on Saturday January 06, 2018 @04:29PM
(#16087563)
If I understand it correctly, Spectre only works within a single address space.
Re:Why Raspberry Pi Isn't Vulnerable to Spectre or Meltdown
by rbanffy on Saturday January 06, 2018 @05:41PM
(#16087890)
Well... I never expected one part of my process not to be able to peek into what the others are doing.
Re:Why Raspberry Pi Isn't Vulnerable to Spectre or Meltdown
by krylon on Saturday January 06, 2018 @05:53PM
(#16087942)
One example would be malicious Javascript - or WebAssembly - strolling through your browser's memory looking for passwords to send home to the mothership. Or other sensitive information, like credit card numbers and so forth.
> Compilers will get called upon to do more safe speculation
Compilers can also emit code that minimizes those situations. Also, extending the ISA with an instruction modifier that signals that otherwise innocent instruction has indeed observable side effects (ideally the processor should know that, but, if the compiler already knows it, a runtime check can be skipped.
> Processors will have to grow the logic to determine when speculation is safe
In many cases, this would be as simple as flagging the micro-op as unsafe and pause the speculation at that point.
For Meltdown, the just-add-silicon approach could be to never share cache between privileged and unprivileged code. To extend that to Spectre, never share cache across different PIDs (but, then, the ISA will have to know what a PID is). Since that would reduce the effective cache effectiveness, caches will have to grow.
Fun times ahead.