diff options
author | Daniel Kiper <[email protected]> | 2017-06-22 12:51:37 +0200 |
---|---|---|
committer | Ingo Molnar <[email protected]> | 2017-06-23 11:11:03 +0200 |
commit | 6c64447ec58b0bac612732303f7ab04562124587 (patch) | |
tree | 8005bb035065983c42fbf0421db2b25455f53f4c /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | 457ea3f7e97881f937136ce0ba1f29f82b9abdb0 (diff) |
x86/xen/efi: Initialize only the EFI struct members used by Xen
The current approach, which is the wholesale efi struct initialization from
a 'efi_xen' local template is not robust. Usually if new member is defined
then it is properly initialized in drivers/firmware/efi/efi.c, but not in
arch/x86/xen/efi.c.
The effect is that the Xen initialization clears any fields the generic code
might have set and the Xen code does not know about yet.
I saw this happen a few times, so let's initialize only the EFI struct members
used by Xen and maintain no local duplicate, to avoid such issues in the future.
Signed-off-by: Daniel Kiper <[email protected]>
Reviewed-by: Boris Ostrovsky <[email protected]>
Acked-by: Ard Biesheuvel <[email protected]>
Cc: Linus Torvalds <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: Thomas Gleixner <[email protected]>
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Link: http://lkml.kernel.org/r/[email protected]
[ Clarified the changelog. ]
Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions