]> git.proxmox.com Git - mirror_edk2.git/blame_incremental - MdeModulePkg/Core/Dxe/Dispatcher/Dispatcher.c
PI 1.1 SMM Feature Check-in
[mirror_edk2.git] / MdeModulePkg / Core / Dxe / Dispatcher / Dispatcher.c
... / ...
CommitLineData
1/** @file\r
2 DXE Dispatcher.\r
3\r
4 Step #1 - When a FV protocol is added to the system every driver in the FV\r
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
9 FV is only processed once.\r
10\r
11 Step #2 - Dispatch. Remove driver from the mScheduledQueue and load and\r
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
14 be placed on the mScheduledQueue.\r
15\r
16 Step #3 - Adding to the mScheduledQueue requires that you process Before\r
17 and After dependencies. This is done recursively as the call to add\r
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
20 processess the After dependecies by recursively calling the routine.\r
21\r
22 Dispatcher Rules:\r
23 The rules for the dispatcher are in chapter 10 of the DXE CIS. Figure 10-3\r
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
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
37\r
38**/\r
39\r
40#include "DxeMain.h"\r
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
46LIST_ENTRY mDiscoveredList = INITIALIZE_LIST_HEAD_VARIABLE (mDiscoveredList);\r
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
79EFI_FV_FILETYPE mDxeFileTypes[] = {\r
80 EFI_FV_FILETYPE_DRIVER,\r
81 EFI_FV_FILETYPE_COMBINED_PEIM_DRIVER,\r
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
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
108VOID\r
109CoreInsertOnScheduledQueueWhileProcessingBeforeAndAfter (\r
110 IN EFI_CORE_DRIVER_ENTRY *InsertedDriverEntry\r
111 );\r
112\r
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
126 @param Event The Event that is being processed, not used.\r
127 @param Context Event Context, not used.\r
128\r
129**/\r
130VOID\r
131EFIAPI\r
132CoreFwVolEventProtocolNotify (\r
133 IN EFI_EVENT Event,\r
134 IN VOID *Context\r
135 );\r
136\r
137/**\r
138 Convert FvHandle and DriverName into an EFI device path\r
139\r
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
146\r
147 @return Pointer to device path constructed from FvHandle and DriverName\r
148\r
149**/\r
150EFI_DEVICE_PATH_PROTOCOL *\r
151CoreFvToDevicePath (\r
152 IN EFI_FIRMWARE_VOLUME2_PROTOCOL *Fv,\r
153 IN EFI_HANDLE FvHandle,\r
154 IN EFI_GUID *DriverName\r
155 );\r
156\r
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
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
170\r
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
174 time.\r
175\r
176**/\r
177EFI_STATUS\r
178CoreAddToDriverList (\r
179 IN EFI_FIRMWARE_VOLUME2_PROTOCOL *Fv,\r
180 IN EFI_HANDLE FvHandle,\r
181 IN EFI_GUID *DriverName\r
182 );\r
183\r
184/**\r
185 Get the driver from the FV through driver name, and produce a FVB protocol on FvHandle.\r
186\r
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
190\r
191 @retval EFI_OUT_OF_RESOURCES No enough memory or other resource.\r
192 @retval EFI_VOLUME_CORRUPTED Corrupted volume.\r
193 @retval EFI_SUCCESS Function successfully returned.\r
194\r
195**/\r
196EFI_STATUS\r
197CoreProcessFvImageFile (\r
198 IN EFI_FIRMWARE_VOLUME2_PROTOCOL *Fv,\r
199 IN EFI_HANDLE FvHandle,\r
200 IN EFI_GUID *DriverName\r
201 );\r
202\r
203\r
204/**\r
205 Enter critical section by gaining lock on mDispatcherLock.\r
206\r
207**/\r
208VOID\r
209CoreAcquireDispatcherLock (\r
210 VOID\r
211 )\r
212{\r
213 CoreAcquireLock (&mDispatcherLock);\r
214}\r
215\r
216\r
217/**\r
218 Exit critical section by releasing lock on mDispatcherLock.\r
219\r
220**/\r
221VOID\r
222CoreReleaseDispatcherLock (\r
223 VOID\r
224 )\r
225{\r
226 CoreReleaseLock (&mDispatcherLock);\r
227}\r
228\r
229\r
230/**\r
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
234 @param DriverEntry Driver to work on.\r
235\r
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
239 @retval Error DEPEX not found.\r
240\r
241**/\r
242EFI_STATUS\r
243CoreGetDepexSectionAndPreProccess (\r
244 IN EFI_CORE_DRIVER_ENTRY *DriverEntry\r
245 )\r
246{\r
247 EFI_STATUS Status;\r
248 EFI_SECTION_TYPE SectionType;\r
249 UINT32 AuthenticationStatus;\r
250 EFI_FIRMWARE_VOLUME2_PROTOCOL *Fv;\r
251\r
252\r
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
260 DriverEntry->Fv,\r
261 &DriverEntry->FileName,\r
262 SectionType,\r
263 0,\r
264 &DriverEntry->Depex,\r
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
276 // If no Depex assume UEFI 2.0 driver model\r
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
289 }\r
290\r
291 return Status;\r
292}\r
293\r
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
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
302\r
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
307\r
308**/\r
309EFI_STATUS\r
310EFIAPI\r
311CoreSchedule (\r
312 IN EFI_HANDLE FirmwareVolumeHandle,\r
313 IN EFI_GUID *DriverName\r
314 )\r
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
325 DriverEntry->Unrequested &&\r
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
334\r
335 return EFI_SUCCESS;\r
336 }\r
337 }\r
338 return EFI_NOT_FOUND;\r
339}\r
340\r
341\r
342\r
343/**\r
344 Convert a driver from the Untrused back to the Scheduled state.\r
345\r
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
349\r
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
353\r
354**/\r
355EFI_STATUS\r
356EFIAPI\r
357CoreTrust (\r
358 IN EFI_HANDLE FirmwareVolumeHandle,\r
359 IN EFI_GUID *DriverName\r
360 )\r
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
371 DriverEntry->Untrusted &&\r
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
381\r
382 return EFI_SUCCESS;\r
383 }\r
384 }\r
385 return EFI_NOT_FOUND;\r
386}\r
387\r
388\r
389\r
390/**\r
391 This is the main Dispatcher for DXE and it exits when there are no more\r
392 drivers to run. Drain the mScheduledQueue and load and start a PE\r
393 image for each driver. Search the mDiscoveredList to see if any driver can\r
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
396 will be called, and when the Bds() exits the Dispatcher will be called\r
397 again.\r
398\r
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
402\r
403**/\r
404EFI_STATUS\r
405EFIAPI\r
406CoreDispatcher (\r
407 VOID\r
408 )\r
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 DEBUG ((DEBUG_INFO, "Loading driver %g\n", &DriverEntry->FileName));\r
446 Status = CoreLoadImage (\r
447 FALSE,\r
448 gDxeCoreImageHandle,\r
449 DriverEntry->FvFileDevicePath,\r
450 NULL,\r
451 0,\r
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
469 // Take driver from Scheduled to Initialized.\r
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
478\r
479 CoreReleaseDispatcherLock ();\r
480\r
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
493\r
494 CoreReleaseDispatcherLock ();\r
495\r
496 \r
497 REPORT_STATUS_CODE_WITH_EXTENDED_DATA (\r
498 EFI_PROGRESS_CODE,\r
499 FixedPcdGet32(PcdStatusCodeValueDxeDriverBegin),\r
500 &DriverEntry->ImageHandle,\r
501 sizeof (DriverEntry->ImageHandle)\r
502 );\r
503\r
504 Status = CoreStartImage (DriverEntry->ImageHandle, NULL, NULL);\r
505\r
506 REPORT_STATUS_CODE_WITH_EXTENDED_DATA (\r
507 EFI_PROGRESS_CODE,\r
508 FixedPcdGet32(PcdStatusCodeValueDxeDriverEnd),\r
509 &DriverEntry->ImageHandle,\r
510 sizeof (DriverEntry->ImageHandle)\r
511 );\r
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
528 }\r
529\r
530 if (DriverEntry->Dependent) {\r
531 if (CoreIsSchedulable (DriverEntry)) {\r
532 CoreInsertOnScheduledQueueWhileProcessingBeforeAndAfter (DriverEntry);\r
533 ReadyToRun = TRUE;\r
534 }\r
535 }\r
536 }\r
537 } while (ReadyToRun);\r
538\r
539 gDispatcherRunning = FALSE;\r
540\r
541 return ReturnStatus;\r
542}\r
543\r
544\r
545/**\r
546 Insert InsertedDriverEntry onto the mScheduledQueue. To do this you\r
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
549 processed you can add InsertedDriverEntry to the mScheduledQueue.\r
550 Then you can add any driver with an After dependency on InsertedDriverEntry\r
551 by recursively calling this routine.\r
552\r
553 @param InsertedDriverEntry The driver to insert on the ScheduledLink Queue\r
554\r
555**/\r
556VOID\r
557CoreInsertOnScheduledQueueWhileProcessingBeforeAndAfter (\r
558 IN EFI_CORE_DRIVER_ENTRY *InsertedDriverEntry\r
559 )\r
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
587\r
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
606\r
607/**\r
608 Return TRUE if the Fv has been processed, FALSE if not.\r
609\r
610 @param FvHandle The handle of a FV that's being tested\r
611\r
612 @retval TRUE Fv protocol on FvHandle has been processed\r
613 @retval FALSE Fv protocol on FvHandle has not yet been processed\r
614\r
615**/\r
616BOOLEAN\r
617FvHasBeenProcessed (\r
618 IN EFI_HANDLE FvHandle\r
619 )\r
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
633\r
634/**\r
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
639 @param FvHandle The handle of a FV that has been processed\r
640\r
641**/\r
642VOID\r
643FvIsBeingProcesssed (\r
644 IN EFI_HANDLE FvHandle\r
645 )\r
646{\r
647 KNOWN_HANDLE *KnownHandle;\r
648\r
649 KnownHandle = AllocatePool (sizeof (KNOWN_HANDLE));\r
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
659\r
660/**\r
661 Convert FvHandle and DriverName into an EFI device path\r
662\r
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
669\r
670 @return Pointer to device path constructed from FvHandle and DriverName\r
671\r
672**/\r
673EFI_DEVICE_PATH_PROTOCOL *\r
674CoreFvToDevicePath (\r
675 IN EFI_FIRMWARE_VOLUME2_PROTOCOL *Fv,\r
676 IN EFI_HANDLE FvHandle,\r
677 IN EFI_GUID *DriverName\r
678 )\r
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
695 SetDevicePathEndNode (&mFvDevicePath.End);\r
696\r
697 FileNameDevicePath = AppendDevicePath (\r
698 FvDevicePath,\r
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
708/**\r
709 Add an entry to the mDiscoveredList. Allocate memory to store the DriverEntry,\r
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
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
721\r
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
725 time.\r
726\r
727**/\r
728EFI_STATUS\r
729CoreAddToDriverList (\r
730 IN EFI_FIRMWARE_VOLUME2_PROTOCOL *Fv,\r
731 IN EFI_HANDLE FvHandle,\r
732 IN EFI_GUID *DriverName\r
733 )\r
734{\r
735 EFI_CORE_DRIVER_ENTRY *DriverEntry;\r
736\r
737\r
738 //\r
739 // Create the Driver Entry for the list. ZeroPool initializes lots of variables to\r
740 // NULL or FALSE.\r
741 //\r
742 DriverEntry = AllocateZeroPool (sizeof (EFI_CORE_DRIVER_ENTRY));\r
743 ASSERT (DriverEntry != NULL);\r
744\r
745 DriverEntry->Signature = EFI_CORE_DRIVER_ENTRY_SIGNATURE;\r
746 CopyGuid (&DriverEntry->FileName, DriverName);\r
747 DriverEntry->FvHandle = FvHandle;\r
748 DriverEntry->Fv = Fv;\r
749 DriverEntry->FvFileDevicePath = CoreFvToDevicePath (Fv, FvHandle, DriverName);\r
750\r
751 CoreGetDepexSectionAndPreProccess (DriverEntry);\r
752\r
753 CoreAcquireDispatcherLock ();\r
754\r
755 InsertTailList (&mDiscoveredList, &DriverEntry->Link);\r
756\r
757 CoreReleaseDispatcherLock ();\r
758\r
759 return EFI_SUCCESS;\r
760}\r
761\r
762\r
763/**\r
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
767 @param FvHandle The handle which FVB protocol installed on.\r
768 @param DriverName The driver guid specified.\r
769\r
770 @retval TRUE This file is found in a EFI_HOB_FIRMWARE_VOLUME2\r
771 Hob.\r
772 @retval FALSE Not found.\r
773\r
774**/\r
775BOOLEAN\r
776FvFoundInHobFv2 (\r
777 IN EFI_HANDLE FvHandle,\r
778 IN CONST EFI_GUID *DriverName\r
779 )\r
780{\r
781 EFI_PEI_HOB_POINTERS HobFv2;\r
782\r
783 HobFv2.Raw = GetHobList ();\r
784\r
785 while ((HobFv2.Raw = GetNextHob (EFI_HOB_TYPE_FV2, HobFv2.Raw)) != NULL) {\r
786 if (CompareGuid (DriverName, &HobFv2.FirmwareVolume2->FileName)) {\r
787 return TRUE;\r
788 }\r
789 HobFv2.Raw = GET_NEXT_HOB (HobFv2);\r
790 }\r
791\r
792 return FALSE;\r
793}\r
794\r
795\r
796\r
797/**\r
798 Get the driver from the FV through driver name, and produce a FVB protocol on FvHandle.\r
799\r
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
803\r
804 @retval EFI_OUT_OF_RESOURCES No enough memory or other resource.\r
805 @retval EFI_VOLUME_CORRUPTED Corrupted volume.\r
806 @retval EFI_SUCCESS Function successfully returned.\r
807\r
808**/\r
809EFI_STATUS\r
810CoreProcessFvImageFile (\r
811 IN EFI_FIRMWARE_VOLUME2_PROTOCOL *Fv,\r
812 IN EFI_HANDLE FvHandle,\r
813 IN EFI_GUID *DriverName\r
814 )\r
815{\r
816 EFI_STATUS Status;\r
817 EFI_SECTION_TYPE SectionType;\r
818 UINT32 AuthenticationStatus;\r
819 VOID *Buffer;\r
820 VOID *AlignedBuffer;\r
821 UINTN BufferSize;\r
822 EFI_FIRMWARE_VOLUME_HEADER *FvHeader;\r
823 UINT32 FvAlignment;\r
824\r
825 //\r
826 // Read the first (and only the first) firmware volume section\r
827 //\r
828 SectionType = EFI_SECTION_FIRMWARE_VOLUME_IMAGE;\r
829 FvHeader = NULL;\r
830 FvAlignment = 0;\r
831 Buffer = NULL;\r
832 BufferSize = 0;\r
833 AlignedBuffer = NULL;\r
834 Status = Fv->ReadSection (\r
835 Fv,\r
836 DriverName,\r
837 SectionType,\r
838 0,\r
839 &Buffer,\r
840 &BufferSize,\r
841 &AuthenticationStatus\r
842 );\r
843 if (!EFI_ERROR (Status)) {\r
844 //\r
845 // FvImage should be at its required alignment.\r
846 //\r
847 FvHeader = (EFI_FIRMWARE_VOLUME_HEADER *) Buffer;\r
848 //\r
849 // Get FvHeader alignment\r
850 //\r
851 FvAlignment = 1 << ((FvHeader->Attributes & EFI_FVB2_ALIGNMENT) >> 16);\r
852 //\r
853 // FvAlignment must be greater than or equal to 8 bytes of the minimum FFS alignment value. \r
854 //\r
855 if (FvAlignment < 8) {\r
856 FvAlignment = 8;\r
857 }\r
858 //\r
859 // Allocate the aligned buffer for the FvImage.\r
860 //\r
861 AlignedBuffer = AllocateAlignedPages (EFI_SIZE_TO_PAGES (BufferSize), (UINTN) FvAlignment);\r
862 if (AlignedBuffer == NULL) {\r
863 Status = EFI_OUT_OF_RESOURCES;\r
864 } else {\r
865 //\r
866 // Move FvImage into the aligned buffer and release the original buffer.\r
867 //\r
868 CopyMem (AlignedBuffer, Buffer, BufferSize);\r
869 CoreFreePool (Buffer);\r
870 Buffer = NULL;\r
871 //\r
872 // Produce a FVB protocol for the file\r
873 //\r
874 Status = ProduceFVBProtocolOnBuffer (\r
875 (EFI_PHYSICAL_ADDRESS) (UINTN) AlignedBuffer,\r
876 (UINT64)BufferSize,\r
877 FvHandle,\r
878 NULL\r
879 );\r
880 }\r
881 }\r
882\r
883 if (EFI_ERROR (Status)) {\r
884 //\r
885 // ReadSection or Produce FVB failed, Free data buffer\r
886 //\r
887 if (Buffer != NULL) {\r
888 FreePool (Buffer);\r
889 }\r
890\r
891 if (AlignedBuffer != NULL) {\r
892 FreeAlignedPages (AlignedBuffer, EFI_SIZE_TO_PAGES (BufferSize));\r
893 }\r
894 }\r
895\r
896 return Status;\r
897}\r
898\r
899\r
900/**\r
901 Event notification that is fired every time a FV dispatch protocol is added.\r
902 More than one protocol may have been added when this event is fired, so you\r
903 must loop on CoreLocateHandle () to see how many protocols were added and\r
904 do the following to each FV:\r
905 If the Fv has already been processed, skip it. If the Fv has not been\r
906 processed then mark it as being processed, as we are about to process it.\r
907 Read the Fv and add any driver in the Fv to the mDiscoveredList.The\r
908 mDiscoveredList is never free'ed and contains variables that define\r
909 the other states the DXE driver transitions to..\r
910 While you are at it read the A Priori file into memory.\r
911 Place drivers in the A Priori list onto the mScheduledQueue.\r
912\r
913 @param Event The Event that is being processed, not used.\r
914 @param Context Event Context, not used.\r
915\r
916**/\r
917VOID\r
918EFIAPI\r
919CoreFwVolEventProtocolNotify (\r
920 IN EFI_EVENT Event,\r
921 IN VOID *Context\r
922 )\r
923{\r
924 EFI_STATUS Status;\r
925 EFI_STATUS GetNextFileStatus;\r
926 EFI_STATUS SecurityStatus;\r
927 EFI_FIRMWARE_VOLUME2_PROTOCOL *Fv;\r
928 EFI_DEVICE_PATH_PROTOCOL *FvDevicePath;\r
929 EFI_HANDLE FvHandle;\r
930 UINTN BufferSize;\r
931 EFI_GUID NameGuid;\r
932 UINTN Key;\r
933 EFI_FV_FILETYPE Type;\r
934 EFI_FV_FILE_ATTRIBUTES Attributes;\r
935 UINTN Size;\r
936 EFI_CORE_DRIVER_ENTRY *DriverEntry;\r
937 EFI_GUID *AprioriFile;\r
938 UINTN AprioriEntryCount;\r
939 UINTN Index;\r
940 LIST_ENTRY *Link;\r
941 UINT32 AuthenticationStatus;\r
942 UINTN SizeOfBuffer;\r
943\r
944\r
945 while (TRUE) {\r
946 BufferSize = sizeof (EFI_HANDLE);\r
947 Status = CoreLocateHandle (\r
948 ByRegisterNotify,\r
949 NULL,\r
950 mFwVolEventRegistration,\r
951 &BufferSize,\r
952 &FvHandle\r
953 );\r
954 if (EFI_ERROR (Status)) {\r
955 //\r
956 // If no more notification events exit\r
957 //\r
958 return;\r
959 }\r
960\r
961 if (FvHasBeenProcessed (FvHandle)) {\r
962 //\r
963 // This Fv has already been processed so lets skip it!\r
964 //\r
965 continue;\r
966 }\r
967\r
968 //\r
969 // Since we are about to process this Fv mark it as processed.\r
970 //\r
971 FvIsBeingProcesssed (FvHandle);\r
972\r
973 Status = CoreHandleProtocol (FvHandle, &gEfiFirmwareVolume2ProtocolGuid, (VOID **)&Fv);\r
974 if (EFI_ERROR (Status)) {\r
975 //\r
976 // The Handle has a FirmwareVolumeDispatch protocol and should also contiain\r
977 // a FirmwareVolume protocol thus we should never get here.\r
978 //\r
979 ASSERT (FALSE);\r
980 continue;\r
981 }\r
982\r
983 Status = CoreHandleProtocol (FvHandle, &gEfiDevicePathProtocolGuid, (VOID **)&FvDevicePath);\r
984 if (EFI_ERROR (Status)) {\r
985 //\r
986 // The Firmware volume doesn't have device path, can't be dispatched.\r
987 //\r
988 continue;\r
989 }\r
990\r
991 //\r
992 // Evaluate the authentication status of the Firmware Volume through\r
993 // Security Architectural Protocol\r
994 //\r
995 if (gSecurity != NULL) {\r
996 SecurityStatus = gSecurity->FileAuthenticationState (\r
997 gSecurity,\r
998 0,\r
999 FvDevicePath\r
1000 );\r
1001 if (SecurityStatus != EFI_SUCCESS) {\r
1002 //\r
1003 // Security check failed. The firmware volume should not be used for any purpose.\r
1004 //\r
1005 continue;\r
1006 }\r
1007 }\r
1008\r
1009 //\r
1010 // Discover Drivers in FV and add them to the Discovered Driver List.\r
1011 // Process EFI_FV_FILETYPE_DRIVER type and then EFI_FV_FILETYPE_COMBINED_PEIM_DRIVER\r
1012 // EFI_FV_FILETYPE_DXE_CORE is processed to produce a Loaded Image protocol for the core\r
1013 // EFI_FV_FILETYPE_FIRMWARE_VOLUME_IMAGE is processed to create a Fvb\r
1014 //\r
1015 for (Index = 0; Index < sizeof (mDxeFileTypes) / sizeof (EFI_FV_FILETYPE); Index++) {\r
1016 //\r
1017 // Initialize the search key\r
1018 //\r
1019 Key = 0;\r
1020 do {\r
1021 Type = mDxeFileTypes[Index];\r
1022 GetNextFileStatus = Fv->GetNextFile (\r
1023 Fv,\r
1024 &Key,\r
1025 &Type,\r
1026 &NameGuid,\r
1027 &Attributes,\r
1028 &Size\r
1029 );\r
1030 if (!EFI_ERROR (GetNextFileStatus)) {\r
1031 if (Type == EFI_FV_FILETYPE_DXE_CORE) {\r
1032 //\r
1033 // If this is the DXE core fill in it's DevicePath & DeviceHandle\r
1034 //\r
1035 if (gDxeCoreLoadedImage->FilePath == NULL) {\r
1036 if (CompareGuid (&NameGuid, gDxeCoreFileName)) {\r
1037 //\r
1038 // Maybe One specail Fv cantains only one DXE_CORE module, so its device path must\r
1039 // be initialized completely.\r
1040 //\r
1041 EfiInitializeFwVolDevicepathNode (&mFvDevicePath.File, &NameGuid);\r
1042 SetDevicePathEndNode (&mFvDevicePath.End);\r
1043\r
1044 gDxeCoreLoadedImage->FilePath = DuplicateDevicePath (\r
1045 (EFI_DEVICE_PATH_PROTOCOL *)&mFvDevicePath\r
1046 );\r
1047 gDxeCoreLoadedImage->DeviceHandle = FvHandle;\r
1048 }\r
1049 }\r
1050 } else if (Type == EFI_FV_FILETYPE_FIRMWARE_VOLUME_IMAGE) {\r
1051 //\r
1052 // Check if this EFI_FV_FILETYPE_FIRMWARE_VOLUME_IMAGE file has already\r
1053 // been extracted.\r
1054 //\r
1055 if (FvFoundInHobFv2 (FvHandle, &NameGuid)) {\r
1056 continue;\r
1057 }\r
1058 //\r
1059 // Found a firmware volume image. Produce a firmware volume block\r
1060 // protocol for it so it gets dispatched from. This is usually a\r
1061 // capsule.\r
1062 //\r
1063 CoreProcessFvImageFile (Fv, FvHandle, &NameGuid);\r
1064 } else {\r
1065 //\r
1066 // Transition driver from Undiscovered to Discovered state\r
1067 //\r
1068 CoreAddToDriverList (Fv, FvHandle, &NameGuid);\r
1069 }\r
1070 }\r
1071 } while (!EFI_ERROR (GetNextFileStatus));\r
1072 }\r
1073\r
1074 //\r
1075 // Read the array of GUIDs from the Apriori file if it is present in the firmware volume\r
1076 //\r
1077 AprioriFile = NULL;\r
1078 Status = Fv->ReadSection (\r
1079 Fv,\r
1080 &gAprioriGuid,\r
1081 EFI_SECTION_RAW,\r
1082 0,\r
1083 (VOID **)&AprioriFile,\r
1084 &SizeOfBuffer,\r
1085 &AuthenticationStatus\r
1086 );\r
1087 if (!EFI_ERROR (Status)) {\r
1088 AprioriEntryCount = SizeOfBuffer / sizeof (EFI_GUID);\r
1089 } else {\r
1090 AprioriEntryCount = 0;\r
1091 }\r
1092\r
1093 //\r
1094 // Put drivers on Apriori List on the Scheduled queue. The Discovered List includes\r
1095 // drivers not in the current FV and these must be skipped since the a priori list\r
1096 // is only valid for the FV that it resided in.\r
1097 //\r
1098 CoreAcquireDispatcherLock ();\r
1099\r
1100 for (Index = 0; Index < AprioriEntryCount; Index++) {\r
1101 for (Link = mDiscoveredList.ForwardLink; Link != &mDiscoveredList; Link = Link->ForwardLink) {\r
1102 DriverEntry = CR(Link, EFI_CORE_DRIVER_ENTRY, Link, EFI_CORE_DRIVER_ENTRY_SIGNATURE);\r
1103 if (CompareGuid (&DriverEntry->FileName, &AprioriFile[Index]) &&\r
1104 (FvHandle == DriverEntry->FvHandle)) {\r
1105 DriverEntry->Dependent = FALSE;\r
1106 DriverEntry->Scheduled = TRUE;\r
1107 InsertTailList (&mScheduledQueue, &DriverEntry->ScheduledLink);\r
1108 break;\r
1109 }\r
1110 }\r
1111 }\r
1112\r
1113 CoreReleaseDispatcherLock ();\r
1114\r
1115 //\r
1116 // Free data allocated by Fv->ReadSection ()\r
1117 //\r
1118 CoreFreePool (AprioriFile);\r
1119 }\r
1120}\r
1121\r
1122\r
1123\r
1124/**\r
1125 Initialize the dispatcher. Initialize the notification function that runs when\r
1126 an FV2 protocol is added to the system.\r
1127\r
1128**/\r
1129VOID\r
1130CoreInitializeDispatcher (\r
1131 VOID\r
1132 )\r
1133{\r
1134 mFwVolEvent = EfiCreateProtocolNotifyEvent (\r
1135 &gEfiFirmwareVolume2ProtocolGuid,\r
1136 TPL_CALLBACK,\r
1137 CoreFwVolEventProtocolNotify,\r
1138 NULL,\r
1139 &mFwVolEventRegistration\r
1140 );\r
1141}\r
1142\r
1143//\r
1144// Function only used in debug builds\r
1145//\r
1146\r
1147/**\r
1148 Traverse the discovered list for any drivers that were discovered but not loaded\r
1149 because the dependency experessions evaluated to false.\r
1150\r
1151**/\r
1152VOID\r
1153CoreDisplayDiscoveredNotDispatched (\r
1154 VOID\r
1155 )\r
1156{\r
1157 LIST_ENTRY *Link;\r
1158 EFI_CORE_DRIVER_ENTRY *DriverEntry;\r
1159\r
1160 for (Link = mDiscoveredList.ForwardLink;Link !=&mDiscoveredList; Link = Link->ForwardLink) {\r
1161 DriverEntry = CR(Link, EFI_CORE_DRIVER_ENTRY, Link, EFI_CORE_DRIVER_ENTRY_SIGNATURE);\r
1162 if (DriverEntry->Dependent) {\r
1163 DEBUG ((DEBUG_LOAD, "Driver %g was discovered but not loaded!!\n", &DriverEntry->FileName));\r
1164 }\r
1165 }\r
1166}\r