Officially none of them were labelled with K'x'y' after Greyhound.
View attachment 61693
Before the switch to Family 10h Software Optimzation Guide, the actual Software Optimization Guide was Deerhound/Greyhound via DH/GH Software Optimization Guide.
View attachment 61692
However, information and valid sources point towards:
K9 = Greyhound
K10 = Bulldozer
Lead Architect of K9(Greyhound) - Mike Clark, for Greyhound being K9.
Greyhound was never called K10 at AMD.
Bulldozer was always called K10 at AMD.
So, if you want to be 100% accurate then. It is either Greyhound or K9, but not K10 since that is exclusively used for Bulldozer only at AMD. Just another symptom of one news outlet saying K10 because F10h and the misinformation echo chamber taking it away.
General idea you are shooting out Thunder 57:
From K7 architecture:
-> Architecture 1/Never leaked-only patent = K8
-> Architecture 2/Never leaked-only patent = K9
-> Fred Weber's Architecture = K10
-> Architecture 1/Leaked by Mitch Alsup and patented = K11
-> Architecture 2 = K12 (Greyhound)
Rather it was K7 (Argon):
Architectures that never came to be.. doesn't impact the count
Fred Weber's Architecture = K8 (Hammer)
Architectures that never came to be.. doesn't impact the count
Architecture that releases = K9 (Greyhound)
Bulldozer 45nm/32nm are both listed as K10 so, both iterations regardless of changes = K10 (Bulldozer)
The only reason Greyhound/Bulldozer are K9/K10 is because their microarchitecture project names K9/K10 were keep overs as for how old they were.
Dirk Meyer explanation in 2006 for changes from 2004 to => 2006:
K8 Revision
Hound => K9 Performance/Greyhound/Family 10h
K8 Revision
Leo => K9 Mobile/Lion/Family 11h
--- From a separate source shortly after ---
Bulldozer started under K10 in 2004, only getting Bulldozer around the same time as Greyhound.
Fred Weber => Phil Hester pretty much killed the K-iteration naming scheme. Opting for using core names or hexadecimal family numbers instead of K9/K10 post-2005.
Andy Glew:
July 2002-June 2004: Advanced Micro Devices (AMD), Sunnyvale, California. K10 architecture
View attachment 61731
Andy Glew:
Nov 15, 2009, 9:54:22 AM
"There were several K10s. While I wanted to work on low power when I went
to AMD, I was hired to consult on low power and do high end CPU, since
the low power project was already rolling and did not need a new chef.
The first K10 that I knew at AMD was a low power part. When that was
cancelled I was sent off on my lonesome, then wth Mike Haertel, to work
on a flagship, out-of-order, aggressive processor, while the original
low power team did something else. When that other low-power project was
cancelled, that team came over to the nascent K10 that I was working on.
My K10 was MCMT, plus a few other things. I had actually had to
promise Fred Weber that I would NOT do anything advanced for this K10 -
no SpMT, just MCMT. But when the other guys came on board, I thought
this meant that I could leave the easy stuff for them, while I tried to
figure out how to do SpMT and/or any other way of using MCMT to speed up
single threads. Part of my motivation was that I had just attended ISCA
2003 in San Diego, where several of outstanding problems in big machines
had been solved, and I was scared that Intel would come out with
something if we did not."
Chuck Moore got the architecture after Andy Glew left and himself joined and was there for the name change from K10 to Bulldozer. After which sometime around 2008 he became Senior Fellow for Accelerated Compute, handing K10(pre-2005)/Bulldozer(post-2005) to Mike Butler.
Timeline of Greyhound becoming K9:
2004 - AMD internally cancelled Ultra-Deep Pipeline Architecture (Original K9 that was cancelled).
2005 - Dirk Meyer and Phil Hester opts for evolutionary iteration to K9
Original K9/Ultra-Deep Pipeline Architecture was officially cancelled(told press that K9 5 GHz wasn't coming out), but DM/PH stated K8H(2004) had evolutionary improvements from K8 thus wasn't K8 but rather K9:
K7 - 32-bit
K8 - 64-bit
K9 - 128-bit (FE/LS/FPU changes for single-op 128-bit)
Family 10h && Greyhound = K9
Family 15h && Bulldozer = K10
Timeline of weirdness;
Under Andy Glew 2002+:
Processor = Core
Cluster A/B can only respectively run Thread A/B
Under Chuck Moore 2005+:
Processor = Core
Cluster A/B can respectively run Thread A/B and collaboratively run A or B.
Under Mike Butler 2008+:
Processor = Module
Core A/B can only respectively run Thread A/B.