On Thu, 19 Jun 2014, Steven Rostedt wrote: > > I don't think there is a need for a global stop_machine()-like > > synchronization here. The printing CPU will be sending IPI to the CPU N+1 > > only after it has finished printing CPU N stacktrace. > > So you plan on sending an IPI to a CPU then wait for it to acknowledge > that it is spinning, and then print out the data and then tell the CPU > it can stop spinning?
Yes, that was exactly my idea. You have to be synchronized with the CPU receiving the NMI anyway in case you'd like to get its pt_regs and dump those as part of the dump. -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
