From: "Greg KH (gregkh@linuxfoundation.org)" <gregkh@linuxfoundation.org>
To: "R, Durgadoss" <durgadoss.r@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Linux PM list (linux-pm@vger.kernel.org)"
<linux-pm@vger.kernel.org>,
"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>
Subject: Re: Kobject_uevent in cpufreq.c
Date: Mon, 13 May 2013 04:58:01 -0700 [thread overview]
Message-ID: <20130513115801.GA11433@kroah.com> (raw)
In-Reply-To: <4D68720C2E767A4AA6A8796D42C8EB59C8D667@BGSMSX101.gar.corp.intel.com>
On Mon, May 13, 2013 at 11:31:57AM +0000, R, Durgadoss wrote:
> Hi,
>
> I am observing an UEvent issue in cpufreq.c.
> The cpufreq_add_dev() function is called whenever a core is 'onlined'.
> we expect the kobject_uevent() method in cpufreq_add_dev() to
> send an UEvent with KOBJ_ADD as the action parameter.
>
> But this call fails because of the 'filter function' inside kobject_uevent_env
> inside lib/kobject_uevent.c. The ->filter points to 'dev_uevent_filter' in
> drivers/base/core.c, where the check for 'device_ktype' fails.
>
> Error message:
> kobject: 'cpufreq' (e5bbf290): kobject_uevent_env:
> filter function caused the event to drop!
>
> As far as I can see, we need a kset, and associated filter function
> inside cpufreq.c to get this working. Is this the right way to go ?
> Any other easy/correct ways to get it working ? Please advise.
What exactly are you trying to do, and want the kernel to do? You
already get on/offline events for CPUs, why do you want them for cpufreq
devices as well?
thanks,
greg k-h
next prev parent reply other threads:[~2013-05-13 11:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 11:31 Kobject_uevent in cpufreq.c R, Durgadoss
2013-05-13 11:58 ` Greg KH (gregkh@linuxfoundation.org) [this message]
2013-05-13 16:08 ` R, Durgadoss
2013-05-14 14:50 ` Greg KH (gregkh@linuxfoundation.org)
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=20130513115801.GA11433@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=durgadoss.r@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox