]> git.proxmox.com Git - mirror_edk2.git/blame - MdeModulePkg/Core/Dxe/Dispatcher/Dispatcher.c
Resolved several warnings generated by GCC.
[mirror_edk2.git] / MdeModulePkg / Core / Dxe / Dispatcher / Dispatcher.c
CommitLineData
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 29Copyright (c) 2006 - 2008, Intel Corporation. <BR>\r
30All rights reserved. This program and the accompanying materials\r
31are licensed and made available under the terms and conditions of the BSD License\r
32which accompanies this distribution. The full text of the license may be found at\r
33http://opensource.org/licenses/bsd-license.php\r
34\r
35THE PROGRAM IS DISTRIBUTED UNDER THE BSD LICENSE ON AN "AS IS" BASIS,\r
36WITHOUT 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 46LIST_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
52LIST_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
57LIST_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
62EFI_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
68BOOLEAN gDispatcherRunning = FALSE;\r
69\r
70//\r
71// Module globals to manage the FwVol registration notification event\r
72//\r
73EFI_EVENT mFwVolEvent;\r
74VOID *mFwVolEventRegistration;\r
75\r
76//\r
77// List of file types supported by dispatcher\r
78//\r
022c6d45 79EFI_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
86typedef 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
91FV_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 108VOID\r
109CoreInsertOnScheduledQueueWhileProcessingBeforeAndAfter (\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 130VOID\r
131EFIAPI\r
132CoreFwVolEventProtocolNotify (\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 150EFI_DEVICE_PATH_PROTOCOL *\r
151CoreFvToDevicePath (\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 177EFI_STATUS\r
178CoreAddToDriverList (\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 196EFI_STATUS\r
28a00297 197CoreProcessFvImageFile (\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 208VOID\r
209CoreAcquireDispatcherLock (\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 221VOID\r
222CoreReleaseDispatcherLock (\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 242EFI_STATUS\r
243CoreGetDepexSectionAndPreProccess (\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 309EFI_STATUS\r
310EFIAPI\r
311CoreSchedule (\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 355EFI_STATUS\r
356EFIAPI\r
357CoreTrust (\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 404EFI_STATUS\r
405EFIAPI\r
406CoreDispatcher (\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
445 Status = CoreLoadImage (\r
022c6d45 446 FALSE,\r
447 gDxeCoreImageHandle,\r
28a00297 448 DriverEntry->FvFileDevicePath,\r
022c6d45 449 NULL,\r
450 0,\r
28a00297 451 &DriverEntry->ImageHandle\r
452 );\r
453\r
454 //\r
455 // Update the driver state to reflect that it's been loaded\r
456 //\r
457 if (EFI_ERROR (Status)) {\r
458 CoreAcquireDispatcherLock ();\r
459\r
460 if (Status == EFI_SECURITY_VIOLATION) {\r
461 //\r
462 // Take driver from Scheduled to Untrused state\r
463 //\r
464 DriverEntry->Untrusted = TRUE;\r
465 } else {\r
466 //\r
467 // The DXE Driver could not be loaded, and do not attempt to load or start it again.\r
022c6d45 468 // Take driver from Scheduled to Initialized.\r
28a00297 469 //\r
470 // This case include the Never Trusted state if EFI_ACCESS_DENIED is returned\r
471 //\r
472 DriverEntry->Initialized = TRUE;\r
473 }\r
474\r
475 DriverEntry->Scheduled = FALSE;\r
476 RemoveEntryList (&DriverEntry->ScheduledLink);\r
022c6d45 477\r
28a00297 478 CoreReleaseDispatcherLock ();\r
022c6d45 479\r
28a00297 480 //\r
481 // If it's an error don't try the StartImage\r
482 //\r
483 continue;\r
484 }\r
485 }\r
486\r
487 CoreAcquireDispatcherLock ();\r
488\r
489 DriverEntry->Scheduled = FALSE;\r
490 DriverEntry->Initialized = TRUE;\r
491 RemoveEntryList (&DriverEntry->ScheduledLink);\r
022c6d45 492\r
28a00297 493 CoreReleaseDispatcherLock ();\r
494\r
2680a308 495 \r
496 REPORT_STATUS_CODE_WITH_EXTENDED_DATA (\r
497 EFI_PROGRESS_CODE,\r
022c6d45 498 FixedPcdGet32(PcdStatusCodeValueDxeDriverBegin),\r
2680a308 499 &DriverEntry->ImageHandle,\r
500 sizeof (DriverEntry->ImageHandle)\r
797a9d67 501 );\r
2680a308 502\r
28a00297 503 Status = CoreStartImage (DriverEntry->ImageHandle, NULL, NULL);\r
2680a308 504\r
505 REPORT_STATUS_CODE_WITH_EXTENDED_DATA (\r
506 EFI_PROGRESS_CODE,\r
022c6d45 507 FixedPcdGet32(PcdStatusCodeValueDxeDriverEnd),\r
2680a308 508 &DriverEntry->ImageHandle,\r
509 sizeof (DriverEntry->ImageHandle)\r
797a9d67 510 );\r
28a00297 511\r
512 ReturnStatus = EFI_SUCCESS;\r
513 }\r
514\r
515 //\r
516 // Search DriverList for items to place on Scheduled Queue\r
517 //\r
518 ReadyToRun = FALSE;\r
519 for (Link = mDiscoveredList.ForwardLink; Link != &mDiscoveredList; Link = Link->ForwardLink) {\r
520 DriverEntry = CR (Link, EFI_CORE_DRIVER_ENTRY, Link, EFI_CORE_DRIVER_ENTRY_SIGNATURE);\r
521\r
522 if (DriverEntry->DepexProtocolError){\r
523 //\r
524 // If Section Extraction Protocol did not let the Depex be read before retry the read\r
525 //\r
526 Status = CoreGetDepexSectionAndPreProccess (DriverEntry);\r
022c6d45 527 }\r
28a00297 528\r
529 if (DriverEntry->Dependent) {\r
530 if (CoreIsSchedulable (DriverEntry)) {\r
022c6d45 531 CoreInsertOnScheduledQueueWhileProcessingBeforeAndAfter (DriverEntry);\r
28a00297 532 ReadyToRun = TRUE;\r
022c6d45 533 }\r
28a00297 534 }\r
535 }\r
536 } while (ReadyToRun);\r
537\r
538 gDispatcherRunning = FALSE;\r
539\r
540 return ReturnStatus;\r
541}\r
542\r
28a00297 543\r
162ed594 544/**\r
545 Insert InsertedDriverEntry onto the mScheduledQueue. To do this you\r
28a00297 546 must add any driver with a before dependency on InsertedDriverEntry first.\r
547 You do this by recursively calling this routine. After all the Befores are\r
162ed594 548 processed you can add InsertedDriverEntry to the mScheduledQueue.\r
549 Then you can add any driver with an After dependency on InsertedDriverEntry\r
28a00297 550 by recursively calling this routine.\r
551\r
162ed594 552 @param InsertedDriverEntry The driver to insert on the ScheduledLink Queue\r
28a00297 553\r
162ed594 554**/\r
162ed594 555VOID\r
556CoreInsertOnScheduledQueueWhileProcessingBeforeAndAfter (\r
557 IN EFI_CORE_DRIVER_ENTRY *InsertedDriverEntry\r
558 )\r
28a00297 559{\r
560 LIST_ENTRY *Link;\r
561 EFI_CORE_DRIVER_ENTRY *DriverEntry;\r
562\r
563 //\r
564 // Process Before Dependency\r
565 //\r
566 for (Link = mDiscoveredList.ForwardLink; Link != &mDiscoveredList; Link = Link->ForwardLink) {\r
567 DriverEntry = CR(Link, EFI_CORE_DRIVER_ENTRY, Link, EFI_CORE_DRIVER_ENTRY_SIGNATURE);\r
568 if (DriverEntry->Before && DriverEntry->Dependent) {\r
569 if (CompareGuid (&InsertedDriverEntry->FileName, &DriverEntry->BeforeAfterGuid)) {\r
570 //\r
571 // Recursively process BEFORE\r
572 //\r
573 CoreInsertOnScheduledQueueWhileProcessingBeforeAndAfter (DriverEntry);\r
574 }\r
575 }\r
576 }\r
577\r
578 //\r
579 // Convert driver from Dependent to Scheduled state\r
580 //\r
581 CoreAcquireDispatcherLock ();\r
582\r
583 InsertedDriverEntry->Dependent = FALSE;\r
584 InsertedDriverEntry->Scheduled = TRUE;\r
585 InsertTailList (&mScheduledQueue, &InsertedDriverEntry->ScheduledLink);\r
022c6d45 586\r
28a00297 587 CoreReleaseDispatcherLock ();\r
588\r
589 //\r
590 // Process After Dependency\r
591 //\r
592 for (Link = mDiscoveredList.ForwardLink; Link != &mDiscoveredList; Link = Link->ForwardLink) {\r
593 DriverEntry = CR(Link, EFI_CORE_DRIVER_ENTRY, Link, EFI_CORE_DRIVER_ENTRY_SIGNATURE);\r
594 if (DriverEntry->After && DriverEntry->Dependent) {\r
595 if (CompareGuid (&InsertedDriverEntry->FileName, &DriverEntry->BeforeAfterGuid)) {\r
596 //\r
597 // Recursively process AFTER\r
598 //\r
599 CoreInsertOnScheduledQueueWhileProcessingBeforeAndAfter (DriverEntry);\r
600 }\r
601 }\r
602 }\r
603}\r
604\r
28a00297 605\r
162ed594 606/**\r
28a00297 607 Return TRUE if the Fv has been processed, FALSE if not.\r
608\r
022c6d45 609 @param FvHandle The handle of a FV that's being tested\r
28a00297 610\r
022c6d45 611 @retval TRUE Fv protocol on FvHandle has been processed\r
e94a9ff7 612 @retval FALSE Fv protocol on FvHandle has not yet been processed\r
28a00297 613\r
162ed594 614**/\r
162ed594 615BOOLEAN\r
616FvHasBeenProcessed (\r
617 IN EFI_HANDLE FvHandle\r
618 )\r
28a00297 619{\r
620 LIST_ENTRY *Link;\r
621 KNOWN_HANDLE *KnownHandle;\r
622\r
623 for (Link = mFvHandleList.ForwardLink; Link != &mFvHandleList; Link = Link->ForwardLink) {\r
624 KnownHandle = CR(Link, KNOWN_HANDLE, Link, KNOWN_HANDLE_SIGNATURE);\r
625 if (KnownHandle->Handle == FvHandle) {\r
626 return TRUE;\r
627 }\r
628 }\r
629 return FALSE;\r
630}\r
631\r
28a00297 632\r
162ed594 633/**\r
28a00297 634 Remember that Fv protocol on FvHandle has had it's drivers placed on the\r
635 mDiscoveredList. This fucntion adds entries on the mFvHandleList. Items are\r
636 never removed/freed from the mFvHandleList.\r
637\r
162ed594 638 @param FvHandle The handle of a FV that has been processed\r
28a00297 639\r
162ed594 640**/\r
162ed594 641VOID\r
642FvIsBeingProcesssed (\r
643 IN EFI_HANDLE FvHandle\r
644 )\r
28a00297 645{\r
646 KNOWN_HANDLE *KnownHandle;\r
647\r
9c4ac31c 648 KnownHandle = AllocatePool (sizeof (KNOWN_HANDLE));\r
28a00297 649 ASSERT (KnownHandle != NULL);\r
650\r
651 KnownHandle->Signature = KNOWN_HANDLE_SIGNATURE;\r
652 KnownHandle->Handle = FvHandle;\r
653 InsertTailList (&mFvHandleList, &KnownHandle->Link);\r
654}\r
655\r
656\r
657\r
162ed594 658\r
659/**\r
660 Convert FvHandle and DriverName into an EFI device path\r
661\r
022c6d45 662 @param Fv Fv protocol, needed to read Depex info out of\r
663 FLASH.\r
664 @param FvHandle Handle for Fv, needed in the\r
665 EFI_CORE_DRIVER_ENTRY so that the PE image can be\r
666 read out of the FV at a later time.\r
667 @param DriverName Name of driver to add to mDiscoveredList.\r
162ed594 668\r
669 @return Pointer to device path constructed from FvHandle and DriverName\r
670\r
671**/\r
28a00297 672EFI_DEVICE_PATH_PROTOCOL *\r
673CoreFvToDevicePath (\r
0c2b5da8 674 IN EFI_FIRMWARE_VOLUME2_PROTOCOL *Fv,\r
28a00297 675 IN EFI_HANDLE FvHandle,\r
676 IN EFI_GUID *DriverName\r
677 )\r
28a00297 678{\r
679 EFI_STATUS Status;\r
680 EFI_DEVICE_PATH_PROTOCOL *FvDevicePath;\r
681 EFI_DEVICE_PATH_PROTOCOL *FileNameDevicePath;\r
682\r
683 //\r
684 // Remember the device path of the FV\r
685 //\r
686 Status = CoreHandleProtocol (FvHandle, &gEfiDevicePathProtocolGuid, (VOID **)&FvDevicePath);\r
687 if (EFI_ERROR (Status)) {\r
688 FileNameDevicePath = NULL;\r
689 } else {\r
690 //\r
691 // Build a device path to the file in the FV to pass into gBS->LoadImage\r
692 //\r
693 EfiInitializeFwVolDevicepathNode (&mFvDevicePath.File, DriverName);\r
1232b214 694 SetDevicePathEndNode (&mFvDevicePath.End);\r
28a00297 695\r
9c4ac31c 696 FileNameDevicePath = AppendDevicePath (\r
022c6d45 697 FvDevicePath,\r
28a00297 698 (EFI_DEVICE_PATH_PROTOCOL *)&mFvDevicePath\r
699 );\r
700 }\r
701\r
702 return FileNameDevicePath;\r
703}\r
704\r
705\r
706\r
162ed594 707/**\r
708 Add an entry to the mDiscoveredList. Allocate memory to store the DriverEntry,\r
28a00297 709 and initilize any state variables. Read the Depex from the FV and store it\r
710 in DriverEntry. Pre-process the Depex to set the SOR, Before and After state.\r
711 The Discovered list is never free'ed and contains booleans that represent the\r
712 other possible DXE driver states.\r
713\r
022c6d45 714 @param Fv Fv protocol, needed to read Depex info out of\r
715 FLASH.\r
716 @param FvHandle Handle for Fv, needed in the\r
717 EFI_CORE_DRIVER_ENTRY so that the PE image can be\r
718 read out of the FV at a later time.\r
719 @param DriverName Name of driver to add to mDiscoveredList.\r
28a00297 720\r
022c6d45 721 @retval EFI_SUCCESS If driver was added to the mDiscoveredList.\r
722 @retval EFI_ALREADY_STARTED The driver has already been started. Only one\r
723 DriverName may be active in the system at any one\r
162ed594 724 time.\r
28a00297 725\r
162ed594 726**/\r
727EFI_STATUS\r
728CoreAddToDriverList (\r
729 IN EFI_FIRMWARE_VOLUME2_PROTOCOL *Fv,\r
730 IN EFI_HANDLE FvHandle,\r
731 IN EFI_GUID *DriverName\r
732 )\r
28a00297 733{\r
734 EFI_CORE_DRIVER_ENTRY *DriverEntry;\r
735\r
022c6d45 736\r
28a00297 737 //\r
022c6d45 738 // Create the Driver Entry for the list. ZeroPool initializes lots of variables to\r
28a00297 739 // NULL or FALSE.\r
740 //\r
9c4ac31c 741 DriverEntry = AllocateZeroPool (sizeof (EFI_CORE_DRIVER_ENTRY));\r
28a00297 742 ASSERT (DriverEntry != NULL);\r
743\r
744 DriverEntry->Signature = EFI_CORE_DRIVER_ENTRY_SIGNATURE;\r
e94a9ff7 745 CopyGuid (&DriverEntry->FileName, DriverName);\r
28a00297 746 DriverEntry->FvHandle = FvHandle;\r
747 DriverEntry->Fv = Fv;\r
748 DriverEntry->FvFileDevicePath = CoreFvToDevicePath (Fv, FvHandle, DriverName);\r
749\r
750 CoreGetDepexSectionAndPreProccess (DriverEntry);\r
022c6d45 751\r
28a00297 752 CoreAcquireDispatcherLock ();\r
022c6d45 753\r
28a00297 754 InsertTailList (&mDiscoveredList, &DriverEntry->Link);\r
755\r
756 CoreReleaseDispatcherLock ();\r
757\r
758 return EFI_SUCCESS;\r
759}\r
760\r
bbc0f1bb 761\r
162ed594 762/**\r
bbc0f1bb 763 Check if a FV Image type file (EFI_FV_FILETYPE_FIRMWARE_VOLUME_IMAGE) is\r
764 described by a EFI_HOB_FIRMWARE_VOLUME2 Hob.\r
765\r
022c6d45 766 @param FvHandle The handle which FVB protocol installed on.\r
767 @param DriverName The driver guid specified.\r
bbc0f1bb 768\r
022c6d45 769 @retval TRUE This file is found in a EFI_HOB_FIRMWARE_VOLUME2\r
770 Hob.\r
162ed594 771 @retval FALSE Not found.\r
bbc0f1bb 772\r
162ed594 773**/\r
162ed594 774BOOLEAN\r
775FvFoundInHobFv2 (\r
776 IN EFI_HANDLE FvHandle,\r
777 IN CONST EFI_GUID *DriverName\r
778 )\r
bbc0f1bb 779{\r
780 EFI_PEI_HOB_POINTERS HobFv2;\r
022c6d45 781\r
bbc0f1bb 782 HobFv2.Raw = GetHobList ();\r
022c6d45 783\r
bbc0f1bb 784 while ((HobFv2.Raw = GetNextHob (EFI_HOB_TYPE_FV2, HobFv2.Raw)) != NULL) {\r
785 if (CompareGuid (DriverName, &HobFv2.FirmwareVolume2->FileName)) {\r
b0d803fe 786 return TRUE;\r
bbc0f1bb 787 }\r
788 HobFv2.Raw = GET_NEXT_HOB (HobFv2);\r
789 }\r
790\r
791 return FALSE;\r
792}\r
28a00297 793\r
794\r
162ed594 795\r
796/**\r
797 Get the driver from the FV through driver name, and produce a FVB protocol on FvHandle.\r
798\r
022c6d45 799 @param Fv The FIRMWARE_VOLUME protocol installed on the FV.\r
800 @param FvHandle The handle which FVB protocol installed on.\r
801 @param DriverName The driver guid specified.\r
162ed594 802\r
022c6d45 803 @retval EFI_OUT_OF_RESOURCES No enough memory or other resource.\r
804 @retval EFI_VOLUME_CORRUPTED Corrupted volume.\r
162ed594 805 @retval EFI_SUCCESS Function successfully returned.\r
806\r
807**/\r
022c6d45 808EFI_STATUS\r
28a00297 809CoreProcessFvImageFile (\r
0c2b5da8 810 IN EFI_FIRMWARE_VOLUME2_PROTOCOL *Fv,\r
28a00297 811 IN EFI_HANDLE FvHandle,\r
812 IN EFI_GUID *DriverName\r
813 )\r
28a00297 814{\r
815 EFI_STATUS Status;\r
816 EFI_SECTION_TYPE SectionType;\r
817 UINT32 AuthenticationStatus;\r
818 VOID *Buffer;\r
38837959 819 VOID *AlignedBuffer;\r
28a00297 820 UINTN BufferSize;\r
38837959 821 EFI_FIRMWARE_VOLUME_HEADER *FvHeader;\r
022c6d45 822 UINT32 FvAlignment;\r
28a00297 823\r
824 //\r
825 // Read the first (and only the first) firmware volume section\r
826 //\r
e94a9ff7 827 SectionType = EFI_SECTION_FIRMWARE_VOLUME_IMAGE;\r
828 FvHeader = NULL;\r
829 FvAlignment = 0;\r
830 Buffer = NULL;\r
831 BufferSize = 0;\r
38837959 832 AlignedBuffer = NULL;\r
28a00297 833 Status = Fv->ReadSection (\r
022c6d45 834 Fv,\r
835 DriverName,\r
836 SectionType,\r
837 0,\r
838 &Buffer,\r
e94a9ff7 839 &BufferSize,\r
840 &AuthenticationStatus\r
841 );\r
28a00297 842 if (!EFI_ERROR (Status)) {\r
843 //\r
38837959 844 // FvImage should be at its required alignment.\r
28a00297 845 //\r
38837959
LG
846 FvHeader = (EFI_FIRMWARE_VOLUME_HEADER *) Buffer;\r
847 FvAlignment = 1 << ((FvHeader->Attributes & EFI_FVB2_ALIGNMENT) >> 16);\r
848 //\r
849 // FvAlignment must be more than 8 bytes required by FvHeader structure.\r
022c6d45 850 //\r
38837959
LG
851 if (FvAlignment < 8) {\r
852 FvAlignment = 8;\r
853 }\r
e94a9ff7 854 //\r
855 // Allocate the aligned buffer for the FvImage.\r
856 //\r
b2c5e194 857 AlignedBuffer = AllocateAlignedPages (EFI_SIZE_TO_PAGES (BufferSize), (UINTN) FvAlignment);\r
38837959
LG
858 if (AlignedBuffer == NULL) {\r
859 Status = EFI_OUT_OF_RESOURCES;\r
860 } else {\r
861 //\r
862 // Move FvImage into the aligned buffer and release the original buffer.\r
863 //\r
864 CopyMem (AlignedBuffer, Buffer, BufferSize);\r
865 CoreFreePool (Buffer);\r
866 Buffer = NULL;\r
867 //\r
868 // Produce a FVB protocol for the file\r
869 //\r
870 Status = ProduceFVBProtocolOnBuffer (\r
871 (EFI_PHYSICAL_ADDRESS) (UINTN) AlignedBuffer,\r
872 (UINT64)BufferSize,\r
873 FvHandle,\r
874 NULL\r
875 );\r
876 }\r
28a00297 877 }\r
878\r
022c6d45 879 if (EFI_ERROR (Status)) {\r
38837959
LG
880 //\r
881 // ReadSection or Produce FVB failed, Free data buffer\r
882 //\r
883 if (Buffer != NULL) {\r
9c4ac31c 884 FreePool (Buffer);\r
38837959 885 }\r
022c6d45 886\r
38837959 887 if (AlignedBuffer != NULL) {\r
b2c5e194 888 FreeAlignedPages (AlignedBuffer, EFI_SIZE_TO_PAGES (BufferSize));\r
38837959 889 }\r
28a00297 890 }\r
891\r
892 return Status;\r
893}\r
894\r
28a00297 895\r
162ed594 896/**\r
897 Event notification that is fired every time a FV dispatch protocol is added.\r
28a00297 898 More than one protocol may have been added when this event is fired, so you\r
899 must loop on CoreLocateHandle () to see how many protocols were added and\r
900 do the following to each FV:\r
162ed594 901 If the Fv has already been processed, skip it. If the Fv has not been\r
28a00297 902 processed then mark it as being processed, as we are about to process it.\r
162ed594 903 Read the Fv and add any driver in the Fv to the mDiscoveredList.The\r
28a00297 904 mDiscoveredList is never free'ed and contains variables that define\r
162ed594 905 the other states the DXE driver transitions to..\r
28a00297 906 While you are at it read the A Priori file into memory.\r
907 Place drivers in the A Priori list onto the mScheduledQueue.\r
908\r
022c6d45 909 @param Event The Event that is being processed, not used.\r
162ed594 910 @param Context Event Context, not used.\r
28a00297 911\r
162ed594 912**/\r
162ed594 913VOID\r
914EFIAPI\r
915CoreFwVolEventProtocolNotify (\r
916 IN EFI_EVENT Event,\r
917 IN VOID *Context\r
918 )\r
28a00297 919{\r
920 EFI_STATUS Status;\r
921 EFI_STATUS GetNextFileStatus;\r
922 EFI_STATUS SecurityStatus;\r
0c2b5da8 923 EFI_FIRMWARE_VOLUME2_PROTOCOL *Fv;\r
28a00297 924 EFI_DEVICE_PATH_PROTOCOL *FvDevicePath;\r
925 EFI_HANDLE FvHandle;\r
926 UINTN BufferSize;\r
927 EFI_GUID NameGuid;\r
928 UINTN Key;\r
929 EFI_FV_FILETYPE Type;\r
930 EFI_FV_FILE_ATTRIBUTES Attributes;\r
931 UINTN Size;\r
932 EFI_CORE_DRIVER_ENTRY *DriverEntry;\r
933 EFI_GUID *AprioriFile;\r
934 UINTN AprioriEntryCount;\r
935 UINTN Index;\r
936 LIST_ENTRY *Link;\r
937 UINT32 AuthenticationStatus;\r
938 UINTN SizeOfBuffer;\r
939\r
940\r
941 while (TRUE) {\r
942 BufferSize = sizeof (EFI_HANDLE);\r
943 Status = CoreLocateHandle (\r
e94a9ff7 944 ByRegisterNotify,\r
945 NULL,\r
946 mFwVolEventRegistration,\r
947 &BufferSize,\r
948 &FvHandle\r
949 );\r
28a00297 950 if (EFI_ERROR (Status)) {\r
951 //\r
952 // If no more notification events exit\r
953 //\r
954 return;\r
955 }\r
956\r
957 if (FvHasBeenProcessed (FvHandle)) {\r
958 //\r
959 // This Fv has already been processed so lets skip it!\r
960 //\r
961 continue;\r
962 }\r
963\r
964 Status = CoreHandleProtocol (FvHandle, &gEfiFirmwareVolumeDispatchProtocolGuid, (VOID **)&Fv);\r
965 if (EFI_ERROR (Status)) {\r
966 //\r
967 // If no dispatch protocol then skip, but do not marked as being processed as it\r
968 // may show up later.\r
969 //\r
970 continue;\r
971 }\r
972\r
973 //\r
974 // Since we are about to process this Fv mark it as processed.\r
975 //\r
976 FvIsBeingProcesssed (FvHandle);\r
977\r
0c2b5da8 978 Status = CoreHandleProtocol (FvHandle, &gEfiFirmwareVolume2ProtocolGuid, (VOID **)&Fv);\r
28a00297 979 if (EFI_ERROR (Status)) {\r
980 //\r
981 // The Handle has a FirmwareVolumeDispatch protocol and should also contiain\r
982 // a FirmwareVolume protocol thus we should never get here.\r
983 //\r
984 ASSERT (FALSE);\r
985 continue;\r
986 }\r
022c6d45 987\r
28a00297 988 Status = CoreHandleProtocol (FvHandle, &gEfiDevicePathProtocolGuid, (VOID **)&FvDevicePath);\r
989 if (EFI_ERROR (Status)) {\r
990 //\r
991 // The Firmware volume doesn't have device path, can't be dispatched.\r
992 //\r
993 continue;\r
994 }\r
022c6d45 995\r
28a00297 996 //\r
022c6d45 997 // Evaluate the authentication status of the Firmware Volume through\r
28a00297 998 // Security Architectural Protocol\r
999 //\r
1000 if (gSecurity != NULL) {\r
1001 SecurityStatus = gSecurity->FileAuthenticationState (\r
022c6d45 1002 gSecurity,\r
1003 0,\r
28a00297 1004 FvDevicePath\r
1005 );\r
1006 if (SecurityStatus != EFI_SUCCESS) {\r
1007 //\r
1008 // Security check failed. The firmware volume should not be used for any purpose.\r
1009 //\r
1010 continue;\r
1011 }\r
022c6d45 1012 }\r
1013\r
28a00297 1014 //\r
022c6d45 1015 // Discover Drivers in FV and add them to the Discovered Driver List.\r
1016 // Process EFI_FV_FILETYPE_DRIVER type and then EFI_FV_FILETYPE_COMBINED_PEIM_DRIVER\r
28a00297 1017 // EFI_FV_FILETYPE_DXE_CORE is processed to produce a Loaded Image protocol for the core\r
1018 // EFI_FV_FILETYPE_FIRMWARE_VOLUME_IMAGE is processed to create a Fvb\r
1019 //\r
e94a9ff7 1020 for (Index = 0; Index < sizeof (mDxeFileTypes) / sizeof (EFI_FV_FILETYPE); Index++) {\r
28a00297 1021 //\r
1022 // Initialize the search key\r
1023 //\r
1024 Key = 0;\r
1025 do {\r
1026 Type = mDxeFileTypes[Index];\r
1027 GetNextFileStatus = Fv->GetNextFile (\r
022c6d45 1028 Fv,\r
28a00297 1029 &Key,\r
022c6d45 1030 &Type,\r
1031 &NameGuid,\r
1032 &Attributes,\r
28a00297 1033 &Size\r
1034 );\r
1035 if (!EFI_ERROR (GetNextFileStatus)) {\r
1036 if (Type == EFI_FV_FILETYPE_DXE_CORE) {\r
1037 //\r
1038 // If this is the DXE core fill in it's DevicePath & DeviceHandle\r
1039 //\r
1040 if (gDxeCoreLoadedImage->FilePath == NULL) {\r
1041 if (CompareGuid (&NameGuid, gDxeCoreFileName)) {\r
1042 //\r
1043 // Maybe One specail Fv cantains only one DXE_CORE module, so its device path must\r
1044 // be initialized completely.\r
1045 //\r
1046 EfiInitializeFwVolDevicepathNode (&mFvDevicePath.File, &NameGuid);\r
1232b214 1047 SetDevicePathEndNode (&mFvDevicePath.End);\r
28a00297 1048\r
9c4ac31c 1049 gDxeCoreLoadedImage->FilePath = DuplicateDevicePath (\r
28a00297 1050 (EFI_DEVICE_PATH_PROTOCOL *)&mFvDevicePath\r
1051 );\r
1052 gDxeCoreLoadedImage->DeviceHandle = FvHandle;\r
1053 }\r
1054 }\r
1055 } else if (Type == EFI_FV_FILETYPE_FIRMWARE_VOLUME_IMAGE) {\r
bbc0f1bb 1056 //\r
022c6d45 1057 // Check if this EFI_FV_FILETYPE_FIRMWARE_VOLUME_IMAGE file has already\r
bbc0f1bb 1058 // been extracted.\r
1059 //\r
1060 if (FvFoundInHobFv2 (FvHandle, &NameGuid)) {\r
1061 continue;\r
1062 }\r
28a00297 1063 //\r
1064 // Found a firmware volume image. Produce a firmware volume block\r
022c6d45 1065 // protocol for it so it gets dispatched from. This is usually a\r
28a00297 1066 // capsule.\r
1067 //\r
1068 CoreProcessFvImageFile (Fv, FvHandle, &NameGuid);\r
1069 } else {\r
1070 //\r
1071 // Transition driver from Undiscovered to Discovered state\r
1072 //\r
1073 CoreAddToDriverList (Fv, FvHandle, &NameGuid);\r
1074 }\r
1075 }\r
1076 } while (!EFI_ERROR (GetNextFileStatus));\r
1077 }\r
022c6d45 1078\r
28a00297 1079 //\r
1080 // Read the array of GUIDs from the Apriori file if it is present in the firmware volume\r
1081 //\r
1082 AprioriFile = NULL;\r
1083 Status = Fv->ReadSection (\r
1084 Fv,\r
1085 &gAprioriGuid,\r
1086 EFI_SECTION_RAW,\r
1087 0,\r
1088 (VOID **)&AprioriFile,\r
1089 &SizeOfBuffer,\r
1090 &AuthenticationStatus\r
1091 );\r
1092 if (!EFI_ERROR (Status)) {\r
1093 AprioriEntryCount = SizeOfBuffer / sizeof (EFI_GUID);\r
1094 } else {\r
1095 AprioriEntryCount = 0;\r
1096 }\r
1097\r
1098 //\r
1099 // Put drivers on Apriori List on the Scheduled queue. The Discovered List includes\r
1100 // drivers not in the current FV and these must be skipped since the a priori list\r
1101 // is only valid for the FV that it resided in.\r
1102 //\r
1103 CoreAcquireDispatcherLock ();\r
022c6d45 1104\r
28a00297 1105 for (Index = 0; Index < AprioriEntryCount; Index++) {\r
1106 for (Link = mDiscoveredList.ForwardLink; Link != &mDiscoveredList; Link = Link->ForwardLink) {\r
1107 DriverEntry = CR(Link, EFI_CORE_DRIVER_ENTRY, Link, EFI_CORE_DRIVER_ENTRY_SIGNATURE);\r
1108 if (CompareGuid (&DriverEntry->FileName, &AprioriFile[Index]) &&\r
1109 (FvHandle == DriverEntry->FvHandle)) {\r
1110 DriverEntry->Dependent = FALSE;\r
1111 DriverEntry->Scheduled = TRUE;\r
1112 InsertTailList (&mScheduledQueue, &DriverEntry->ScheduledLink);\r
1113 break;\r
1114 }\r
1115 }\r
1116 }\r
1117\r
1118 CoreReleaseDispatcherLock ();\r
1119\r
1120 //\r
022c6d45 1121 // Free data allocated by Fv->ReadSection ()\r
28a00297 1122 //\r
022c6d45 1123 CoreFreePool (AprioriFile);\r
28a00297 1124 }\r
1125}\r
1126\r
1127\r
28a00297 1128\r
162ed594 1129/**\r
28a00297 1130 Initialize the dispatcher. Initialize the notification function that runs when\r
e94a9ff7 1131 an FV2 protocol is added to the system.\r
28a00297 1132\r
162ed594 1133**/\r
1134VOID\r
1135CoreInitializeDispatcher (\r
1136 VOID\r
1137 )\r
28a00297 1138{\r
7899b797 1139 mFwVolEvent = EfiCreateProtocolNotifyEvent (\r
022c6d45 1140 &gEfiFirmwareVolume2ProtocolGuid,\r
28a00297 1141 TPL_CALLBACK,\r
1142 CoreFwVolEventProtocolNotify,\r
1143 NULL,\r
7899b797 1144 &mFwVolEventRegistration\r
28a00297 1145 );\r
1146}\r
1147\r
1148//\r
1149// Function only used in debug builds\r
1150//\r
162ed594 1151\r
1152/**\r
1153 Traverse the discovered list for any drivers that were discovered but not loaded\r
1154 because the dependency experessions evaluated to false.\r
1155\r
1156**/\r
28a00297 1157VOID\r
1158CoreDisplayDiscoveredNotDispatched (\r
1159 VOID\r
1160 )\r
28a00297 1161{\r
1162 LIST_ENTRY *Link;\r
1163 EFI_CORE_DRIVER_ENTRY *DriverEntry;\r
1164\r
1165 for (Link = mDiscoveredList.ForwardLink;Link !=&mDiscoveredList; Link = Link->ForwardLink) {\r
1166 DriverEntry = CR(Link, EFI_CORE_DRIVER_ENTRY, Link, EFI_CORE_DRIVER_ENTRY_SIGNATURE);\r
1167 if (DriverEntry->Dependent) {\r
162ed594 1168 DEBUG ((DEBUG_LOAD, "Driver %g was discovered but not loaded!!\n", &DriverEntry->FileName));\r
28a00297 1169 }\r
1170 }\r
1171}\r