lkml.org 
[lkml]   [2007]   [Aug]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [patch] add kdump_after_notifier
    * Takenori Nagano <t-nagano@ah.jp.nec.com> [2007-08-16 11:26]:
    > Vivek Goyal wrote:
    > > - Modify Kdump to register on die_chain list.
    > > - Modify Kdb to register on die_chain list.
    > > - Export all the registered members of die_chain through sysfs along with
    > > their priorities. Priorities should be modifiable. Most likely one
    > > shall have to introduce additional field in struct notifier_block. This
    > > field will be a string as an identifier of the user registerd. e.g
    > > "Kdump", "Kdb" etc.
    > >
    > > Now user will be able to view all the die_chain users through sysfs and
    > > be able to modify the order in which these should run by modifying their
    > > priority. Hence all the RAS tools can co-exist.
    >
    > This is my image of your proposal.
    >
    > - Print current order
    >
    > # cat /sys/class/misc/debug/panic_notifier_list
    > priority name
    > 1 IPMI
    > 2 watchdog
    > 3 Kdb
    > 4 Kdump

    I think something like

    /sys/class/misc/debug/panic_notifier/ipmi/priority
    /sys/class/misc/debug/panic_notifier/watchdog/priority
    /sys/class/misc/debug/panic_notifier/kdb/priority
    /sys/class/misc/debug/panic_notifier/kdump/priority

    would be better. It's more self-describing if you want to change the
    order.



    Thanks,
    Bernhard

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2007-08-16 11:47    [W:2.886 / U:0.172 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site