News for hackers. Stuff that matters.
Re:Windows for Arm on M1 Mac Successfully Virtualized by bryanlarsen on Friday November 27, 2020 @03:09PM (#25232162)
Another option is AMD. Originally they were going to have a Zen variant that ran ARM. They shelved that plan once the x86 version of Zen showed promise, but there are rumours that the plan continues on the back burner.

https://en.wikipedia.org/wiki/AMD_K12

Re:Windows for Arm on M1 Mac Successfully Virtualized by ip26 on Friday November 27, 2020 @04:14PM (#25232620)
Dual ISA would be pretty cool. The more I learn about the differences between ARM and x86, the more it starts to seem like it really is not that much of a stretch. Just need the market for it.
Re:Windows for Arm on M1 Mac Successfully Virtualized by ineedasername on Friday November 27, 2020 @07:12PM (#25233814)
At this point it seems more and more that x86 is still around purely due to legacy reasons and path-dependency. Intel's failure to execute on mobile really opened the door for ARM to have tons of resources over a decade thrown into it's development as a platform, and now the M1 is and extremely solid proof of concept that tentative forways into ARM on desktops/laptops/servers will absolutely warrant the shift in platforms. A few years for software ports and an extra 2 generations of chip improvements, and I think Intel's failure to execute on it's fab processes will just become a moot point. I have more confidence in AMD to pivot, and they have their GPU business as well. Intel may be relegated to aging obsolescence the same way HP and IBM did with their "big iron".
Re:Windows for Arm on M1 Mac Successfully Virtualized by zinekeller on Saturday November 28, 2020 @10:06AM (#25237933)
> Intel may be relegated to aging obsolescence the same way HP and IBM did with their "big iron".

Cough cough Itanium is an Intel-HP collaboration cough cough

Re:Windows for Arm on M1 Mac Successfully Virtualized by ineedasername on Sunday November 29, 2020 @11:00PM (#25250604)
Hah, true. That was absolutely the wrong chip at the wrong time, poorly implemented and lacking the software base of other platforms. I have no idea why they built the thing rather than put more resources behind Xeon, which was basically the end result anyway.
Re:Windows for Arm on M1 Mac Successfully Virtualized by pabs3 on Friday November 27, 2020 @10:00PM (#25234850)
Multi-ISA chips have been announced from a couple of vendors (Loongson and Tachyum). The Loongson one does a MIPSish native ISA, MIPS, ARM, x86 and RISC-V, with the last three being slower.

https://www.zhihu.com/question/414069789 (needs Google Translate)

Re:Windows for Arm on M1 Mac Successfully Virtualized by mschuster91 on Friday November 27, 2020 @06:57PM (#25233709)
In the server market that could actually work, there are virtually no constraints on power or die size there.
Re:Windows for Arm on M1 Mac Successfully Virtualized by egsmi on Friday November 27, 2020 @07:27PM (#25233924)
There are plenty of constraints in the server markets. The primary ones are economic.
Re:Windows for Arm on M1 Mac Successfully Virtualized by api on Friday November 27, 2020 @03:37PM (#25232356)
AMD, Nvidia, and Marvell after the Cavium acquisition could do it. Intel could too but wouldn’t unless the x86 market tanked badly.
Re:Windows for Arm on M1 Mac Successfully Virtualized by m_mueller on Friday November 27, 2020 @03:53PM (#25232475)
> unless the x86 market tanked badly

That has always been a question of when, not if. And M1 shows that it is quickly approaching. In a market where physical limits have slowed down miniaturization, with just 5-10 years away from a standstill, a low efficiency instruction set focused on backwards binary compatibility is going to get washed out of most usecases very quickly. It's going the way of the IBM mainframe - still sold decades after its heyday, but marginalized to a niche (bunch of enterprise cloud instances for software that is too expensive to recompile/port).

Re:Windows for Arm on M1 Mac Successfully Virtualized by bryanlarsen on Friday November 27, 2020 @04:57PM (#25232926)
M1's awesomeness has almost nothing to do with the instruction set. AMD64 and ARM64 are very similar in terms of complexity.

M1's awesomeness has to do with:

- assembling a killer team - 5nm process - high speed, low latency DRAM - big-little

The only substantive difference between the AMD64 and ARM64 instruction sets is that ARM64 has a more relaxed memory model.

Re:Windows for Arm on M1 Mac Successfully Virtualized by api on Friday November 27, 2020 @05:18PM (#25233055)
Not true from what I’ve read. The problem with x86 is not complexity but variable instruction lengths. This makes it hard to determine instruction boundaries, complicating decoders and making more than 4-way decode hard. M1 has 8 decoders for comparison, and it would be easy to have 100 with ARM if there were a benefit to that many.
Re:Windows for Arm on M1 Mac Successfully Virtualized by bryanlarsen on Friday November 27, 2020 @07:15PM (#25233836)
1. AMD64 is a lot easier to decode than the legacy i86 8/16/32 bit instruction set.

2. Decoding took a significant portion of the chip when they were a million transistors. The m1 has 16 billion resistors, decoding is a much less significant fraction of the chip.

Re:Windows for Arm on M1 Mac Successfully Virtualized by petra on Friday November 27, 2020 @08:00PM (#25234140)
Complexity isn't only about transistors, but also about delay.

And sure, there's pipelining but than your limited by latency.

Re:Windows for Arm on M1 Mac Successfully Virtualized by ben-schaaf on Friday November 27, 2020 @08:17PM (#25234238)
> The limitation of the x86 decoder is that each clock cycle can only process up to 4 instructions, but if it is a familiar instruction, it can be placed in the operation cache, and 8 instructions can be processed per cycle.

http://www.apothetech.com/amd-zen-3-vs-zen-2-amd-zen-3-is-39...

Re:Windows for Arm on M1 Mac Successfully Virtualized by gumby on Friday November 27, 2020 @03:57PM (#25232515)
Back in the Andy Grove era Intel exited its original business (memory) while it was profitable, foreseeing its rapid commoditization. The Intel of today sold off its excellent ARM business (acquired from DEC) and is incapable of doing anything but ride a sinking ship to doom.
Re:Windows for Arm on M1 Mac Successfully Virtualized by tmzt on Friday November 27, 2020 @06:55PM (#25233699)
At the time, StrongARM and PXA dominated PDAs and smartphones, while the higher-end parts were used in storage devices.

It's a little confusing still why they sold the whole thing while the market was growing.

Marvell seemingly abandoned portable devices and rolled IXP(?) into their own lines for a time.

Re:Windows for Arm on M1 Mac Successfully Virtualized by nolok on Saturday November 28, 2020 @06:50AM (#25237027)
Eh, Intel was so scared of itself it even stopped Atom getting properly powerful, and that was x86. No way they will get into the ARM team, the instant what they build starts being powerful they will get scared of it too and kill it.

A good part of why they take such a beating in x86 too, Intel has no backup plan because they're scared of their own backup up, while being oblivious to the fact that it was their backup plan that saved them during the post-P4 era.

At least AMD is not scared of throwing away their arch every few years and restart, they've pretty much been doing that like clockwork every five years for the past two decades.

Re:Windows for Arm on M1 Mac Successfully Virtualized by bitcoinmoney on Friday November 27, 2020 @09:53PM (#25234808)
It’s not the ISA that matters. But the execution of the project. Apple just showed it can make fast ARM. Is M1 faster than the latest zen?
Re:Windows for Arm on M1 Mac Successfully Virtualized by sudosysgen on Friday November 27, 2020 @11:04PM (#25235169)
No, it isn't. It's toe-to-toe on single core performance, sometimes faster, but slower in multicore.
Re:Windows for Arm on M1 Mac Successfully Virtualized by socialdemocrat on Saturday November 28, 2020 @12:18AM (#25235479)
Yeah but zen3 only pulls off matching M1 Firestorm by using 60% higher clock frequency and thus running a lot hotter.

At same clock frequency t he Zen3 would have been destroyed by the M1

Re:Windows for Arm on M1 Mac Successfully Virtualized by deeringc on Saturday November 28, 2020 @01:17AM (#25235689)
Yes, but Apple also used their financial muscle to secure all of the 5nm capacity from TSMC. We're not comparing apples with apples here.
Re:Windows for Arm on M1 Mac Successfully Virtualized by ksec on Saturday November 28, 2020 @02:43AM (#25236023)
>Apple also used their financial muscle to secure all of the 5nm capacity from TSMC

It would be more accurate to describe Apple was the only customer willing to pay and has enough volume.

Re:Windows for Arm on M1 Mac Successfully Virtualized by 29083011397778 on Saturday November 28, 2020 @03:20AM (#25236169)
If you mean AMD couldn't match what Apple was willing to pay when you say "Apple was the only customer willing to pay", then absolutely. Otherwise, when push comes to shove in a bidding war with Apple, I don't think AMD really has a chance.
Re:Windows for Arm on M1 Mac Successfully Virtualized by starfallg on Saturday November 28, 2020 @05:31AM (#25236781)
That's grossly mis-characterising the relationship between clock speed, performance and power consumption/heat dissipation in chip design.
Re:Windows for Arm on M1 Mac Successfully Virtualized by sudosysgen on Saturday November 28, 2020 @02:27PM (#25239808)
And yet at the same power in multicore tasks Zen 2 outperforms the M1.
Re:Windows for Arm on M1 Mac Successfully Virtualized by DCKing on Friday November 27, 2020 @05:02PM (#25232957)
> Originally they were going to have a Zen variant that ran ARM.

Was AMD's K12 related to Zen in any way? AMD's predecessor to that, the Opteron A1100 series, was bog standard Cortex A57 cores. I figured K12 would be at best an evolution of a standard ARM design, but if it was more that would be very interesting. Would love to know more about this.

Re:Windows for Arm on M1 Mac Successfully Virtualized by deaddodo on Friday November 27, 2020 @05:34PM (#25233156)
It wasn't a Zen variant; but the K12 was intended to be AMD's custom ARM uArch aimed at the server space. So there's a good chance it would have been focused on performance over power efficiency.
Re:Windows for Arm on M1 Mac Successfully Virtualized by gumby on Friday November 27, 2020 @08:43PM (#25234377)
Power efficiency is an issue in the datacenter as well as you have to get that heat out, which also takes power.
Re:Windows for Arm on M1 Mac Successfully Virtualized by deaddodo on Friday November 27, 2020 @10:44PM (#25235084)
I said over, as in relative to other ARM uArchs. Clearly, the power efficiency was the main draw of the proposal in the first place.