[lkml]   [2011]   [May]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 4/4] x86, mce: Have MCE persistent event off by default for now
    Em Wed, May 04, 2011 at 02:40:37PM -0700, Luck, Tony escreveu:
    > > Yes, i definitely think a gateway to printk would be useful, so that the system
    > > can log MCE events the syslog way as well. This probably makes sense for
    > > persistent events in general, not just MCE events.
    > s/as well/instead/ ??? If the persistent event mechanism is correctly feeding
    > data to a mart daemon, I don't think we need any printk() chatter. It is only
    > if this is not working that we'd want to see some console logging.
    > I agree that this isn't just a property of the MCE persistent event - other
    > persistent events would very likely want a way to shout for help if the events
    > are piling up with no listener.
    > > printk itself could become a persistent event. (Transparently and without
    > > breaking compatible syslogd/klogd functionality.)
    > Someone from Google was very skeptical of printk() remaining stable from
    > release to release ... a big issue when you have some heavy duty infrastructure
    > trying to parse and consume these messages. We should really consider such
    > stuff a user visible ABI, and thus not subject to random breakage - which
    > is a radical departure from our current attitude to printk().

    what is the problem with adding free form additional info to whatever
    turns into heavenly for ever unchanged dogma? :-)

    - Arnaldo

     \ /
      Last update: 2011-05-05 03:37    [W:0.278 / U:5.140 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site