Fix MB calculation in the reporting of the MTRR hole
authorDuncan Laurie <dlaurie@chromium.org>
Fri, 6 Jan 2012 23:49:30 +0000 (15:49 -0800)
committerStefan Reinauer <stefan.reinauer@coreboot.org>
Fri, 30 Mar 2012 15:55:55 +0000 (17:55 +0200)
Change-Id: I34b5c4ffd2a3f3e895d2bffedce1c00ee9aea942
Signed-off-by: Duncan Laurie <dlaurie@google.com>
Reviewed-on: http://review.coreboot.org/763
Tested-by: build bot (Jenkins)
Reviewed-by: Ronald G. Minnich <rminnich@gmail.com>
src/cpu/x86/mtrr/mtrr.c

index 8dccfefa042f1a43b8cbea6e1a394a541ae63e46..5f5e02bbb1c9d41ea78433b998c16647c109b9f2 100644 (file)
@@ -306,7 +306,7 @@ static unsigned int range_to_mtrr(unsigned int reg,
 
        if (hole_sizek) {
                printk(BIOS_DEBUG, "Adding hole at %ldMB-%ldMB\n",
-                      hole_startk, hole_startk + hole_sizek);
+                      hole_startk >> 10, (hole_startk + hole_sizek) >> 10);
                reg = range_to_mtrr(reg, hole_startk, hole_sizek,
                              next_range_startk, MTRR_TYPE_UNCACHEABLE,
                              address_bits, above4gb);