On 2013-08-23 22:17, Borislav Petkov wrote: > On Fri, Aug 23, 2013 at 06:40:46PM +0200, Jan Kiszka wrote: >> Below some hunks to get it working again - at least in the absence of >> any microcode in the initrd. Marking all involved functions as __init >> is another option (as __init implies notrace). But I bet there is more >> hidden. I see e.g. a pr_warn() in find_cpio_init that should trigger >> the issue as well if we hit the error it reports (btw. printing at >> this point of the boot should not work anyway, should it?). > > I guess we can do early_printk there instead as x86_64_start_kernel() > does it but I'm not sure for the 32-bit case where we call > load_ucode_bsp/ap before we've even enabled paging.
early_printk doesn't seem to work as well on 32-bit until paging was enabled. Jan -- Siemens AG, Corporate Technology, CT RTC ITP SES-DE Corporate Competence Center Embedded Linux -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
