summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKyösti Mälkki <kyosti.malkki@gmail.com>2016-11-19 16:39:10 +0200
committerKyösti Mälkki <kyosti.malkki@gmail.com>2016-11-20 03:10:32 +0100
commit78c5f0cc029ab877ab5bf018abed18684c038602 (patch)
treefc9df13d1f6595554862bc994f6283fdc4226d20
parentdfb2de80ec7a4cc26bc31158405620e807072714 (diff)
arch/x86 GDT: Fix orphan debug output
On S3 resume path, CBMEM_ID_GDT already exists but we only printed the final "ok" string. Always tell GDT is about to be moved. Change-Id: Ic91c5389cf4d47d28a6c54db152c18541c413bc1 Signed-off-by: Kyösti Mälkki <kyosti.malkki@gmail.com> Reviewed-on: https://review.coreboot.org/17500 Tested-by: build bot (Jenkins) Reviewed-by: Aaron Durbin <adurbin@chromium.org>
-rw-r--r--src/arch/x86/gdt.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/arch/x86/gdt.c b/src/arch/x86/gdt.c
index fe14155dd6..982b8ae9d2 100644
--- a/src/arch/x86/gdt.c
+++ b/src/arch/x86/gdt.c
@@ -45,9 +45,9 @@ static void move_gdt(int is_recovery)
printk(BIOS_ERR, "Error: Could not relocate GDT.\n");
return;
}
- printk(BIOS_DEBUG, "Moving GDT to %p...", newgdt);
memcpy((void*)newgdt, &gdt, num_gdt_bytes);
}
+ printk(BIOS_DEBUG, "Moving GDT to %p...", newgdt);
gdtarg.base = (uintptr_t)newgdt;
gdtarg.limit = num_gdt_bytes - 1;