"Sampathkumar, Kishore (STSD)" <[EMAIL PROTECTED]> writes: > I tried the below suggestion. It doesn't seem to work. > > What I now notice is that, the system reboots immediately on executing > the "memory" in load_segments(). It doesn't ever get to executing > set_idt() and the printk statements I have placed after that. > > Wanted to know: by placing "memory" in load_segments(), you are > essentially inserting a memory barrier, isn't it? So, is this just to > ensure ordered execution of memory store operations involved in code > before and the code after "memory"?
Does this work if you try this on a kernel where you don't have to patch kexec in? Eric
_______________________________________________ fastboot mailing list [email protected] https://lists.osdl.org/mailman/listinfo/fastboot
