On 11/13/19, grarpamp wrote:
> https://www.nytimes.com/2019/11/12/technology/intel-chip-fix.html
>
> Intel caught lying about it.
https://news.ycombinator.com/item?id=21535630
The Internet is also speculating that, given the top secret
"[ir]responsible disclosure" process, and the slowdowns
On Wed, Nov 13, 2019 at 06:20:49PM -0500, grarpamp wrote:
> On 11/13/19, Georgi Guninski wrote:
> >> Users flock to AMD.
> >
> > Is AMD really better?
> > I suspect it is the same garbage as Intel.
>
> AMD's price:performance is compelling right now,
> and enjoying underdog rising.
>
> It's
On Wed, Nov 13, 2019 at 12:10:10AM -0500, grarpamp wrote:
> https://www.phoronix.com/scan.php?page=article=intel-jcc-gaming=1
> https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files
>
> Users flock to AMD.
Is AMD really better?
I suspect it is the same garbage as Intel.
https://www.nytimes.com/2019/11/12/technology/intel-chip-fix.html
Intel caught lying about it.
Last May, when Intel released a patch for a group of security
vulnerabilities researchers had found in the company's computer
processors, Intel implied that all the problems were solved. But that
Bunch of other exploits rolled up...
Too bad users had to wait, for again the Nth time
in a couple years, for 'responsible disclosure'
over their top secret closed source hardware.
#OpenFabs , #OpenHW , #OpenAudit
https://xenbits.xen.org/xsa/advisory-305.html
https://www.phoronix.com/scan.php?page=article=intel-jcc-gaming=1
https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files
Intel is today making public the Jump Conditional Code (JCC) erratum.
This is a bug involving the CPU's Decoded ICache where on Skylake and
derived CPUs where
