On Tue, Mar 04, 2008 at 06:05:06PM +0100, Zoltan Menyhart wrote: > This patch adds a lock free, yet safe way of storing MCA/INIT logs. > You will not end up with logs mixed up from different MCAs. A good goal. > The MCAs/INITs are rare. One hopes. :-) > There is no use wasting much permanent resources. Sometimes a necessary evil. Normal memory allocation routines cannot be called from MCA/INIT context. > Should you see a burst of events, they are not uncorrelated. > Only the recovered events are treated. Should you miss one, > you'll see it later :-) > With the others, you will not be able to store them on disk anyway. Even if the system is going down it is still nice to try to go down gracefully. Taking a system dump and logging as much as possible is usefull, too. > There are IA64_MAX_MCA_INIT_BUFS log buffers for the MCA, and > another IA64_MAX_MCA_INIT_BUFS log buffers for the INIT handler. > > IA64_MAX_MCA_INIT_BUFS >= 2. > > There is no per CPU log buffer. In the case where all the CPUs are INITed, what happens? Does this assume only one CPU at a time processes/logs records? > The code does not assume that the rendezvous always works. Could you explain. Do you mean MCA/INIT rendezvous? -- Russ Anderson, OS RAS/Partitioning Project Lead SGI - Silicon Graphics Inc rja@xxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|