On Mon, Feb 26, 2018 at 11:37:09AM +0300, Kirill A. Shutemov wrote: > On Mon, Feb 26, 2018 at 11:15:34AM +0300, Cyrill Gorcunov wrote: > > On Mon, Feb 26, 2018 at 11:02:56AM +0300, Kirill A. Shutemov wrote: > > ... > > > > Also, could do a puts() hexdump of the affected memory area _before_ we overwrite > > > > it? Is it empty? Could we add some debug warning that checks that it's all zeroes? > > > > > > The problem is that we don't really have a way get a message out of there. > > > > > > http://lkml.kernel.org/r/793b9c55-e85b-97b5-c857-dd8edcda4081@xxxxxxxxx > > > > > > > I'm sorry for stepping in (since I didn't follow the series in details) > > but can't we use vga memory here and print this early data tere? > > I have no idea how to do this :/ https://wiki.osdev.org/Printing_To_Screen Kirill, note that it might not do the trick at all, just give the link a shot and check if it would worth the efforts. > > And what about systems without monitor at all? Such early boot things *require* additional equipment anyway jtag/monitors/etc for debug stage at least. -- To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|