| Foreword |
|
xi | |
| Preface |
|
xv | |
|
|
|
1 | (10) |
|
|
|
2 | (3) |
|
|
|
3 | (1) |
|
|
|
3 | (2) |
|
|
|
5 | (1) |
|
|
|
5 | (2) |
|
Defining Success and Failure |
|
|
6 | (1) |
|
|
|
7 | (1) |
|
|
|
7 | (2) |
|
The Business of Excellence |
|
|
9 | (2) |
|
|
|
11 | (32) |
|
|
|
11 | (1) |
|
|
|
12 | (8) |
|
|
|
13 | (2) |
|
|
|
15 | (1) |
|
|
|
15 | (1) |
|
Setting the Leadership Tone |
|
|
16 | (1) |
|
|
|
17 | (1) |
|
|
|
17 | (1) |
|
The Storage Room Solution |
|
|
18 | (1) |
|
|
|
19 | (1) |
|
|
|
19 | (1) |
|
|
|
20 | (4) |
|
|
|
21 | (1) |
|
The ``What Would Happen If'' Game |
|
|
22 | (1) |
|
|
|
23 | (1) |
|
|
|
24 | (6) |
|
|
|
25 | (1) |
|
|
|
25 | (1) |
|
Floating-Point Chickens and Eggs |
|
|
26 | (1) |
|
|
|
26 | (1) |
|
|
|
27 | (1) |
|
All Design Teams Are Not Equal |
|
|
28 | (1) |
|
Overpromise or Overdeliver? |
|
|
28 | (2) |
|
|
|
30 | (4) |
|
|
|
30 | (1) |
|
|
|
31 | (1) |
|
|
|
31 | (1) |
|
|
|
31 | (1) |
|
|
|
32 | (1) |
|
|
|
33 | (1) |
|
Not-So-Secret Instructions |
|
|
33 | (1) |
|
Help from the Software World |
|
|
33 | (1) |
|
The Truth about Hardware and Software |
|
|
33 | (1) |
|
Establishing the Design Team |
|
|
34 | (9) |
|
Roles and Responsibilities |
|
|
35 | (1) |
|
|
|
36 | (1) |
|
|
|
37 | (1) |
|
Making Microcode a Special Case |
|
|
38 | (1) |
|
|
|
39 | (1) |
|
Architects, Engineers, and Schedules |
|
|
40 | (1) |
|
|
|
41 | (2) |
|
|
|
43 | (36) |
|
|
|
44 | (1) |
|
|
|
45 | (6) |
|
Handling the Nonquantifiable |
|
|
45 | (1) |
|
Managing New Perspectives |
|
|
46 | (1) |
|
|
|
47 | (1) |
|
|
|
48 | (3) |
|
|
|
51 | (8) |
|
|
|
51 | (2) |
|
Engineering Change Orders |
|
|
53 | (1) |
|
|
|
53 | (1) |
|
|
|
54 | (1) |
|
|
|
55 | (1) |
|
Timely Resolution, No Pocket Vetoes |
|
|
56 | (1) |
|
|
|
57 | (1) |
|
ECO Control and the Project POR |
|
|
57 | (2) |
|
The Bridge from Architecture to Design |
|
|
59 | (2) |
|
|
|
60 | (1) |
|
|
|
61 | (14) |
|
Mismanaging Design Errors |
|
|
62 | (1) |
|
Make an Example of the Offender |
|
|
62 | (1) |
|
|
|
62 | (1) |
|
|
|
62 | (1) |
|
|
|
63 | (1) |
|
|
|
63 | (2) |
|
When Bugs Get In Anyway, Find Them Before Production |
|
|
65 | (1) |
|
|
|
66 | (1) |
|
|
|
67 | (2) |
|
|
|
69 | (2) |
|
Plan to Survive Bugs that Make It to Production |
|
|
71 | (1) |
|
A Six-Step Plan for High Product Quality |
|
|
72 | (1) |
|
|
|
73 | (1) |
|
|
|
74 | (1) |
|
|
|
75 | (1) |
|
Another One Rides the Bus |
|
|
75 | (4) |
|
|
|
79 | (36) |
|
|
|
80 | (1) |
|
|
|
81 | (3) |
|
|
|
81 | (1) |
|
Documentation and Communication |
|
|
82 | (1) |
|
|
|
82 | (1) |
|
Integrating Architects and Design Engineers |
|
|
83 | (1) |
|
Performance and Feature Trade-offs |
|
|
84 | (5) |
|
(Over-) Optimizing Performance |
|
|
84 | (1) |
|
Perfect A; Mediocre B, C, and D |
|
|
84 | (1) |
|
The Technical Purity Trap |
|
|
84 | (1) |
|
|
|
85 | (2) |
|
Performance-Monitoring Facilities |
|
|
87 | (1) |
|
|
|
87 | (1) |
|
Protecting the Family Jewels |
|
|
88 | (1) |
|
|
|
88 | (1) |
|
Gratuitous Innovation Considered Harmful |
|
|
89 | (1) |
|
Validation and Model Health |
|
|
90 | (3) |
|
|
|
90 | (1) |
|
|
|
91 | (1) |
|
Health and the Tapeout Target |
|
|
92 | (1) |
|
|
|
93 | (1) |
|
Coordinating with Other Projects |
|
|
93 | (5) |
|
|
|
94 | (1) |
|
|
|
94 | (2) |
|
|
|
96 | (1) |
|
|
|
96 | (2) |
|
|
|
98 | (17) |
|
Awards, Rewards, and Recognition |
|
|
98 | (2) |
|
|
|
100 | (3) |
|
Project Management by Grass Cutting |
|
|
103 | (2) |
|
Marginal Return from Incremental Heads |
|
|
105 | (1) |
|
|
|
106 | (3) |
|
|
|
109 | (1) |
|
The Mystery of the Unchanging Curve |
|
|
109 | (1) |
|
Flexibility Is Required of All |
|
|
110 | (2) |
|
The Simplification Effort |
|
|
112 | (3) |
|
|
|
115 | (22) |
|
|
|
117 | (2) |
|
|
|
117 | (1) |
|
|
|
118 | (1) |
|
|
|
118 | (1) |
|
|
|
119 | (2) |
|
Prioritizing War Room Issues |
|
|
119 | (1) |
|
Managing the Microcode Patch Space |
|
|
120 | (1) |
|
|
|
121 | (8) |
|
|
|
121 | (1) |
|
|
|
122 | (2) |
|
|
|
124 | (3) |
|
Executive Pedagogy and Shopping Carts |
|
|
127 | (2) |
|
Managing to the Next Processor |
|
|
129 | (1) |
|
|
|
130 | (2) |
|
|
|
132 | (5) |
|
|
|
133 | (1) |
|
How Not to Give Magazine Interviews |
|
|
133 | (1) |
|
|
|
134 | (3) |
|
|
|
137 | (18) |
|
|
|
138 | (4) |
|
|
|
138 | (1) |
|
Hiring and the Promotion List |
|
|
139 | (2) |
|
|
|
141 | (1) |
|
|
|
142 | (8) |
|
|
|
143 | (2) |
|
The Led Zeppelin Incident |
|
|
145 | (1) |
|
Exiting the Exit Bag Check |
|
|
146 | (2) |
|
|
|
148 | (1) |
|
|
|
149 | (1) |
|
|
|
150 | (2) |
|
We Are So Rich, We Must Be Good |
|
|
152 | (1) |
|
|
|
153 | (2) |
|
Inquiring Minds Like Yours |
|
|
155 | (16) |
|
What was Intel thinking with that chip ID tag, which caused such a public uproar? |
|
|
155 | (1) |
|
Was the P6 project affected by the Pentium's floating point divider bug? |
|
|
156 | (3) |
|
Why did Pentium have a flawed floating point divider, when its predecessor, the i486, did not? |
|
|
159 | (1) |
|
How would you respond to the claim that the P6 is built on ideas stolen from Digital Equipment Corp.? |
|
|
160 | (1) |
|
What did the P6 team think about Intel's Itanium Processor Family? |
|
|
161 | (3) |
|
Is Intel the sweatshop some people say it is? |
|
|
164 | (2) |
|
How can I become the chief architect of a company such as Intel? |
|
|
166 | (1) |
|
|
|
167 | (1) |
|
And In Closing I'd Just Like To Say . . . |
|
|
168 | (3) |
|
|
|
171 | (2) |
|
|
|
173 | (6) |
|
Out-of-Order, Superscalar Microarchitecture: A Primer |
|
|
173 | (2) |
|
|
|
175 | (4) |
| Glossary |
|
179 | (6) |
| Index |
|
185 | |