May be time for OpenBSD people ( if they have the resources ) to build a CPU from ground up with RISC-V?
Meltdown, aka “Dear Intel, you suck”
21–30 of 176 posts
Re: Meltdown, aka “Dear Intel, you suck”
#22May be time for OpenBSD people ( if they have the resources ) to build a CPU from ground up with RISC-V?
There are already CPUs available that aren't affected by these bugs. The problem is that most people want the fastest CPU for a given price -- and making a new, slow, expensive CPU isn't going to solve that problem.
Re: Meltdown, aka “Dear Intel, you suck”
#23Earlier quoted context omitted.
Just crowdsource a few billion $ for R&D and we are good to go.
The first and most important phases of hardware design are a lot like software development. If open source folks can write an OS without much funding, then they can design a CPU.
Re: Meltdown, aka “Dear Intel, you suck”
#24Re: Meltdown, aka “Dear Intel, you suck”
#25Is there not some sort of OS embargo consortium that could be created to resolve this?
The problem with embargoes is that they tend to run so long that users are put at risk unnecessarily. Most of the reasons for extending embargoes way beyond the time needed to prepare and test patches are just bullshit. For example, from the conversation on the KRACK embargo: >Q. What is the rationale on extending the embargo so long? To give vendors a chance to patch? It seems like once people in the know know about…
Re: Meltdown, aka “Dear Intel, you suck”
#26Earlier quoted context omitted.
There are already CPUs available that aren't affected by these bugs. The problem is that most people want the fastest CPU for a given price -- and making a new, slow, expensive CPU isn't going to solve that problem.
Which widely available and affordable CPUs aren't affected by Spectre?
Re: Meltdown, aka “Dear Intel, you suck”
#27Earlier quoted context omitted.
The first and most important phases of hardware design are a lot like software development. If open source folks can write an OS without much funding, then they can design a CPU.
Arguably , the most important phase of hardware design is actual production of said design.
Re: Meltdown, aka “Dear Intel, you suck”
#28Earlier quoted context omitted.
Everyone is affected by Spectre, but my understanding is that Meltdown is a particularly powerful "version" of Spectre that only affects Intel CPUs ?
My ELI5 attempt: There are 3 vulnerabilities. Meltdown is 1 of the 3. Meltdown is pretty much Intel only. Some ARM SoCs are also affected, but these are relatively rare. AMD64 is unaffected by Meltdown. Spectre are the other 2 vulnerabilities. Spectre affects pretty much everyone. Meltdown is more severe, and more of a blunder. For a technical explanation, see [1]. Was recently referred to at HN as well. [1] https://…
Re: Meltdown, aka “Dear Intel, you suck”
#29Meanwhile I have seen nothing from QNX or Integrity...
Re: Meltdown, aka “Dear Intel, you suck”
#30May be time for OpenBSD people ( if they have the resources ) to build a CPU from ground up with RISC-V?
OpenBSD has struggled at times to pay their power bills. They don't have the resources to branch off into building new hardware from first principles.