8 ms·
India's first RISC-V based Chip is Here: Linux boots on Shakti processor
- rwmj 8y agoAnnoyingly this chip lacks the Compressed (RVC) extension, making it incompatible with all existing Linux distros. These will either have to be recompiled without any Compressed instructions (which increases I-cache pressure on other CPUs that do support it), or we'll need to ship two versions of everything. From discussions I believe they've been recompiling Fedora & Debian from sources without RVC.
- oklababa 8y agowhat are you talking bro? it's already running on ubuntu
- rwmj 8y agoWhat does that have to do with anything? AIUI they have compiled their own distro (which is not Ubuntu). It leaves the rest of us with the problem of how (or even if) we support this chip. Do we offer two versions of Fedora, with twice the storage, twice the build time, and toolchain changes to support these two architectures? Or do we compile Fedora without RVC, impacting performance on chips which do support RVC? This is an unfortunate (but long-predicted) side-effect of not making RVC mandatory for Unix-like RISC-V systems.
- 1023bytes 8y agoIf you are referring to that screenshot in the article, that is just the PC it's connected to. If you look closer at the terminal you can see it's running Buildroot.
- mmrezaie 8y agoWhy did they choose to not have RVC? Also, what happens if one of these groups working on RISC-V decides they need to add a couple of more instructions in there? Is there a group that you can send your patches for the review like Linux kernel? I do not understand the compatibility of the risc-v cpus!
- rwmj 8y agoI was discussing this with someone involved with the project and it comes down to wanting to handle only 32 bit instructions (RVC instructions are 16 bit; other RISC-V extensions can have > 32 bit instructions, although of course if you don't support any of those extensions then you don't have to deal with it). This is a simplifying assumption in the decoder element in their pipeline. RISC-V does allow you to define other extensions in a methodical and detectable way, and we intend to detect those at runtime (as you would, for example, with something like AES-NI or AVX on Intel). However RVC impacts every bit of compiled code so there's no way to deal with it at runtime (something like that would make all binaries much bigger and would greatly complicate the toolchain).
- vectorEQ 8y agoi like it how they just want to process 1 length instructions (32bit). that's so much easier to build for debuggers/assemblers etc. i think it's a good move to allow for people to write custom OS onto it. As the more complicated aspects of generating machine code have gone, it's easier to write targeted compilers, assemblers and debuggers etc. i find this very interesting choice!
- monocasa 8y agoIt's probably more about the hardware's instruction decoder. The RVC code has unaligned 32-bit instructions, and that greatly increases the complexity at instruction decode time. Now you have to worry about crazy stuff like an instruction that straddles two different pages.
- deleted 8y ago[deleted]
- ailideex 8y agoIs this really such a big issue? Currently there are already multiple arm builds from some distros to deal with similar problems: https://archlinuxarm.org/about/downloads https://archlinuxarm.org/about/downloads
- rwmj 8y agoIt's exactly the fragmentation of ARM that I'd like to avoid. Same story goes for bootloaders, kernels, out-of-tree drivers etc. You might find my 15 minute talk at the RISC-V workshop interesting on this subject: https://rwmj.wordpress.com/2018/05/21/my-talk-from-the-risc-v-workshop-in-barcelona/ https://rwmj.wordpress.com/2018/05/21/my-talk-from-the-risc-... The bit about RISC-V on servers starts around 5 mins in.
- ailideex 8y agoIf the only issue is the kernel (which I don't know it is) ... I'm not that sure there is such a big problem. If it is essentially different architectures which requires all binaries to be compiled differently then the problem is much more dire. I think your points in the video is important - or rather, should be important - but from the fragmentation of ARM it seems they are not as important to chip makers as they should be. However ARM's fragmentation seems to have not been a serious impediment to it's adoption. I think though going forward the solution may be to target higher level machines (i.e. JVM). This obviously is not realistic for the kernel - but for software that most people want to run on RHEL it would most likely be fine.
- rwmj 8y agoFor RVC the problem is everywhere. However I argue in the video that even just different kernels, bootloaders or out-of-tree drivers are a real problem when you're deploying servers at scale. ARM has distinctly not been popular in the data center (despite years of work). That's for many reasons but one is surely the fragmentation of the platform.
- 8y ago
- neuron_clash 8y agoThe shakti effort was started in 2014. As a member of the group I can say that, then RVC was only seen at as optional extension. We got the tapeout opportunity an year ago. Later the riscv community has taken the decision to make RVC extension mandatory for distros without involving most of its committee members. Had we been told earlier would have given the support.
- rwmj 8y agoThis is true and very unfortunate how it was handled. However I do think the decision to standardize on RVC for Unix-like systems / servers was the right one, no matter how it was arrived at.
- mwcampbell 8y agoI think the politics of how the decision was made are more important than the technical merits of the decision. Given that, apparently, some community members decided to make RVC mandatory without telling the rest of the committee, I think the only right thing to do is to recompile distros without RVC and live with it. Then, the large binaries and icache pressure will stand as a permanent reminder of how not to make a decision. Also, is it possible to use only a handful of RVC-enabled binaries on a system that otherwise doesn't use RVC? If so, it might not be so bad.
- brucehoult 8y agoThis seems not correct to me. No one has made RVC "mandatory". For a start no one had any authority to do any such thing! Some people building Linux-capable processors decided to include RVC. Some people with Linux distributions (Fedora, Debian), seeing that all known current efforts to build linux capable processors were supporting RVC, and seeing the large benefits it provides, decided to build their distros using RVC. If someone wants a Linux distro that doesn't use RVC .. it's not a problem. The instructions supported are exactly the same. There are no portability problems. If a package will build successfully with RVC then it will compile without it, no problem, with no additional human work. Just change one configure flag when you build the compiler (to default to rv64g instead of rv64gc). The only difference is the binaries will all be 30% to 50% bigger. Some more build machines will be required, and a few GB of disk space. Theses are trivial things. It's absolutely nothing like the difference between, say, armeabi and armhf or the differences between armv4, armv4t, armv5, armv6, armv7.
- wolfgke 8y ago> Annoyingly this chip lacks the Compressed (RVC) extension, making it incompatible with all existing Linux distros. These will either have to be recompiled without any Compressed instructions (which increases I-cache pressure on other CPUs that do support it), or we'll need to ship two versions of everything. Perhaps ARM actually did have a point with their "FUD" campaign against RISC-V: > https://archive.is/SkiH0 https://archive.is/SkiH0 (EDIT: in particular, consider point 3).
- ajross 8y agoAnd how many mutually incompatible instruction sets have been shipped under the ARM branding? I mean, glass houses and all.
- masklinn 8y agoOTOH Arch provides 29 different ARM packages…
- nickik 8y agoNot really, this is simply a case where the Shakti people were so early that the standard simply wasted defined yet, it was not even clear when how things would be standardized.
- swatkat 8y agoProject page: http://rise.cse.iitm.ac.in/shakti.html http://rise.cse.iitm.ac.in/shakti.html
- iamshs 8y agoAnother ppt from team. https://content.riscv.org/wp-content/uploads/2018/07/1100-19.07.18-Vinod-Ganesan-Gopinathan-Muthuswamy-IIT-Madras.pdf https://content.riscv.org/wp-content/uploads/2018/07/1100-19... Project lead looks to be running a semiconductor company, and they say they have NDA with the fab company.
- ktm5j 8y agoThanks, this article was pretty lackluster to be honest..
- nickik 8y agoPeople should really look at the Shakti program. It is really quite cool and because it releases everything in open-source we have a real shot at getting all kinds advanced processors and other free IPs. There was a workshop at Chennai: https://riscv.org/2018/07/risc-v-workshop-in-chennai-proceedings/ https://riscv.org/2018/07/risc-v-workshop-in-chennai-proceed... Also, this is an old video but gives the basic information for the project: https://www.youtube.com/watch?v=OoxOzvf78uQ https://www.youtube.com/watch?v=OoxOzvf78uQ This is one of the leads: https://news.ycombinator.com/user?id=gsmadhusudan https://news.ycombinator.com/user?id=gsmadhusudan I think I will repost his comment on Shakti, more people should see it, it was an answer in a thread about Shakti being an 'ARM killer': ------------------------------------------------------------------------------------ As the lead architect of Shakti and the guy who helped kick-start the project, I figure I am owed my 2 cents ! 1. We never positioned it as an ARM killer ! That was the imagination of the reporter who wrote the article. 2. Shakti is not a state only project. Parts of Shakti are funded by the govt, these relate to cores and SoCs needed by the Govt. The defense and strategic sector procurement is huge, runs in the 10s of billions of USD.There is significant funding in terms of manpower, tools and free foundry shuttles provided by the private sector. In fact Shakti has more traction with the private sector than the govt sector in terms of immediate deployments. 3. The CPU eco-system including ARM's is a bit sclerotic. It is not the lic cost that is the problem, it is the inherent lack of flexibility in the model. 4. Shakti is not only a CPU. Other components include a new interconnect based on SRIO, GenZ with our extensions accompanied by open source silicon, a new NVMe+ based storage standard again based on open source SSD controller silicon (using Shakti cores of course), open source Rust based MK OS for supporting tagged ISAs for secure Shakti variants, fault tolerant variants for aerospace and ADAS applications, ML/AI accelerators based on our AI research (we are one of the top RL ML labs around). 4. the Shakti program will also deliver a whole host of IPs including the smaller trivial ones and also as needed bigger blocks like SRIO, PCIe and DDR4. All open source of course. 5. We are also doing our own 10G and 25G PHYs 6. A few startups will come out of this but that can wait till we have a good open source base. 7. The standard cores coming out of IIT will be production grade and not research chips. And building a processor is still tough these days. Try building a 16 core, quad wide server monster with 4 DDR4 channels, 4x25G I/O ports, 2 ports for multi-socket support. All connected via a power optimized mesh fabric. Of course you have to develop the on-chip and off-chip cache coherency stuff too ! 8. And yes we are in talks with AMD for using the EPYC socket. But don't think they will bite. Just ignore the India bit and look at what Shakti aims to achieve, then you will get a better picture. I have no idea how successful we will be and I frankly do not care. What we will achieve (and have to some extent already) is - create a critical mass of CPU architects in India - create a concept to fab eco-system ind India for designing any class of CPUs - add a good dose of practical CPU design knowhow into the engineering curriculum - become one of the top 5 CPU arch labs around Shakti is already going into production. The first design is actually in the control system of an experimental civilian nuclear reactor. IIT is within the fallout zone so you can be sure we will get the design right. If you want any further info, mail me. My email is on the Shakti site. G S Madhusudan
- jstanley 8y agoThis is excellent news. I wonder how long it will be until we can buy a full raspi-like platform that has no proprietary chips or firmware.
- turblety 8y agoWhat do you think of the HiFive Unleashed [1]. I don't have one but they have claimed [2] the entire boot process is free and open source? 1. https://www.sifive.com/products/hifive-unleashed/ https://www.sifive.com/products/hifive-unleashed/ 2. https://forums.sifive.com/t/who-should-buy-the-hifive-unleashed/1072/5 https://forums.sifive.com/t/who-should-buy-the-hifive-unleas...
- jstanley 8y agoLooks very cool, I'd not heard of this before! I can't see where you can actually buy one, or how much it costs, but looks like a project to keep an eye on.
- RossBencina 8y agoWeird, there's something up with their Crowd Supply page. I saw the price there the other day (in the right hand panel that is currently empty): https://www.crowdsupply.com/sifive/hifive-unleashed https://www.crowdsupply.com/sifive/hifive-unleashed The expansion board still lists a price: https://www.crowdsupply.com/microsemi/hifive-unleashed-expansion-board https://www.crowdsupply.com/microsemi/hifive-unleashed-expan... From memory, the HiFive Unleashed was on the order of $1000. The FAQ discusses why the price is high, they're planning for it to come down as demand ramps up. There's also an Arduino-like embedded board: https://www.crowdsupply.com/sifive/hifive1 https://www.crowdsupply.com/sifive/hifive1
- poizan42 8y agoThe price for the initial batch was $999 a piece. Unless you can buy one from one of the initial backers I think you will have to wait for them to produce more of them.
- 8y ago
- sbmthakur 8y agoThe article misspells it as 'Shakrti' in the body. Posting here because there is no comment section on the blog.
- zaarn 8y agoWhat's the price point of one of these processors? The article doesn't seem to be clear on this.
- pkphilip 8y agoFrom what I can gather, this is only in the test stage and has not yet been fabricated yet. They are testing this using FPGA
- testingforwhat 8y agoNo, it's a test chip manufactured using Intel's 22 nm process: https://twitter.com/ShaktiProcessor/status/1023274380430921728 https://twitter.com/ShaktiProcessor/status/10232743804309217...
- oklababa 8y agothis is the best news i ahve seen so far
- moh_maya 8y agoPrevious discussion, about 8 months ago: https://news.ycombinator.com/item?id=15684225 https://news.ycombinator.com/item?id=15684225
- signa11 8y agosorry, but this is not the same _discussion_ article you have referred to, was an introduction to the shakti project, but now linux is booting on the cpu. two, very different things.
- srean 8y agoI do not take these links to mean, "why are you posting this, we have already discussed this", but as "here's related conversation that you might find interesting and relevant". Such crosslinking is a true service.
- signa11 8y agoah, i was inadvertently conflating that with this. thanks for your clarification, and as you have pointed out, it most definitely is quite valuable.
- zhte415 8y agoIf others are curious what Shakti means, as I was, here's the Wikipedia summary > Shakti is the concept or personification of divine feminine creative power, sometimes referred to as “The Great Divine Mother” in Hinduism. As a mother, she is known as “Adi Shakti” or “Adi Parashakti”. On the earthly plane, Shakti most actively manifests through female embodiment and creativity/fertility, though it is also present in males in its potential, unmanifest form.[3] Hindus believe that Shakti is both responsible for creation and the agent of all change. Shakti is cosmic existence as well as liberation, its most significant form being the Kundalini Shakti, a mysterious psychospiritual force.[4][5] > In Shaktism, Shakti is worshipped as the Supreme Being. Shakti embodies the active feminine energy of Shiva and is synonymously identified with Tripura Sundari or Parvati. https://en.wikipedia.org/wiki/Shakti https://en.wikipedia.org/wiki/Shakti
- z3phyr 8y agoIn everyday speech, it generally means power/strength.
- nickik 8y agoThey called it POWER because initially they wanted to us the POWER ISA rather then RISC-V. Luckily they switched over.
- zokier 8y agoWhy luckily? Whats wrong with POWER?
- Keyframe 8y agoNot (as) open!
- nickik 8y agoBecause RISC-V is an open ISA. POWER would have been made in India in terms of 'you patents are not valid here' and not have been usable outside of India. RISC-V also is becoming the standard for research and the open-hardware community. Now the Indians can share and collaborate with the open-hardware community.
- msravi 8y agoSo it appears that this is taped out using Intel's 22nm FinFET process. https://twitter.com/ShaktiProcessor/status/1023274380430921728?s=20 https://twitter.com/ShaktiProcessor/status/10232743804309217...
- Keyframe 8y agoFew things excite me as RISC-V. Hardware is in dire need of major disruption and it's starting to happen, a bit by bit. Hardware manufacturing as well needs disruption, but that's an ultra hard mountain to climb, for now.