On Thu, Jun 11, 2009 at 03:57:56PM -0700, Grant Erickson wrote: > On 6/11/09 11:52 AM, Robin Getz wrote: > > On Thu 11 Jun 2009 13:53, David VomLehn pondered: > >> On Wed, Jun 10, 2009 at 09:26:40PM -0400, Robin Getz wrote: > >>> I would be interested in Paul and Russell - how have you solved this > >>> issue? (Or do your kernel's never crash? :) > >> > >> Our kernel does crash, so we have to do this. I had submitted a patch a > >> while ago that tweaks emit_log_char, but this was bounced, reasonably, > >> because it would be interferring with the great majority of people who > >> are not interested in capturing log output. The suggestion was made that > >> we do this with a console driver. I've recently got a version working, > >> as a module, but I've only started testing of the version integrated > >> into the kernel tree. Still, post early, post often, so I've appended > >> a version of the patch here to see if this seems to be the right > >> direction. > > > > Yeah - it looks like n people have done this n ways. > > > > I think even Andrew M had mentioned that he had done something in a past > > embedded life. > > > > I think what you have would do what I need it to do - I'm not so sure about > > what Wolfgang/Grant had in mind (- since they wanted also to dump buffers > > from the bootloader into the console for syslog processing)... > > Regrettably, I have not had the time to follow-up on this since my last > commentary in March: > > http://lkml.org/lkml/2009/3/31/293 > > However, from what I can glean of the discussion, you are correct that this > does not precisely cover what Wolfgang (originally) or, later, I was working > towards in that neither boot loader logs nor round-trip log buffering > (bootloader to kernel and back again) are covered. > > However, the value and what's being proposed here and what I and others > proposed--at least in the embedded kingdom--seems high and the features and > implementation needn't be mutually exclusive. I agree. In this case, we have three different approaches to three different problems (bootloader buffers, continuous state logging, and in-kernel capture of logging). All are problems that need to be solved. Personally, I'd love to have the continuous state logging, though I don't need the bootloader buffer part. > Grant -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
