]>
Commit | Line | Data |
---|---|---|
162ed594 | 1 | /** @file\r |
797a9d67 | 2 | DXE Dispatcher.\r |
28a00297 | 3 | \r |
4 | Step #1 - When a FV protocol is added to the system every driver in the FV\r | |
022c6d45 | 5 | is added to the mDiscoveredList. The SOR, Before, and After Depex are\r |
6 | pre-processed as drivers are added to the mDiscoveredList. If an Apriori\r | |
7 | file exists in the FV those drivers are addeded to the\r | |
8 | mScheduledQueue. The mFvHandleList is used to make sure a\r | |
28a00297 | 9 | FV is only processed once.\r |
10 | \r | |
11 | Step #2 - Dispatch. Remove driver from the mScheduledQueue and load and\r | |
022c6d45 | 12 | start it. After mScheduledQueue is drained check the\r |
13 | mDiscoveredList to see if any item has a Depex that is ready to\r | |
28a00297 | 14 | be placed on the mScheduledQueue.\r |
15 | \r | |
022c6d45 | 16 | Step #3 - Adding to the mScheduledQueue requires that you process Before\r |
28a00297 | 17 | and After dependencies. This is done recursively as the call to add\r |
022c6d45 | 18 | to the mScheduledQueue checks for Before and recursively adds\r |
19 | all Befores. It then addes the item that was passed in and then\r | |
28a00297 | 20 | processess the After dependecies by recursively calling the routine.\r |
21 | \r | |
22 | Dispatcher Rules:\r | |
022c6d45 | 23 | The rules for the dispatcher are in chapter 10 of the DXE CIS. Figure 10-3\r |
28a00297 | 24 | is the state diagram for the DXE dispatcher\r |
25 | \r | |
26 | Depex - Dependency Expresion.\r | |
27 | SOR - Schedule On Request - Don't schedule if this bit is set.\r | |
28 | \r | |
23c98c94 | 29 | Copyright (c) 2006 - 2008, Intel Corporation. <BR>\r |
30 | All rights reserved. This program and the accompanying materials\r | |
31 | are licensed and made available under the terms and conditions of the BSD License\r | |
32 | which accompanies this distribution. The full text of the license may be found at\r | |
33 | http://opensource.org/licenses/bsd-license.php\r | |
34 | \r | |
35 | THE PROGRAM IS DISTRIBUTED UNDER THE BSD LICENSE ON AN "AS IS" BASIS,\r | |
36 | WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED.\r | |
797a9d67 | 37 | \r |
38 | **/\r | |
28a00297 | 39 | \r |
9c4ac31c | 40 | #include "DxeMain.h"\r |
28a00297 | 41 | \r |
42 | //\r | |
43 | // The Driver List contains one copy of every driver that has been discovered.\r | |
44 | // Items are never removed from the driver list. List of EFI_CORE_DRIVER_ENTRY\r | |
45 | //\r | |
022c6d45 | 46 | LIST_ENTRY mDiscoveredList = INITIALIZE_LIST_HEAD_VARIABLE (mDiscoveredList);\r |
28a00297 | 47 | \r |
48 | //\r | |
49 | // Queue of drivers that are ready to dispatch. This queue is a subset of the\r | |
50 | // mDiscoveredList.list of EFI_CORE_DRIVER_ENTRY.\r | |
51 | //\r | |
52 | LIST_ENTRY mScheduledQueue = INITIALIZE_LIST_HEAD_VARIABLE (mScheduledQueue);\r | |
53 | \r | |
54 | //\r | |
55 | // List of handles who's Fv's have been parsed and added to the mFwDriverList.\r | |
56 | //\r | |
57 | LIST_ENTRY mFvHandleList = INITIALIZE_LIST_HEAD_VARIABLE (mFvHandleList); // list of KNOWN_HANDLE\r | |
58 | \r | |
59 | //\r | |
60 | // Lock for mDiscoveredList, mScheduledQueue, gDispatcherRunning.\r | |
61 | //\r | |
62 | EFI_LOCK mDispatcherLock = EFI_INITIALIZE_LOCK_VARIABLE (TPL_HIGH_LEVEL);\r | |
63 | \r | |
64 | \r | |
65 | //\r | |
66 | // Flag for the DXE Dispacher. TRUE if dispatcher is execuing.\r | |
67 | //\r | |
68 | BOOLEAN gDispatcherRunning = FALSE;\r | |
69 | \r | |
70 | //\r | |
71 | // Module globals to manage the FwVol registration notification event\r | |
72 | //\r | |
73 | EFI_EVENT mFwVolEvent;\r | |
74 | VOID *mFwVolEventRegistration;\r | |
75 | \r | |
76 | //\r | |
77 | // List of file types supported by dispatcher\r | |
78 | //\r | |
022c6d45 | 79 | EFI_FV_FILETYPE mDxeFileTypes[] = {\r |
80 | EFI_FV_FILETYPE_DRIVER,\r | |
81 | EFI_FV_FILETYPE_COMBINED_PEIM_DRIVER,\r | |
28a00297 | 82 | EFI_FV_FILETYPE_DXE_CORE,\r |
83 | EFI_FV_FILETYPE_FIRMWARE_VOLUME_IMAGE\r | |
84 | };\r | |
85 | \r | |
86 | typedef struct {\r | |
87 | MEDIA_FW_VOL_FILEPATH_DEVICE_PATH File;\r | |
88 | EFI_DEVICE_PATH_PROTOCOL End;\r | |
89 | } FV_FILEPATH_DEVICE_PATH;\r | |
90 | \r | |
91 | FV_FILEPATH_DEVICE_PATH mFvDevicePath;\r | |
92 | \r | |
93 | \r | |
94 | //\r | |
95 | // Function Prototypes\r | |
96 | //\r | |
162ed594 | 97 | /**\r |
98 | Insert InsertedDriverEntry onto the mScheduledQueue. To do this you\r | |
99 | must add any driver with a before dependency on InsertedDriverEntry first.\r | |
100 | You do this by recursively calling this routine. After all the Befores are\r | |
101 | processed you can add InsertedDriverEntry to the mScheduledQueue.\r | |
102 | Then you can add any driver with an After dependency on InsertedDriverEntry\r | |
103 | by recursively calling this routine.\r | |
104 | \r | |
105 | @param InsertedDriverEntry The driver to insert on the ScheduledLink Queue\r | |
106 | \r | |
107 | **/\r | |
28a00297 | 108 | VOID\r |
109 | CoreInsertOnScheduledQueueWhileProcessingBeforeAndAfter (\r | |
110 | IN EFI_CORE_DRIVER_ENTRY *InsertedDriverEntry\r | |
111 | );\r | |
022c6d45 | 112 | \r |
162ed594 | 113 | /**\r |
114 | Event notification that is fired every time a FV dispatch protocol is added.\r | |
115 | More than one protocol may have been added when this event is fired, so you\r | |
116 | must loop on CoreLocateHandle () to see how many protocols were added and\r | |
117 | do the following to each FV:\r | |
118 | If the Fv has already been processed, skip it. If the Fv has not been\r | |
119 | processed then mark it as being processed, as we are about to process it.\r | |
120 | Read the Fv and add any driver in the Fv to the mDiscoveredList.The\r | |
121 | mDiscoveredList is never free'ed and contains variables that define\r | |
122 | the other states the DXE driver transitions to..\r | |
123 | While you are at it read the A Priori file into memory.\r | |
124 | Place drivers in the A Priori list onto the mScheduledQueue.\r | |
125 | \r | |
022c6d45 | 126 | @param Event The Event that is being processed, not used.\r |
162ed594 | 127 | @param Context Event Context, not used.\r |
128 | \r | |
129 | **/\r | |
28a00297 | 130 | VOID\r |
131 | EFIAPI\r | |
132 | CoreFwVolEventProtocolNotify (\r | |
133 | IN EFI_EVENT Event,\r | |
134 | IN VOID *Context\r | |
135 | );\r | |
136 | \r | |
162ed594 | 137 | /**\r |
022c6d45 | 138 | Convert FvHandle and DriverName into an EFI device path\r |
162ed594 | 139 | \r |
022c6d45 | 140 | @param Fv Fv protocol, needed to read Depex info out of\r |
141 | FLASH.\r | |
142 | @param FvHandle Handle for Fv, needed in the\r | |
143 | EFI_CORE_DRIVER_ENTRY so that the PE image can be\r | |
144 | read out of the FV at a later time.\r | |
145 | @param DriverName Name of driver to add to mDiscoveredList.\r | |
162ed594 | 146 | \r |
147 | @return Pointer to device path constructed from FvHandle and DriverName\r | |
148 | \r | |
149 | **/\r | |
28a00297 | 150 | EFI_DEVICE_PATH_PROTOCOL *\r |
151 | CoreFvToDevicePath (\r | |
0c2b5da8 | 152 | IN EFI_FIRMWARE_VOLUME2_PROTOCOL *Fv,\r |
28a00297 | 153 | IN EFI_HANDLE FvHandle,\r |
154 | IN EFI_GUID *DriverName\r | |
155 | );\r | |
156 | \r | |
162ed594 | 157 | /**\r |
158 | Add an entry to the mDiscoveredList. Allocate memory to store the DriverEntry,\r | |
159 | and initilize any state variables. Read the Depex from the FV and store it\r | |
160 | in DriverEntry. Pre-process the Depex to set the SOR, Before and After state.\r | |
161 | The Discovered list is never free'ed and contains booleans that represent the\r | |
162 | other possible DXE driver states.\r | |
163 | \r | |
022c6d45 | 164 | @param Fv Fv protocol, needed to read Depex info out of\r |
165 | FLASH.\r | |
166 | @param FvHandle Handle for Fv, needed in the\r | |
167 | EFI_CORE_DRIVER_ENTRY so that the PE image can be\r | |
168 | read out of the FV at a later time.\r | |
169 | @param DriverName Name of driver to add to mDiscoveredList.\r | |
162ed594 | 170 | \r |
022c6d45 | 171 | @retval EFI_SUCCESS If driver was added to the mDiscoveredList.\r |
172 | @retval EFI_ALREADY_STARTED The driver has already been started. Only one\r | |
173 | DriverName may be active in the system at any one\r | |
162ed594 | 174 | time.\r |
175 | \r | |
176 | **/\r | |
28a00297 | 177 | EFI_STATUS\r |
178 | CoreAddToDriverList (\r | |
23c98c94 | 179 | IN EFI_FIRMWARE_VOLUME2_PROTOCOL *Fv,\r |
180 | IN EFI_HANDLE FvHandle,\r | |
181 | IN EFI_GUID *DriverName\r | |
28a00297 | 182 | );\r |
183 | \r | |
162ed594 | 184 | /**\r |
185 | Get the driver from the FV through driver name, and produce a FVB protocol on FvHandle.\r | |
186 | \r | |
022c6d45 | 187 | @param Fv The FIRMWARE_VOLUME protocol installed on the FV.\r |
188 | @param FvHandle The handle which FVB protocol installed on.\r | |
189 | @param DriverName The driver guid specified.\r | |
162ed594 | 190 | \r |
022c6d45 | 191 | @retval EFI_OUT_OF_RESOURCES No enough memory or other resource.\r |
192 | @retval EFI_VOLUME_CORRUPTED Corrupted volume.\r | |
162ed594 | 193 | @retval EFI_SUCCESS Function successfully returned.\r |
194 | \r | |
195 | **/\r | |
022c6d45 | 196 | EFI_STATUS\r |
28a00297 | 197 | CoreProcessFvImageFile (\r |
0c2b5da8 | 198 | IN EFI_FIRMWARE_VOLUME2_PROTOCOL *Fv,\r |
28a00297 | 199 | IN EFI_HANDLE FvHandle,\r |
200 | IN EFI_GUID *DriverName\r | |
201 | );\r | |
202 | \r | |
162ed594 | 203 | \r |
204 | /**\r | |
205 | Enter critical section by gaining lock on mDispatcherLock.\r | |
206 | \r | |
207 | **/\r | |
28a00297 | 208 | VOID\r |
209 | CoreAcquireDispatcherLock (\r | |
210 | VOID\r | |
211 | )\r | |
28a00297 | 212 | {\r |
213 | CoreAcquireLock (&mDispatcherLock);\r | |
214 | }\r | |
215 | \r | |
162ed594 | 216 | \r |
217 | /**\r | |
218 | Exit critical section by releasing lock on mDispatcherLock.\r | |
219 | \r | |
220 | **/\r | |
28a00297 | 221 | VOID\r |
222 | CoreReleaseDispatcherLock (\r | |
223 | VOID\r | |
224 | )\r | |
28a00297 | 225 | {\r |
226 | CoreReleaseLock (&mDispatcherLock);\r | |
227 | }\r | |
228 | \r | |
28a00297 | 229 | \r |
162ed594 | 230 | /**\r |
28a00297 | 231 | Read Depex and pre-process the Depex for Before and After. If Section Extraction\r |
232 | protocol returns an error via ReadSection defer the reading of the Depex.\r | |
233 | \r | |
022c6d45 | 234 | @param DriverEntry Driver to work on.\r |
28a00297 | 235 | \r |
022c6d45 | 236 | @retval EFI_SUCCESS Depex read and preprossesed\r |
237 | @retval EFI_PROTOCOL_ERROR The section extraction protocol returned an error\r | |
238 | and Depex reading needs to be retried.\r | |
162ed594 | 239 | @retval Error DEPEX not found.\r |
28a00297 | 240 | \r |
162ed594 | 241 | **/\r |
162ed594 | 242 | EFI_STATUS\r |
243 | CoreGetDepexSectionAndPreProccess (\r | |
244 | IN EFI_CORE_DRIVER_ENTRY *DriverEntry\r | |
245 | )\r | |
28a00297 | 246 | {\r |
247 | EFI_STATUS Status;\r | |
248 | EFI_SECTION_TYPE SectionType;\r | |
249 | UINT32 AuthenticationStatus;\r | |
0c2b5da8 | 250 | EFI_FIRMWARE_VOLUME2_PROTOCOL *Fv;\r |
28a00297 | 251 | \r |
022c6d45 | 252 | \r |
28a00297 | 253 | Fv = DriverEntry->Fv;\r |
254 | \r | |
255 | //\r | |
256 | // Grab Depex info, it will never be free'ed.\r | |
257 | //\r | |
258 | SectionType = EFI_SECTION_DXE_DEPEX;\r | |
259 | Status = Fv->ReadSection (\r | |
022c6d45 | 260 | DriverEntry->Fv,\r |
28a00297 | 261 | &DriverEntry->FileName,\r |
022c6d45 | 262 | SectionType,\r |
263 | 0,\r | |
264 | &DriverEntry->Depex,\r | |
28a00297 | 265 | (UINTN *)&DriverEntry->DepexSize,\r |
266 | &AuthenticationStatus\r | |
267 | );\r | |
268 | if (EFI_ERROR (Status)) {\r | |
269 | if (Status == EFI_PROTOCOL_ERROR) {\r | |
270 | //\r | |
271 | // The section extraction protocol failed so set protocol error flag\r | |
272 | //\r | |
273 | DriverEntry->DepexProtocolError = TRUE;\r | |
274 | } else {\r | |
275 | //\r | |
8a7d75b0 | 276 | // If no Depex assume UEFI 2.0 driver model\r |
28a00297 | 277 | //\r |
278 | DriverEntry->Depex = NULL;\r | |
279 | DriverEntry->Dependent = TRUE;\r | |
280 | DriverEntry->DepexProtocolError = FALSE;\r | |
281 | }\r | |
282 | } else {\r | |
283 | //\r | |
284 | // Set Before, After, and Unrequested state information based on Depex\r | |
285 | // Driver will be put in Dependent or Unrequested state\r | |
286 | //\r | |
287 | CorePreProcessDepex (DriverEntry);\r | |
288 | DriverEntry->DepexProtocolError = FALSE;\r | |
022c6d45 | 289 | }\r |
28a00297 | 290 | \r |
291 | return Status;\r | |
292 | }\r | |
293 | \r | |
162ed594 | 294 | \r |
295 | /**\r | |
296 | Check every driver and locate a matching one. If the driver is found, the Unrequested\r | |
297 | state flag is cleared.\r | |
298 | \r | |
022c6d45 | 299 | @param FirmwareVolumeHandle The handle of the Firmware Volume that contains\r |
300 | the firmware file specified by DriverName.\r | |
301 | @param DriverName The Driver name to put in the Dependent state.\r | |
162ed594 | 302 | \r |
022c6d45 | 303 | @retval EFI_SUCCESS The DriverName was found and it's SOR bit was\r |
304 | cleared\r | |
305 | @retval EFI_NOT_FOUND The DriverName does not exist or it's SOR bit was\r | |
306 | not set.\r | |
162ed594 | 307 | \r |
308 | **/\r | |
28a00297 | 309 | EFI_STATUS\r |
310 | EFIAPI\r | |
311 | CoreSchedule (\r | |
312 | IN EFI_HANDLE FirmwareVolumeHandle,\r | |
313 | IN EFI_GUID *DriverName\r | |
314 | )\r | |
28a00297 | 315 | {\r |
316 | LIST_ENTRY *Link;\r | |
317 | EFI_CORE_DRIVER_ENTRY *DriverEntry;\r | |
318 | \r | |
319 | //\r | |
320 | // Check every driver\r | |
321 | //\r | |
322 | for (Link = mDiscoveredList.ForwardLink; Link != &mDiscoveredList; Link = Link->ForwardLink) {\r | |
323 | DriverEntry = CR(Link, EFI_CORE_DRIVER_ENTRY, Link, EFI_CORE_DRIVER_ENTRY_SIGNATURE);\r | |
324 | if (DriverEntry->FvHandle == FirmwareVolumeHandle &&\r | |
022c6d45 | 325 | DriverEntry->Unrequested &&\r |
28a00297 | 326 | CompareGuid (DriverName, &DriverEntry->FileName)) {\r |
327 | //\r | |
328 | // Move the driver from the Unrequested to the Dependent state\r | |
329 | //\r | |
330 | CoreAcquireDispatcherLock ();\r | |
331 | DriverEntry->Unrequested = FALSE;\r | |
332 | DriverEntry->Dependent = TRUE;\r | |
333 | CoreReleaseDispatcherLock ();\r | |
022c6d45 | 334 | \r |
28a00297 | 335 | return EFI_SUCCESS;\r |
336 | }\r | |
337 | }\r | |
022c6d45 | 338 | return EFI_NOT_FOUND;\r |
28a00297 | 339 | }\r |
340 | \r | |
341 | \r | |
162ed594 | 342 | \r |
343 | /**\r | |
e94a9ff7 | 344 | Convert a driver from the Untrused back to the Scheduled state.\r |
162ed594 | 345 | \r |
022c6d45 | 346 | @param FirmwareVolumeHandle The handle of the Firmware Volume that contains\r |
347 | the firmware file specified by DriverName.\r | |
348 | @param DriverName The Driver name to put in the Scheduled state\r | |
162ed594 | 349 | \r |
022c6d45 | 350 | @retval EFI_SUCCESS The file was found in the untrusted state, and it\r |
351 | was promoted to the trusted state.\r | |
352 | @retval EFI_NOT_FOUND The file was not found in the untrusted state.\r | |
162ed594 | 353 | \r |
354 | **/\r | |
28a00297 | 355 | EFI_STATUS\r |
356 | EFIAPI\r | |
357 | CoreTrust (\r | |
358 | IN EFI_HANDLE FirmwareVolumeHandle,\r | |
359 | IN EFI_GUID *DriverName\r | |
360 | )\r | |
28a00297 | 361 | {\r |
362 | LIST_ENTRY *Link;\r | |
363 | EFI_CORE_DRIVER_ENTRY *DriverEntry;\r | |
364 | \r | |
365 | //\r | |
366 | // Check every driver\r | |
367 | //\r | |
368 | for (Link = mDiscoveredList.ForwardLink; Link != &mDiscoveredList; Link = Link->ForwardLink) {\r | |
369 | DriverEntry = CR(Link, EFI_CORE_DRIVER_ENTRY, Link, EFI_CORE_DRIVER_ENTRY_SIGNATURE);\r | |
370 | if (DriverEntry->FvHandle == FirmwareVolumeHandle &&\r | |
022c6d45 | 371 | DriverEntry->Untrusted &&\r |
28a00297 | 372 | CompareGuid (DriverName, &DriverEntry->FileName)) {\r |
373 | //\r | |
374 | // Transition driver from Untrusted to Scheduled state.\r | |
375 | //\r | |
376 | CoreAcquireDispatcherLock ();\r | |
377 | DriverEntry->Untrusted = FALSE;\r | |
378 | DriverEntry->Scheduled = TRUE;\r | |
379 | InsertTailList (&mScheduledQueue, &DriverEntry->ScheduledLink);\r | |
380 | CoreReleaseDispatcherLock ();\r | |
022c6d45 | 381 | \r |
28a00297 | 382 | return EFI_SUCCESS;\r |
383 | }\r | |
384 | }\r | |
022c6d45 | 385 | return EFI_NOT_FOUND;\r |
28a00297 | 386 | }\r |
387 | \r | |
388 | \r | |
28a00297 | 389 | \r |
162ed594 | 390 | /**\r |
391 | This is the main Dispatcher for DXE and it exits when there are no more\r | |
28a00297 | 392 | drivers to run. Drain the mScheduledQueue and load and start a PE\r |
162ed594 | 393 | image for each driver. Search the mDiscoveredList to see if any driver can\r |
28a00297 | 394 | be placed on the mScheduledQueue. If no drivers are placed on the\r |
395 | mScheduledQueue exit the function. On exit it is assumed the Bds()\r | |
162ed594 | 396 | will be called, and when the Bds() exits the Dispatcher will be called\r |
28a00297 | 397 | again.\r |
398 | \r | |
022c6d45 | 399 | @retval EFI_ALREADY_STARTED The DXE Dispatcher is already running\r |
400 | @retval EFI_NOT_FOUND No DXE Drivers were dispatched\r | |
401 | @retval EFI_SUCCESS One or more DXE Drivers were dispatched\r | |
28a00297 | 402 | \r |
162ed594 | 403 | **/\r |
162ed594 | 404 | EFI_STATUS\r |
405 | EFIAPI\r | |
406 | CoreDispatcher (\r | |
407 | VOID\r | |
408 | )\r | |
28a00297 | 409 | {\r |
410 | EFI_STATUS Status;\r | |
411 | EFI_STATUS ReturnStatus;\r | |
412 | LIST_ENTRY *Link;\r | |
413 | EFI_CORE_DRIVER_ENTRY *DriverEntry;\r | |
414 | BOOLEAN ReadyToRun;\r | |
415 | \r | |
416 | if (gDispatcherRunning) {\r | |
417 | //\r | |
418 | // If the dispatcher is running don't let it be restarted.\r | |
419 | //\r | |
420 | return EFI_ALREADY_STARTED;\r | |
421 | }\r | |
422 | \r | |
423 | gDispatcherRunning = TRUE;\r | |
424 | \r | |
425 | \r | |
426 | ReturnStatus = EFI_NOT_FOUND;\r | |
427 | do {\r | |
428 | //\r | |
429 | // Drain the Scheduled Queue\r | |
430 | //\r | |
431 | while (!IsListEmpty (&mScheduledQueue)) {\r | |
432 | DriverEntry = CR (\r | |
433 | mScheduledQueue.ForwardLink,\r | |
434 | EFI_CORE_DRIVER_ENTRY,\r | |
435 | ScheduledLink,\r | |
436 | EFI_CORE_DRIVER_ENTRY_SIGNATURE\r | |
437 | );\r | |
438 | \r | |
439 | //\r | |
440 | // Load the DXE Driver image into memory. If the Driver was transitioned from\r | |
441 | // Untrused to Scheduled it would have already been loaded so we may need to\r | |
442 | // skip the LoadImage\r | |
443 | //\r | |
444 | if (DriverEntry->ImageHandle == NULL) {\r | |
94903510 | 445 | DEBUG ((DEBUG_INFO, "Loading driver %g\n", &DriverEntry->FileName));\r |
28a00297 | 446 | Status = CoreLoadImage (\r |
022c6d45 | 447 | FALSE,\r |
448 | gDxeCoreImageHandle,\r | |
28a00297 | 449 | DriverEntry->FvFileDevicePath,\r |
022c6d45 | 450 | NULL,\r |
451 | 0,\r | |
28a00297 | 452 | &DriverEntry->ImageHandle\r |
453 | );\r | |
454 | \r | |
455 | //\r | |
456 | // Update the driver state to reflect that it's been loaded\r | |
457 | //\r | |
458 | if (EFI_ERROR (Status)) {\r | |
459 | CoreAcquireDispatcherLock ();\r | |
460 | \r | |
461 | if (Status == EFI_SECURITY_VIOLATION) {\r | |
462 | //\r | |
463 | // Take driver from Scheduled to Untrused state\r | |
464 | //\r | |
465 | DriverEntry->Untrusted = TRUE;\r | |
466 | } else {\r | |
467 | //\r | |
468 | // The DXE Driver could not be loaded, and do not attempt to load or start it again.\r | |
022c6d45 | 469 | // Take driver from Scheduled to Initialized.\r |
28a00297 | 470 | //\r |
471 | // This case include the Never Trusted state if EFI_ACCESS_DENIED is returned\r | |
472 | //\r | |
473 | DriverEntry->Initialized = TRUE;\r | |
474 | }\r | |
475 | \r | |
476 | DriverEntry->Scheduled = FALSE;\r | |
477 | RemoveEntryList (&DriverEntry->ScheduledLink);\r | |
022c6d45 | 478 | \r |
28a00297 | 479 | CoreReleaseDispatcherLock ();\r |
022c6d45 | 480 | \r |
28a00297 | 481 | //\r |
482 | // If it's an error don't try the StartImage\r | |
483 | //\r | |
484 | continue;\r | |
485 | }\r | |
486 | }\r | |
487 | \r | |
488 | CoreAcquireDispatcherLock ();\r | |
489 | \r | |
490 | DriverEntry->Scheduled = FALSE;\r | |
491 | DriverEntry->Initialized = TRUE;\r | |
492 | RemoveEntryList (&DriverEntry->ScheduledLink);\r | |
022c6d45 | 493 | \r |
28a00297 | 494 | CoreReleaseDispatcherLock ();\r |
495 | \r | |
2680a308 | 496 | \r |
497 | REPORT_STATUS_CODE_WITH_EXTENDED_DATA (\r | |
498 | EFI_PROGRESS_CODE,\r | |
022c6d45 | 499 | FixedPcdGet32(PcdStatusCodeValueDxeDriverBegin),\r |
2680a308 | 500 | &DriverEntry->ImageHandle,\r |
501 | sizeof (DriverEntry->ImageHandle)\r | |
797a9d67 | 502 | );\r |
2680a308 | 503 | \r |
28a00297 | 504 | Status = CoreStartImage (DriverEntry->ImageHandle, NULL, NULL);\r |
2680a308 | 505 | \r |
506 | REPORT_STATUS_CODE_WITH_EXTENDED_DATA (\r | |
507 | EFI_PROGRESS_CODE,\r | |
022c6d45 | 508 | FixedPcdGet32(PcdStatusCodeValueDxeDriverEnd),\r |
2680a308 | 509 | &DriverEntry->ImageHandle,\r |
510 | sizeof (DriverEntry->ImageHandle)\r | |
797a9d67 | 511 | );\r |
28a00297 | 512 | \r |
513 | ReturnStatus = EFI_SUCCESS;\r | |
514 | }\r | |
515 | \r | |
516 | //\r | |
517 | // Search DriverList for items to place on Scheduled Queue\r | |
518 | //\r | |
519 | ReadyToRun = FALSE;\r | |
520 | for (Link = mDiscoveredList.ForwardLink; Link != &mDiscoveredList; Link = Link->ForwardLink) {\r | |
521 | DriverEntry = CR (Link, EFI_CORE_DRIVER_ENTRY, Link, EFI_CORE_DRIVER_ENTRY_SIGNATURE);\r | |
522 | \r | |
523 | if (DriverEntry->DepexProtocolError){\r | |
524 | //\r | |
525 | // If Section Extraction Protocol did not let the Depex be read before retry the read\r | |
526 | //\r | |
527 | Status = CoreGetDepexSectionAndPreProccess (DriverEntry);\r | |
022c6d45 | 528 | }\r |
28a00297 | 529 | \r |
530 | if (DriverEntry->Dependent) {\r | |
531 | if (CoreIsSchedulable (DriverEntry)) {\r | |
022c6d45 | 532 | CoreInsertOnScheduledQueueWhileProcessingBeforeAndAfter (DriverEntry);\r |
28a00297 | 533 | ReadyToRun = TRUE;\r |
022c6d45 | 534 | }\r |
28a00297 | 535 | }\r |
536 | }\r | |
537 | } while (ReadyToRun);\r | |
538 | \r | |
539 | gDispatcherRunning = FALSE;\r | |
540 | \r | |
541 | return ReturnStatus;\r | |
542 | }\r | |
543 | \r | |
28a00297 | 544 | \r |
162ed594 | 545 | /**\r |
546 | Insert InsertedDriverEntry onto the mScheduledQueue. To do this you\r | |
28a00297 | 547 | must add any driver with a before dependency on InsertedDriverEntry first.\r |
548 | You do this by recursively calling this routine. After all the Befores are\r | |
162ed594 | 549 | processed you can add InsertedDriverEntry to the mScheduledQueue.\r |
550 | Then you can add any driver with an After dependency on InsertedDriverEntry\r | |
28a00297 | 551 | by recursively calling this routine.\r |
552 | \r | |
162ed594 | 553 | @param InsertedDriverEntry The driver to insert on the ScheduledLink Queue\r |
28a00297 | 554 | \r |
162ed594 | 555 | **/\r |
162ed594 | 556 | VOID\r |
557 | CoreInsertOnScheduledQueueWhileProcessingBeforeAndAfter (\r | |
558 | IN EFI_CORE_DRIVER_ENTRY *InsertedDriverEntry\r | |
559 | )\r | |
28a00297 | 560 | {\r |
561 | LIST_ENTRY *Link;\r | |
562 | EFI_CORE_DRIVER_ENTRY *DriverEntry;\r | |
563 | \r | |
564 | //\r | |
565 | // Process Before Dependency\r | |
566 | //\r | |
567 | for (Link = mDiscoveredList.ForwardLink; Link != &mDiscoveredList; Link = Link->ForwardLink) {\r | |
568 | DriverEntry = CR(Link, EFI_CORE_DRIVER_ENTRY, Link, EFI_CORE_DRIVER_ENTRY_SIGNATURE);\r | |
569 | if (DriverEntry->Before && DriverEntry->Dependent) {\r | |
570 | if (CompareGuid (&InsertedDriverEntry->FileName, &DriverEntry->BeforeAfterGuid)) {\r | |
571 | //\r | |
572 | // Recursively process BEFORE\r | |
573 | //\r | |
574 | CoreInsertOnScheduledQueueWhileProcessingBeforeAndAfter (DriverEntry);\r | |
575 | }\r | |
576 | }\r | |
577 | }\r | |
578 | \r | |
579 | //\r | |
580 | // Convert driver from Dependent to Scheduled state\r | |
581 | //\r | |
582 | CoreAcquireDispatcherLock ();\r | |
583 | \r | |
584 | InsertedDriverEntry->Dependent = FALSE;\r | |
585 | InsertedDriverEntry->Scheduled = TRUE;\r | |
586 | InsertTailList (&mScheduledQueue, &InsertedDriverEntry->ScheduledLink);\r | |
022c6d45 | 587 | \r |
28a00297 | 588 | CoreReleaseDispatcherLock ();\r |
589 | \r | |
590 | //\r | |
591 | // Process After Dependency\r | |
592 | //\r | |
593 | for (Link = mDiscoveredList.ForwardLink; Link != &mDiscoveredList; Link = Link->ForwardLink) {\r | |
594 | DriverEntry = CR(Link, EFI_CORE_DRIVER_ENTRY, Link, EFI_CORE_DRIVER_ENTRY_SIGNATURE);\r | |
595 | if (DriverEntry->After && DriverEntry->Dependent) {\r | |
596 | if (CompareGuid (&InsertedDriverEntry->FileName, &DriverEntry->BeforeAfterGuid)) {\r | |
597 | //\r | |
598 | // Recursively process AFTER\r | |
599 | //\r | |
600 | CoreInsertOnScheduledQueueWhileProcessingBeforeAndAfter (DriverEntry);\r | |
601 | }\r | |
602 | }\r | |
603 | }\r | |
604 | }\r | |
605 | \r | |
28a00297 | 606 | \r |
162ed594 | 607 | /**\r |
28a00297 | 608 | Return TRUE if the Fv has been processed, FALSE if not.\r |
609 | \r | |
022c6d45 | 610 | @param FvHandle The handle of a FV that's being tested\r |
28a00297 | 611 | \r |
022c6d45 | 612 | @retval TRUE Fv protocol on FvHandle has been processed\r |
e94a9ff7 | 613 | @retval FALSE Fv protocol on FvHandle has not yet been processed\r |
28a00297 | 614 | \r |
162ed594 | 615 | **/\r |
162ed594 | 616 | BOOLEAN\r |
617 | FvHasBeenProcessed (\r | |
618 | IN EFI_HANDLE FvHandle\r | |
619 | )\r | |
28a00297 | 620 | {\r |
621 | LIST_ENTRY *Link;\r | |
622 | KNOWN_HANDLE *KnownHandle;\r | |
623 | \r | |
624 | for (Link = mFvHandleList.ForwardLink; Link != &mFvHandleList; Link = Link->ForwardLink) {\r | |
625 | KnownHandle = CR(Link, KNOWN_HANDLE, Link, KNOWN_HANDLE_SIGNATURE);\r | |
626 | if (KnownHandle->Handle == FvHandle) {\r | |
627 | return TRUE;\r | |
628 | }\r | |
629 | }\r | |
630 | return FALSE;\r | |
631 | }\r | |
632 | \r | |
28a00297 | 633 | \r |
162ed594 | 634 | /**\r |
28a00297 | 635 | Remember that Fv protocol on FvHandle has had it's drivers placed on the\r |
636 | mDiscoveredList. This fucntion adds entries on the mFvHandleList. Items are\r | |
637 | never removed/freed from the mFvHandleList.\r | |
638 | \r | |
162ed594 | 639 | @param FvHandle The handle of a FV that has been processed\r |
28a00297 | 640 | \r |
162ed594 | 641 | **/\r |
162ed594 | 642 | VOID\r |
643 | FvIsBeingProcesssed (\r | |
644 | IN EFI_HANDLE FvHandle\r | |
645 | )\r | |
28a00297 | 646 | {\r |
647 | KNOWN_HANDLE *KnownHandle;\r | |
648 | \r | |
9c4ac31c | 649 | KnownHandle = AllocatePool (sizeof (KNOWN_HANDLE));\r |
28a00297 | 650 | ASSERT (KnownHandle != NULL);\r |
651 | \r | |
652 | KnownHandle->Signature = KNOWN_HANDLE_SIGNATURE;\r | |
653 | KnownHandle->Handle = FvHandle;\r | |
654 | InsertTailList (&mFvHandleList, &KnownHandle->Link);\r | |
655 | }\r | |
656 | \r | |
657 | \r | |
658 | \r | |
162ed594 | 659 | \r |
660 | /**\r | |
661 | Convert FvHandle and DriverName into an EFI device path\r | |
662 | \r | |
022c6d45 | 663 | @param Fv Fv protocol, needed to read Depex info out of\r |
664 | FLASH.\r | |
665 | @param FvHandle Handle for Fv, needed in the\r | |
666 | EFI_CORE_DRIVER_ENTRY so that the PE image can be\r | |
667 | read out of the FV at a later time.\r | |
668 | @param DriverName Name of driver to add to mDiscoveredList.\r | |
162ed594 | 669 | \r |
670 | @return Pointer to device path constructed from FvHandle and DriverName\r | |
671 | \r | |
672 | **/\r | |
28a00297 | 673 | EFI_DEVICE_PATH_PROTOCOL *\r |
674 | CoreFvToDevicePath (\r | |
0c2b5da8 | 675 | IN EFI_FIRMWARE_VOLUME2_PROTOCOL *Fv,\r |
28a00297 | 676 | IN EFI_HANDLE FvHandle,\r |
677 | IN EFI_GUID *DriverName\r | |
678 | )\r | |
28a00297 | 679 | {\r |
680 | EFI_STATUS Status;\r | |
681 | EFI_DEVICE_PATH_PROTOCOL *FvDevicePath;\r | |
682 | EFI_DEVICE_PATH_PROTOCOL *FileNameDevicePath;\r | |
683 | \r | |
684 | //\r | |
685 | // Remember the device path of the FV\r | |
686 | //\r | |
687 | Status = CoreHandleProtocol (FvHandle, &gEfiDevicePathProtocolGuid, (VOID **)&FvDevicePath);\r | |
688 | if (EFI_ERROR (Status)) {\r | |
689 | FileNameDevicePath = NULL;\r | |
690 | } else {\r | |
691 | //\r | |
692 | // Build a device path to the file in the FV to pass into gBS->LoadImage\r | |
693 | //\r | |
694 | EfiInitializeFwVolDevicepathNode (&mFvDevicePath.File, DriverName);\r | |
1232b214 | 695 | SetDevicePathEndNode (&mFvDevicePath.End);\r |
28a00297 | 696 | \r |
9c4ac31c | 697 | FileNameDevicePath = AppendDevicePath (\r |
022c6d45 | 698 | FvDevicePath,\r |
28a00297 | 699 | (EFI_DEVICE_PATH_PROTOCOL *)&mFvDevicePath\r |
700 | );\r | |
701 | }\r | |
702 | \r | |
703 | return FileNameDevicePath;\r | |
704 | }\r | |
705 | \r | |
706 | \r | |
707 | \r | |
162ed594 | 708 | /**\r |
709 | Add an entry to the mDiscoveredList. Allocate memory to store the DriverEntry,\r | |
28a00297 | 710 | and initilize any state variables. Read the Depex from the FV and store it\r |
711 | in DriverEntry. Pre-process the Depex to set the SOR, Before and After state.\r | |
712 | The Discovered list is never free'ed and contains booleans that represent the\r | |
713 | other possible DXE driver states.\r | |
714 | \r | |
022c6d45 | 715 | @param Fv Fv protocol, needed to read Depex info out of\r |
716 | FLASH.\r | |
717 | @param FvHandle Handle for Fv, needed in the\r | |
718 | EFI_CORE_DRIVER_ENTRY so that the PE image can be\r | |
719 | read out of the FV at a later time.\r | |
720 | @param DriverName Name of driver to add to mDiscoveredList.\r | |
28a00297 | 721 | \r |
022c6d45 | 722 | @retval EFI_SUCCESS If driver was added to the mDiscoveredList.\r |
723 | @retval EFI_ALREADY_STARTED The driver has already been started. Only one\r | |
724 | DriverName may be active in the system at any one\r | |
162ed594 | 725 | time.\r |
28a00297 | 726 | \r |
162ed594 | 727 | **/\r |
728 | EFI_STATUS\r | |
729 | CoreAddToDriverList (\r | |
730 | IN EFI_FIRMWARE_VOLUME2_PROTOCOL *Fv,\r | |
731 | IN EFI_HANDLE FvHandle,\r | |
732 | IN EFI_GUID *DriverName\r | |
733 | )\r | |
28a00297 | 734 | {\r |
735 | EFI_CORE_DRIVER_ENTRY *DriverEntry;\r | |
736 | \r | |
022c6d45 | 737 | \r |
28a00297 | 738 | //\r |
022c6d45 | 739 | // Create the Driver Entry for the list. ZeroPool initializes lots of variables to\r |
28a00297 | 740 | // NULL or FALSE.\r |
741 | //\r | |
9c4ac31c | 742 | DriverEntry = AllocateZeroPool (sizeof (EFI_CORE_DRIVER_ENTRY));\r |
28a00297 | 743 | ASSERT (DriverEntry != NULL);\r |
744 | \r | |
745 | DriverEntry->Signature = EFI_CORE_DRIVER_ENTRY_SIGNATURE;\r | |
e94a9ff7 | 746 | CopyGuid (&DriverEntry->FileName, DriverName);\r |
28a00297 | 747 | DriverEntry->FvHandle = FvHandle;\r |
748 | DriverEntry->Fv = Fv;\r | |
749 | DriverEntry->FvFileDevicePath = CoreFvToDevicePath (Fv, FvHandle, DriverName);\r | |
750 | \r | |
751 | CoreGetDepexSectionAndPreProccess (DriverEntry);\r | |
022c6d45 | 752 | \r |
28a00297 | 753 | CoreAcquireDispatcherLock ();\r |
022c6d45 | 754 | \r |
28a00297 | 755 | InsertTailList (&mDiscoveredList, &DriverEntry->Link);\r |
756 | \r | |
757 | CoreReleaseDispatcherLock ();\r | |
758 | \r | |
759 | return EFI_SUCCESS;\r | |
760 | }\r | |
761 | \r | |
bbc0f1bb | 762 | \r |
162ed594 | 763 | /**\r |
bbc0f1bb | 764 | Check if a FV Image type file (EFI_FV_FILETYPE_FIRMWARE_VOLUME_IMAGE) is\r |
765 | described by a EFI_HOB_FIRMWARE_VOLUME2 Hob.\r | |
766 | \r | |
022c6d45 | 767 | @param FvHandle The handle which FVB protocol installed on.\r |
768 | @param DriverName The driver guid specified.\r | |
bbc0f1bb | 769 | \r |
022c6d45 | 770 | @retval TRUE This file is found in a EFI_HOB_FIRMWARE_VOLUME2\r |
771 | Hob.\r | |
162ed594 | 772 | @retval FALSE Not found.\r |
bbc0f1bb | 773 | \r |
162ed594 | 774 | **/\r |
162ed594 | 775 | BOOLEAN\r |
776 | FvFoundInHobFv2 (\r | |
777 | IN EFI_HANDLE FvHandle,\r | |
778 | IN CONST EFI_GUID *DriverName\r | |
779 | )\r | |
bbc0f1bb | 780 | {\r |
781 | EFI_PEI_HOB_POINTERS HobFv2;\r | |
022c6d45 | 782 | \r |
bbc0f1bb | 783 | HobFv2.Raw = GetHobList ();\r |
022c6d45 | 784 | \r |
bbc0f1bb | 785 | while ((HobFv2.Raw = GetNextHob (EFI_HOB_TYPE_FV2, HobFv2.Raw)) != NULL) {\r |
786 | if (CompareGuid (DriverName, &HobFv2.FirmwareVolume2->FileName)) {\r | |
b0d803fe | 787 | return TRUE;\r |
bbc0f1bb | 788 | }\r |
789 | HobFv2.Raw = GET_NEXT_HOB (HobFv2);\r | |
790 | }\r | |
791 | \r | |
792 | return FALSE;\r | |
793 | }\r | |
28a00297 | 794 | \r |
795 | \r | |
162ed594 | 796 | \r |
797 | /**\r | |
798 | Get the driver from the FV through driver name, and produce a FVB protocol on FvHandle.\r | |
799 | \r | |
022c6d45 | 800 | @param Fv The FIRMWARE_VOLUME protocol installed on the FV.\r |
801 | @param FvHandle The handle which FVB protocol installed on.\r | |
802 | @param DriverName The driver guid specified.\r | |
162ed594 | 803 | \r |
022c6d45 | 804 | @retval EFI_OUT_OF_RESOURCES No enough memory or other resource.\r |
805 | @retval EFI_VOLUME_CORRUPTED Corrupted volume.\r | |
162ed594 | 806 | @retval EFI_SUCCESS Function successfully returned.\r |
807 | \r | |
808 | **/\r | |
022c6d45 | 809 | EFI_STATUS\r |
28a00297 | 810 | CoreProcessFvImageFile (\r |
0c2b5da8 | 811 | IN EFI_FIRMWARE_VOLUME2_PROTOCOL *Fv,\r |
28a00297 | 812 | IN EFI_HANDLE FvHandle,\r |
813 | IN EFI_GUID *DriverName\r | |
814 | )\r | |
28a00297 | 815 | {\r |
816 | EFI_STATUS Status;\r | |
817 | EFI_SECTION_TYPE SectionType;\r | |
818 | UINT32 AuthenticationStatus;\r | |
819 | VOID *Buffer;\r | |
38837959 | 820 | VOID *AlignedBuffer;\r |
28a00297 | 821 | UINTN BufferSize;\r |
38837959 | 822 | EFI_FIRMWARE_VOLUME_HEADER *FvHeader;\r |
022c6d45 | 823 | UINT32 FvAlignment;\r |
28a00297 | 824 | \r |
825 | //\r | |
826 | // Read the first (and only the first) firmware volume section\r | |
827 | //\r | |
e94a9ff7 | 828 | SectionType = EFI_SECTION_FIRMWARE_VOLUME_IMAGE;\r |
829 | FvHeader = NULL;\r | |
830 | FvAlignment = 0;\r | |
831 | Buffer = NULL;\r | |
832 | BufferSize = 0;\r | |
38837959 | 833 | AlignedBuffer = NULL;\r |
28a00297 | 834 | Status = Fv->ReadSection (\r |
022c6d45 | 835 | Fv,\r |
836 | DriverName,\r | |
837 | SectionType,\r | |
838 | 0,\r | |
839 | &Buffer,\r | |
e94a9ff7 | 840 | &BufferSize,\r |
841 | &AuthenticationStatus\r | |
842 | );\r | |
28a00297 | 843 | if (!EFI_ERROR (Status)) {\r |
844 | //\r | |
38837959 | 845 | // FvImage should be at its required alignment.\r |
28a00297 | 846 | //\r |
38837959 LG |
847 | FvHeader = (EFI_FIRMWARE_VOLUME_HEADER *) Buffer;\r |
848 | FvAlignment = 1 << ((FvHeader->Attributes & EFI_FVB2_ALIGNMENT) >> 16);\r | |
849 | //\r | |
850 | // FvAlignment must be more than 8 bytes required by FvHeader structure.\r | |
022c6d45 | 851 | //\r |
38837959 LG |
852 | if (FvAlignment < 8) {\r |
853 | FvAlignment = 8;\r | |
854 | }\r | |
e94a9ff7 | 855 | //\r |
856 | // Allocate the aligned buffer for the FvImage.\r | |
857 | //\r | |
b2c5e194 | 858 | AlignedBuffer = AllocateAlignedPages (EFI_SIZE_TO_PAGES (BufferSize), (UINTN) FvAlignment);\r |
38837959 LG |
859 | if (AlignedBuffer == NULL) {\r |
860 | Status = EFI_OUT_OF_RESOURCES;\r | |
861 | } else {\r | |
862 | //\r | |
863 | // Move FvImage into the aligned buffer and release the original buffer.\r | |
864 | //\r | |
865 | CopyMem (AlignedBuffer, Buffer, BufferSize);\r | |
866 | CoreFreePool (Buffer);\r | |
867 | Buffer = NULL;\r | |
868 | //\r | |
869 | // Produce a FVB protocol for the file\r | |
870 | //\r | |
871 | Status = ProduceFVBProtocolOnBuffer (\r | |
872 | (EFI_PHYSICAL_ADDRESS) (UINTN) AlignedBuffer,\r | |
873 | (UINT64)BufferSize,\r | |
874 | FvHandle,\r | |
875 | NULL\r | |
876 | );\r | |
877 | }\r | |
28a00297 | 878 | }\r |
879 | \r | |
022c6d45 | 880 | if (EFI_ERROR (Status)) {\r |
38837959 LG |
881 | //\r |
882 | // ReadSection or Produce FVB failed, Free data buffer\r | |
883 | //\r | |
884 | if (Buffer != NULL) {\r | |
9c4ac31c | 885 | FreePool (Buffer);\r |
38837959 | 886 | }\r |
022c6d45 | 887 | \r |
38837959 | 888 | if (AlignedBuffer != NULL) {\r |
b2c5e194 | 889 | FreeAlignedPages (AlignedBuffer, EFI_SIZE_TO_PAGES (BufferSize));\r |
38837959 | 890 | }\r |
28a00297 | 891 | }\r |
892 | \r | |
893 | return Status;\r | |
894 | }\r | |
895 | \r | |
28a00297 | 896 | \r |
162ed594 | 897 | /**\r |
898 | Event notification that is fired every time a FV dispatch protocol is added.\r | |
28a00297 | 899 | More than one protocol may have been added when this event is fired, so you\r |
900 | must loop on CoreLocateHandle () to see how many protocols were added and\r | |
901 | do the following to each FV:\r | |
162ed594 | 902 | If the Fv has already been processed, skip it. If the Fv has not been\r |
28a00297 | 903 | processed then mark it as being processed, as we are about to process it.\r |
162ed594 | 904 | Read the Fv and add any driver in the Fv to the mDiscoveredList.The\r |
28a00297 | 905 | mDiscoveredList is never free'ed and contains variables that define\r |
162ed594 | 906 | the other states the DXE driver transitions to..\r |
28a00297 | 907 | While you are at it read the A Priori file into memory.\r |
908 | Place drivers in the A Priori list onto the mScheduledQueue.\r | |
909 | \r | |
022c6d45 | 910 | @param Event The Event that is being processed, not used.\r |
162ed594 | 911 | @param Context Event Context, not used.\r |
28a00297 | 912 | \r |
162ed594 | 913 | **/\r |
162ed594 | 914 | VOID\r |
915 | EFIAPI\r | |
916 | CoreFwVolEventProtocolNotify (\r | |
917 | IN EFI_EVENT Event,\r | |
918 | IN VOID *Context\r | |
919 | )\r | |
28a00297 | 920 | {\r |
921 | EFI_STATUS Status;\r | |
922 | EFI_STATUS GetNextFileStatus;\r | |
923 | EFI_STATUS SecurityStatus;\r | |
0c2b5da8 | 924 | EFI_FIRMWARE_VOLUME2_PROTOCOL *Fv;\r |
28a00297 | 925 | EFI_DEVICE_PATH_PROTOCOL *FvDevicePath;\r |
926 | EFI_HANDLE FvHandle;\r | |
927 | UINTN BufferSize;\r | |
928 | EFI_GUID NameGuid;\r | |
929 | UINTN Key;\r | |
930 | EFI_FV_FILETYPE Type;\r | |
931 | EFI_FV_FILE_ATTRIBUTES Attributes;\r | |
932 | UINTN Size;\r | |
933 | EFI_CORE_DRIVER_ENTRY *DriverEntry;\r | |
934 | EFI_GUID *AprioriFile;\r | |
935 | UINTN AprioriEntryCount;\r | |
936 | UINTN Index;\r | |
937 | LIST_ENTRY *Link;\r | |
938 | UINT32 AuthenticationStatus;\r | |
939 | UINTN SizeOfBuffer;\r | |
940 | \r | |
941 | \r | |
942 | while (TRUE) {\r | |
943 | BufferSize = sizeof (EFI_HANDLE);\r | |
944 | Status = CoreLocateHandle (\r | |
e94a9ff7 | 945 | ByRegisterNotify,\r |
946 | NULL,\r | |
947 | mFwVolEventRegistration,\r | |
948 | &BufferSize,\r | |
949 | &FvHandle\r | |
950 | );\r | |
28a00297 | 951 | if (EFI_ERROR (Status)) {\r |
952 | //\r | |
953 | // If no more notification events exit\r | |
954 | //\r | |
955 | return;\r | |
956 | }\r | |
957 | \r | |
958 | if (FvHasBeenProcessed (FvHandle)) {\r | |
959 | //\r | |
960 | // This Fv has already been processed so lets skip it!\r | |
961 | //\r | |
962 | continue;\r | |
963 | }\r | |
964 | \r | |
28a00297 | 965 | //\r |
966 | // Since we are about to process this Fv mark it as processed.\r | |
967 | //\r | |
968 | FvIsBeingProcesssed (FvHandle);\r | |
969 | \r | |
0c2b5da8 | 970 | Status = CoreHandleProtocol (FvHandle, &gEfiFirmwareVolume2ProtocolGuid, (VOID **)&Fv);\r |
28a00297 | 971 | if (EFI_ERROR (Status)) {\r |
972 | //\r | |
973 | // The Handle has a FirmwareVolumeDispatch protocol and should also contiain\r | |
974 | // a FirmwareVolume protocol thus we should never get here.\r | |
975 | //\r | |
976 | ASSERT (FALSE);\r | |
977 | continue;\r | |
978 | }\r | |
022c6d45 | 979 | \r |
28a00297 | 980 | Status = CoreHandleProtocol (FvHandle, &gEfiDevicePathProtocolGuid, (VOID **)&FvDevicePath);\r |
981 | if (EFI_ERROR (Status)) {\r | |
982 | //\r | |
983 | // The Firmware volume doesn't have device path, can't be dispatched.\r | |
984 | //\r | |
985 | continue;\r | |
986 | }\r | |
022c6d45 | 987 | \r |
28a00297 | 988 | //\r |
022c6d45 | 989 | // Evaluate the authentication status of the Firmware Volume through\r |
28a00297 | 990 | // Security Architectural Protocol\r |
991 | //\r | |
992 | if (gSecurity != NULL) {\r | |
993 | SecurityStatus = gSecurity->FileAuthenticationState (\r | |
022c6d45 | 994 | gSecurity,\r |
995 | 0,\r | |
28a00297 | 996 | FvDevicePath\r |
997 | );\r | |
998 | if (SecurityStatus != EFI_SUCCESS) {\r | |
999 | //\r | |
1000 | // Security check failed. The firmware volume should not be used for any purpose.\r | |
1001 | //\r | |
1002 | continue;\r | |
1003 | }\r | |
022c6d45 | 1004 | }\r |
1005 | \r | |
28a00297 | 1006 | //\r |
022c6d45 | 1007 | // Discover Drivers in FV and add them to the Discovered Driver List.\r |
1008 | // Process EFI_FV_FILETYPE_DRIVER type and then EFI_FV_FILETYPE_COMBINED_PEIM_DRIVER\r | |
28a00297 | 1009 | // EFI_FV_FILETYPE_DXE_CORE is processed to produce a Loaded Image protocol for the core\r |
1010 | // EFI_FV_FILETYPE_FIRMWARE_VOLUME_IMAGE is processed to create a Fvb\r | |
1011 | //\r | |
e94a9ff7 | 1012 | for (Index = 0; Index < sizeof (mDxeFileTypes) / sizeof (EFI_FV_FILETYPE); Index++) {\r |
28a00297 | 1013 | //\r |
1014 | // Initialize the search key\r | |
1015 | //\r | |
1016 | Key = 0;\r | |
1017 | do {\r | |
1018 | Type = mDxeFileTypes[Index];\r | |
1019 | GetNextFileStatus = Fv->GetNextFile (\r | |
022c6d45 | 1020 | Fv,\r |
28a00297 | 1021 | &Key,\r |
022c6d45 | 1022 | &Type,\r |
1023 | &NameGuid,\r | |
1024 | &Attributes,\r | |
28a00297 | 1025 | &Size\r |
1026 | );\r | |
1027 | if (!EFI_ERROR (GetNextFileStatus)) {\r | |
1028 | if (Type == EFI_FV_FILETYPE_DXE_CORE) {\r | |
1029 | //\r | |
1030 | // If this is the DXE core fill in it's DevicePath & DeviceHandle\r | |
1031 | //\r | |
1032 | if (gDxeCoreLoadedImage->FilePath == NULL) {\r | |
1033 | if (CompareGuid (&NameGuid, gDxeCoreFileName)) {\r | |
1034 | //\r | |
1035 | // Maybe One specail Fv cantains only one DXE_CORE module, so its device path must\r | |
1036 | // be initialized completely.\r | |
1037 | //\r | |
1038 | EfiInitializeFwVolDevicepathNode (&mFvDevicePath.File, &NameGuid);\r | |
1232b214 | 1039 | SetDevicePathEndNode (&mFvDevicePath.End);\r |
28a00297 | 1040 | \r |
9c4ac31c | 1041 | gDxeCoreLoadedImage->FilePath = DuplicateDevicePath (\r |
28a00297 | 1042 | (EFI_DEVICE_PATH_PROTOCOL *)&mFvDevicePath\r |
1043 | );\r | |
1044 | gDxeCoreLoadedImage->DeviceHandle = FvHandle;\r | |
1045 | }\r | |
1046 | }\r | |
1047 | } else if (Type == EFI_FV_FILETYPE_FIRMWARE_VOLUME_IMAGE) {\r | |
bbc0f1bb | 1048 | //\r |
022c6d45 | 1049 | // Check if this EFI_FV_FILETYPE_FIRMWARE_VOLUME_IMAGE file has already\r |
bbc0f1bb | 1050 | // been extracted.\r |
1051 | //\r | |
1052 | if (FvFoundInHobFv2 (FvHandle, &NameGuid)) {\r | |
1053 | continue;\r | |
1054 | }\r | |
28a00297 | 1055 | //\r |
1056 | // Found a firmware volume image. Produce a firmware volume block\r | |
022c6d45 | 1057 | // protocol for it so it gets dispatched from. This is usually a\r |
28a00297 | 1058 | // capsule.\r |
1059 | //\r | |
1060 | CoreProcessFvImageFile (Fv, FvHandle, &NameGuid);\r | |
1061 | } else {\r | |
1062 | //\r | |
1063 | // Transition driver from Undiscovered to Discovered state\r | |
1064 | //\r | |
1065 | CoreAddToDriverList (Fv, FvHandle, &NameGuid);\r | |
1066 | }\r | |
1067 | }\r | |
1068 | } while (!EFI_ERROR (GetNextFileStatus));\r | |
1069 | }\r | |
022c6d45 | 1070 | \r |
28a00297 | 1071 | //\r |
1072 | // Read the array of GUIDs from the Apriori file if it is present in the firmware volume\r | |
1073 | //\r | |
1074 | AprioriFile = NULL;\r | |
1075 | Status = Fv->ReadSection (\r | |
1076 | Fv,\r | |
1077 | &gAprioriGuid,\r | |
1078 | EFI_SECTION_RAW,\r | |
1079 | 0,\r | |
1080 | (VOID **)&AprioriFile,\r | |
1081 | &SizeOfBuffer,\r | |
1082 | &AuthenticationStatus\r | |
1083 | );\r | |
1084 | if (!EFI_ERROR (Status)) {\r | |
1085 | AprioriEntryCount = SizeOfBuffer / sizeof (EFI_GUID);\r | |
1086 | } else {\r | |
1087 | AprioriEntryCount = 0;\r | |
1088 | }\r | |
1089 | \r | |
1090 | //\r | |
1091 | // Put drivers on Apriori List on the Scheduled queue. The Discovered List includes\r | |
1092 | // drivers not in the current FV and these must be skipped since the a priori list\r | |
1093 | // is only valid for the FV that it resided in.\r | |
1094 | //\r | |
1095 | CoreAcquireDispatcherLock ();\r | |
022c6d45 | 1096 | \r |
28a00297 | 1097 | for (Index = 0; Index < AprioriEntryCount; Index++) {\r |
1098 | for (Link = mDiscoveredList.ForwardLink; Link != &mDiscoveredList; Link = Link->ForwardLink) {\r | |
1099 | DriverEntry = CR(Link, EFI_CORE_DRIVER_ENTRY, Link, EFI_CORE_DRIVER_ENTRY_SIGNATURE);\r | |
1100 | if (CompareGuid (&DriverEntry->FileName, &AprioriFile[Index]) &&\r | |
1101 | (FvHandle == DriverEntry->FvHandle)) {\r | |
1102 | DriverEntry->Dependent = FALSE;\r | |
1103 | DriverEntry->Scheduled = TRUE;\r | |
1104 | InsertTailList (&mScheduledQueue, &DriverEntry->ScheduledLink);\r | |
1105 | break;\r | |
1106 | }\r | |
1107 | }\r | |
1108 | }\r | |
1109 | \r | |
1110 | CoreReleaseDispatcherLock ();\r | |
1111 | \r | |
1112 | //\r | |
022c6d45 | 1113 | // Free data allocated by Fv->ReadSection ()\r |
28a00297 | 1114 | //\r |
022c6d45 | 1115 | CoreFreePool (AprioriFile);\r |
28a00297 | 1116 | }\r |
1117 | }\r | |
1118 | \r | |
1119 | \r | |
28a00297 | 1120 | \r |
162ed594 | 1121 | /**\r |
28a00297 | 1122 | Initialize the dispatcher. Initialize the notification function that runs when\r |
e94a9ff7 | 1123 | an FV2 protocol is added to the system.\r |
28a00297 | 1124 | \r |
162ed594 | 1125 | **/\r |
1126 | VOID\r | |
1127 | CoreInitializeDispatcher (\r | |
1128 | VOID\r | |
1129 | )\r | |
28a00297 | 1130 | {\r |
7899b797 | 1131 | mFwVolEvent = EfiCreateProtocolNotifyEvent (\r |
022c6d45 | 1132 | &gEfiFirmwareVolume2ProtocolGuid,\r |
28a00297 | 1133 | TPL_CALLBACK,\r |
1134 | CoreFwVolEventProtocolNotify,\r | |
1135 | NULL,\r | |
7899b797 | 1136 | &mFwVolEventRegistration\r |
28a00297 | 1137 | );\r |
1138 | }\r | |
1139 | \r | |
1140 | //\r | |
1141 | // Function only used in debug builds\r | |
1142 | //\r | |
162ed594 | 1143 | \r |
1144 | /**\r | |
1145 | Traverse the discovered list for any drivers that were discovered but not loaded\r | |
1146 | because the dependency experessions evaluated to false.\r | |
1147 | \r | |
1148 | **/\r | |
28a00297 | 1149 | VOID\r |
1150 | CoreDisplayDiscoveredNotDispatched (\r | |
1151 | VOID\r | |
1152 | )\r | |
28a00297 | 1153 | {\r |
1154 | LIST_ENTRY *Link;\r | |
1155 | EFI_CORE_DRIVER_ENTRY *DriverEntry;\r | |
1156 | \r | |
1157 | for (Link = mDiscoveredList.ForwardLink;Link !=&mDiscoveredList; Link = Link->ForwardLink) {\r | |
1158 | DriverEntry = CR(Link, EFI_CORE_DRIVER_ENTRY, Link, EFI_CORE_DRIVER_ENTRY_SIGNATURE);\r | |
1159 | if (DriverEntry->Dependent) {\r | |
162ed594 | 1160 | DEBUG ((DEBUG_LOAD, "Driver %g was discovered but not loaded!!\n", &DriverEntry->FileName));\r |
28a00297 | 1161 | }\r |
1162 | }\r | |
1163 | }\r |