All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Wim Van Sebroeck <wim@iguana.be>
Cc: Don Zickus <dzickus@redhat.com>,
	linux-watchdog@vger.kernel.org, kexec@lists.infradead.org,
	LKML <linux-kernel@vger.kernel.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	dyoung@redhat.com, vgoyal@redhat.com
Subject: Re: [PATCH v3] watchdog: Add hook for kicking in kdump path
Date: Mon, 27 May 2013 18:10:47 -0700	[thread overview]
Message-ID: <20130528011047.GA28597@roeck-us.net> (raw)
In-Reply-To: <20130527191618.GD14258@spo001.leaseweb.com>

On Mon, May 27, 2013 at 09:16:18PM +0200, Wim Van Sebroeck wrote:
>  Hi Guenter,
> 
> > > Hi Guenter,
> > > 
> > > Is there an easy way to determine which driver is loaded for each
> > > /dev/watchdogN device (from a script perspective).
> > > 
> > > Basically, I wanted to determine the module that needs to be included in
> > > the kdump initrd image.
> > > 
> > Sometimes. For example, the iTCO_wdt driver has an entry in /sys/devices, and
> > /sys/class/watchdog/watchdogX/device points to it. That is not always the case,
> > howewver. In my system, for example, the MEI watchdog is active, but there is
> > nothing I can find that would give me an indication that /dev/watchdog0 actually
> > points to the MEI watchdog driver.
> > 
> > Of course I might be missing something, and there might be some other means
> > to identify the driver from userspace. Would be great, actually, as I am having
> > the same problem.
> 
> Only when you set the .parent field in the watchdog_device data you will get the
> referal in the /sys/class/... tree. In iTCO_wdt.c you have the following code
> that does that: iTCO_wdt_watchdog_dev.parent = dev->dev.parent;
> 
> From the watchdog-kernel-api documentation:
> * parent: set this to the parent device (or NULL) before calling
>   watchdog_register_device.
> 
Hi Wim,

We live and learn ... thanks a lot for the hint!

Guenter

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: Guenter Roeck <linux@roeck-us.net>
To: Wim Van Sebroeck <wim@iguana.be>
Cc: Don Zickus <dzickus@redhat.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	linux-watchdog@vger.kernel.org, kexec@lists.infradead.org,
	LKML <linux-kernel@vger.kernel.org>,
	vgoyal@redhat.com, dyoung@redhat.com
Subject: Re: [PATCH v3] watchdog: Add hook for kicking in kdump path
Date: Mon, 27 May 2013 18:10:47 -0700	[thread overview]
Message-ID: <20130528011047.GA28597@roeck-us.net> (raw)
In-Reply-To: <20130527191618.GD14258@spo001.leaseweb.com>

On Mon, May 27, 2013 at 09:16:18PM +0200, Wim Van Sebroeck wrote:
>  Hi Guenter,
> 
> > > Hi Guenter,
> > > 
> > > Is there an easy way to determine which driver is loaded for each
> > > /dev/watchdogN device (from a script perspective).
> > > 
> > > Basically, I wanted to determine the module that needs to be included in
> > > the kdump initrd image.
> > > 
> > Sometimes. For example, the iTCO_wdt driver has an entry in /sys/devices, and
> > /sys/class/watchdog/watchdogX/device points to it. That is not always the case,
> > howewver. In my system, for example, the MEI watchdog is active, but there is
> > nothing I can find that would give me an indication that /dev/watchdog0 actually
> > points to the MEI watchdog driver.
> > 
> > Of course I might be missing something, and there might be some other means
> > to identify the driver from userspace. Would be great, actually, as I am having
> > the same problem.
> 
> Only when you set the .parent field in the watchdog_device data you will get the
> referal in the /sys/class/... tree. In iTCO_wdt.c you have the following code
> that does that: iTCO_wdt_watchdog_dev.parent = dev->dev.parent;
> 
> From the watchdog-kernel-api documentation:
> * parent: set this to the parent device (or NULL) before calling
>   watchdog_register_device.
> 
Hi Wim,

We live and learn ... thanks a lot for the hint!

Guenter

  reply	other threads:[~2013-05-28  1:10 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-17 21:19 [PATCH v3] watchdog: Add hook for kicking in kdump path Don Zickus
2013-04-17 21:19 ` Don Zickus
2013-04-17 21:33 ` Guenter Roeck
2013-04-17 21:33   ` Guenter Roeck
2013-04-17 21:49 ` Eric W. Biederman
2013-04-17 21:49   ` Eric W. Biederman
2013-04-18  3:03   ` Guenter Roeck
2013-04-18  3:03     ` Guenter Roeck
2013-04-18 13:00   ` Don Zickus
2013-04-18 13:00     ` Don Zickus
2013-04-18 13:49     ` Guenter Roeck
2013-04-18 13:49       ` Guenter Roeck
2013-04-18 13:52       ` Don Zickus
2013-04-18 13:52         ` Don Zickus
2013-04-18 14:54         ` Guenter Roeck
2013-04-18 14:54           ` Guenter Roeck
2013-04-24 14:42           ` Don Zickus
2013-04-24 14:42             ` Don Zickus
2013-04-24 15:21             ` Guenter Roeck
2013-04-24 15:21               ` Guenter Roeck
2013-05-27 19:16               ` Wim Van Sebroeck
2013-05-28  1:10                 ` Guenter Roeck [this message]
2013-05-28  1:10                   ` Guenter Roeck
2013-05-30 20:37                   ` Wim Van Sebroeck
2013-05-28 15:34                 ` Guenter Roeck
2013-05-28 15:34                   ` Guenter Roeck
2013-05-30 21:54                   ` Wim Van Sebroeck
2013-04-18 16:35 ` Eric W. Biederman
2013-04-18 16:35   ` Eric W. Biederman
2013-04-18 17:44   ` Don Zickus
2013-04-18 17:44     ` Don Zickus
2013-04-18 18:09     ` Eric W. Biederman
2013-04-18 18:09       ` Eric W. Biederman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130528011047.GA28597@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=dyoung@redhat.com \
    --cc=dzickus@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=vgoyal@redhat.com \
    --cc=wim@iguana.be \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.