linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Regarding to CPU hotplug
Date: Mon, 10 Sep 2007 07:13:15 +0000	[thread overview]
Message-ID: <20070910071315.GA5367@kroah.com> (raw)
In-Reply-To: <OF1E936790.FCEE2367-ON65257352.001D2EE5-65257352.001D2710@in.ibm.com>

On Mon, Sep 10, 2007 at 10:49:52AM +0530, Omprakash Vishnoi wrote:
> 
>  Hi All,
>        I read the doc. Linux Symposium "Udev-A userspace implementation of
> devfs",there i understood,i have to make   rulefile in "/etc/udev/rule.d/"
> for CPU  hotplug,but how can i know which CPU getting add or
> removed.Acctually       as in my project,we want notification for CPU's
> getting remove or add at user  level.
> 
>       pls tell me what procedure i have to follow,And how can i know which
> CPU getting remove or add.

I think you can just listen for the dbus events coming from HAL that
show the cpus going up and down.  Have you tried looking at the events
that happen when you do this to the machine?

thanks,

greg k-h

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  reply	other threads:[~2007-09-10  7:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-10  5:31 Regarding to CPU hotplug Omprakash Vishnoi
2007-09-10  7:13 ` Greg KH [this message]
2007-09-10  8:36 ` Omprakash Vishnoi
2007-09-10 14:08 ` Greg KH
2007-09-10 22:46 ` Kay Sievers

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=20070910071315.GA5367@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-hotplug@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).