A Hardware-Software Symbiosis 120
Roland Piquepaille writes "We all want smaller and faster computers. Of course, this increases the complexity of the work of computer designers. But now, computer scientists from the University of Virginia are coming with a radical new idea which may revolutionize computer design. They've developed Tortola, a virtual interface that enables hardware and software to communicate and to solve problems together. This approach can be applied to get a better performance from a specific system. It also can be used in the areas of security or power consumption. And it soon could be commercialized with the help of IBM and Intel."
Re:NoROLAND NOROLAND NOROLAND (Score:3, Insightful)
The stories he submits link directly to the article, it's only his submitter link that goes to his blog. I rarely, if ever, look at who submitted the article.
If he somehow profits from submitting articles I'm interested in reading, more power to him.
hmm (Score:1, Insightful)
"We could use the software to hide flaws in the hardware, which would allow designers to release products sooner because problems could be fixed later," translation -> Hardware companies can produce shit and if someone happens to notice a flaw we can create a patch instead of testing our products first. Will this not also open the hardware up to a virus?
Doesn't sound like such a good thing to me (Score:4, Insightful)
I can't wait to pay £400 for a Beta CPU and then get to endure 6 months of crashing until it gets patched.
BS again.... (Score:5, Insightful)
Using inferface layers to get more portable and easier to use interfaces is an old and well-established technique.
There people are looking for money, right? Why does
CCS (Score:5, Insightful)
If there wasn't a pic of a cute professor involved, would anyone care?
Hardware signalling and code re-ordering (Score:2, Insightful)
When the hardware detects a problem it signals the software. The software knows the location of the problematic code by checking a "last executed branch" register. A dynamic optimizer(software) then re-orders the code in that region and caches it to be used in future passes through that section.
The trick will be getting the dynamic optimizer light-weight enough that it doesn't induce performance hits in and of itself. Also, as an above poster noted, re-ordering code on the fly is fraught with peril. It seems this could have application in general purpose laptops, cellphones, and other non-safety critical gadgets. There should definitely be a bit in the machine control register to switch off the optimizer.