I can't wait to see how this will affect battery life among other thinds (is Rembrant 6nm as well?) .
Certainly a much needed change, considering Cezanne was essentially Renoir with the CCX replaced and L3 doubled. There hasn't been much change to the uncore for 2 years.
I absolutely agree that with the rise of cheap NVMe storage, the most limited IO type on desktop are the pci x4/NVMe ports. I don't think the system needs to provide for all of those ports to work at the same time (people use extra slots for extra capacity, not for running superfast raid configs), and the extra latency for using a hub between the device and the CPU is negligible for storage uses. I suspect that AMD thinks so too, and that the B650 (if it's called that) has more PCIe lanes. Let's say, 3x4, with one of them splittable into individual pci/sata like the two lanes in B550, so a normal midrange B550 might have:
-1 PCIe x16 from the CPU
-1 NVMe x4 from the CPU
-2 NVMe x4 from the chipset
-2 PCIe x1 from the chipset
-2 sata 6GBps from the chipset.
Then a doubled up config would take the x4 from the CPU, but provide up to 3 extra x4 from the chipset.
X670 chipset is for AM5 platform and will introduce too the 12VO, the more heat generated by this chip can be explained because it's a MCM chip with two B650. It can explain why on chinese forum they talks about a X670 which is doubled compared to B650
In the meanwhile some leaker yesterday on Twitter said that Raphael will be launched at Computex, so earlier than some expected. To be taken with a big grain of salt, of course.
AMD to briefly talk about Zen4 at CES 2022 In an exclusive interview with Antony Leather (Forbes/CrazyTechLab), AMD CTO Mark Papermaster confirmed that Zen4 architecture will be part of the CES 2022 press conference, however, the primary focus will be on updated Zen3 architecture with 3D...
videocardz.com
If AMD starts to share details of Zen4 at CES, the Computex release may be not be far from reality. Or simply, as Genoa samples should be already in selected custormers' hands, they feel there is no point to keep it so tight anymore.
AMD to briefly talk about Zen4 at CES 2022 In an exclusive interview with Antony Leather (Forbes/CrazyTechLab), AMD CTO Mark Papermaster confirmed that Zen4 architecture will be part of the CES 2022 press conference, however, the primary focus will be on updated Zen3 architecture with 3D...
videocardz.com
If AMD starts to share details of Zen4 at CES, the Computex release may be not be far from reality. Or simply, as Genoa samples should be already in selected custormers' hands, they feel there is no point to keep it so tight anymore.
Interview is quite hilarious, Papermaster dodging questions with non statements and before you know it the interview is over and he has given out absolutely zero information.
But 18 months should be the expected time frame, right around Computex or thereabouts
The X670 is probably the cIOD used in Raphael but in 6nm will be expensive, AMD can just keep the cIOD which has defect on igfx to make with it the X670
Computex 2022 release for Raphael would be a nice surprise after all the speculation that it would be Q4. Nice of them to at least adhere to an 18 month cadence. We may see Raphael and Vermeer-X/Zen3d overlap after all!
The X670 is probably the cIOD used in Raphael but in 6nm will be expensive, AMD can just keep the cIOD which has defect on igfx to make with it the X670
This makes me more suspicious that there will not be any SP5 based Threadripper. Perhaps they will have AM5 go up to 3 cpu chiplets with an HEDT platform using 2 IO die to provide a lot more IO than the regular AM5. Perhaps I am misunderstanding though. An IO die will presumably have 32 pci-express gen 4,at least, possibly gen 5 capable. They could do something like an x8 from the cpu for each chip and provide 24 lanes out from each chip (some used for sata, usb, etc). That would allow close to Threadripper level IO (16 still left from cpu and 48 from chipset = 64 lanes). If they allowed pci-express gen 5 between the chiplets, that could provide more than current Threadripper level IO. Also, the trace lengths have been decreasing with each pci-express generation. Perhaps they daisy chain two IO die to significantly reduce trace lengths. That could actually reduce board cost and complexity. Perhaps an x8 pci-express 5 off cpu to chipset IO die, another x16 for IO, with the remaining x8 going to a second IO die. That could keep trace lengths very short. It wouldn’t make sense for a mini-itx board in that case.
The market position where Intel has no answer to Threadripper is why there isn't anything new in the pipeline. Just like Intel could get away with sitting on 4 core CPUs for all of those years, AMD can get away with continuing to sell existing TR parts.
They'll probably eventually have something new, but right now they're going to prioritize the areas where they can't rest of their laurels due to competition from Intel or they can make more money. Threadripper is in the awkward middle position where it's not quite as profitable as the server market and not nearly as contested as the desktop and mobile markets.
We'll get some new parts eventually, but there just isn't any pressure on AMD to do it as soon as some might like. Maybe there are some technical hurdles in there as well, but they're not vastly different from what would need to be solved for new server parts.
We have to remember, the current Threadripper lineup is quite different from it's origin as well. The WX high end parts are essentially Epyc parts that were repurposed into high end workstation parts either by choice, or because they didn't hit certain efficiency targets in binning. The WX line is a trivial offshoot of the server parts. The lower end Threadripper parts are different enough to require a bit more cost. They continue only because AMD is contractually obligated to continue to support the Zen2 server parts with CCDs. Since they must continue in production, those TR parts help with volume levels. They'll probably disappear when there is no longer a need to make Zen2 CCDs. Will there be a Zen3 low end TR part? Maybe if the chip shortage ever lets up. But, there's really no market need for it at present.
Many thanks to @Hans de Vries for this doc which I picked up from Twitter
One interesting take away from this diagram I was able to dig is DC-SCM, as you can judge from the standard, it is mostly written by Microsoft and Google.
Confidential computing at MS and Google using EPYC Milan is still in beta because of multiple reasons. But I can surmise these below reading some of the bulletins
MS, Google, TenCent, Oracle and few others identified some weaknesses in the whole chain of SEV.
There were vulnerabilities in some of the register access when using SEV SNP
Shortcomings in how the BIOS/EEPROM is accessed and the Versioned Chip Endorsement Key (VCEK) used for SEV is managed
Securing only the SW and CPU is not enough, you need to secure the whole HW platform.
Seems DC-SCM plans to secure the way BIOS and external EEPROM/Flash/Physical access is managed using an OCP module
AMD addressed major CVEs in SEV already with firmware update.
And the server ecosystem is also moving to secure the BMC/EEPROM/BIOS/etc as well.
Even JTAG access needs secure unlock, which should have been done long ago, but I guess if the VM is not even encrypted, no need to bother with JTAG access when you can access the process memory directly.
All in all a very impactful change that can be partly (or even majorly) attributed to the introduction of SEV and the CCP.
Doing the rounds right now is a lot of work from AMD and other partners like Google, Microsoft, Tencent and Oracle to bring in SEV-SNP upstream. (Downstream should already be available already)
In fact, hyper-v will have a new VM isolation mechanism written around SEV SNP
Seems Zen 4 will introduce some newer SEV features which Lisa showed in the main slide. (I read from LinkedIn there is a feature called VMG but not very clear what it does)
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.