5 ms·
One of the best benefits of Itanium are its security features: http://www.intel.com/content/dam/www/public/us/en/documents/white-papers/intel-itanium-secure-wh
by nickpsecurity 11y ago
One of the best benefits of Itanium are its security features:
http://www.intel.com/content/dam/www/public/us/en/documents/white-papers/intel-itanium-secure-white-paper.pdf http://www.intel.com/content/dam/www/public/us/en/documents/...
These are rarely discussed. However, Secure64's SourceT OS got plenty of mileage out of them. You might not be able to argue for Itanium on cost, performance, or ease of use. However, one could argue for it as a better start on secure OS's or appliances. Unlike academic prototypes, it's also in production with high speed and reliability. Let's also not forget you can do reverse stacks and other bug prevention tricks with less performance hit or clunkiness on a RISC architecture vs x86.
Personally, I'd just rather them have modernized the i960MX, minus other BiiN stuff:
https://en.wikipedia.org/wiki/BiiN https://en.wikipedia.org/wiki/BiiN
Targeting a robust, UNIX-compatible OS and C toolchain to it might have let it survive and get continually updated. Then, when HLL's got popular, we'd have a good hardware target for them that supported POLA inside applications. As usual, I'm speaking of great stuff in a past or never-happened tense. Least Itanium made it so far.
- wglb 11y agoHere is an interesting (not) security feature: https://news.ycombinator.com/item?id=9956044 https://news.ycombinator.com/item?id=9956044
- nickpsecurity 11y agoNot doing it fully during a procedure call is an optimization. I responded to the comment with links from 2002 and 2005 that showed this along with proper way to save everything to memory. Shouldn't have been a surprise to someone reading up on it.
- wglb 11y agoSo they used a securely designed component and got bit anyway.
- nickpsecurity 11y agoThat wasn't the security features. It was the features not designed for security and targeting an audience wanting performance enhancements. The kind of thing that often leads to unexpected problems. ;)
- kjs3 11y agoYeah...the i960mx was a missed opportunity. It was certainly oversold as "Intels RISC replacement for x86" (it was never going to be that in the real world), but it would have been interesting to see how far it would have gone if the decision hadn't been "we'll just neuter the little bastard and try and recoup some development dollars by using it as an embedded processor".
- nickpsecurity 11y ago""we'll just neuter the little bastard and try and recoup some development dollars by using it as an embedded processor"." Lmao well-put. Maybe if they saw it worded that way on the drawing board they might have seen the folly. I keep thinking of checking on the Alpha ISA licensing situation to get PALcode, etc back. Last I checked Intel and Samsung had control of licensing but it kinda disappeared. Might just stick with SPARC or RISC-V with modifications to use clever modifications from the past. Might even try to design a knock-off of i960's better features updates based on lessons learned over time.
- kjs3 11y agoI've been impressed with the RISC-V folks. Seem to have solid talent and realistic goals.
- nickpsecurity 11y agoDid you mean the main University group (s) that defined and implemented the ISA? If so, I agree they've done well. I especially loved that they open-sourced a 1+GHz 48nm core. Awesome stuff. I posted a link to Schneiers Squid thread today on a bunch of asynchronous chip work. One was a 180nm FPGA w/ several times Xilinx's performance and one a 40nm microcontroller. I imagine a combination of RISC-V with that async flow would produce one drool-worthy processor in price, performance, and NRE cost.
- thesz 11y agoCan you point out where the links are?