public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Vivek Goyal <vgoyal@redhat.com>,
	Michael Holzheu <holzheu@linux.vnet.ibm.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	schwidefsky@de.ibm.com, kexec@lists.infradead.org,
	linux-kernel@vger.kernel.org, Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: kdump: No udev events for memory hotplug?
Date: Thu, 27 Oct 2011 05:45:33 -0700	[thread overview]
Message-ID: <1319719533.23600.55.camel@nimitz> (raw)
In-Reply-To: <20111027073058.GA2422@osiris.boeblingen.de.ibm.com>

On Thu, 2011-10-27 at 09:30 +0200, Heiko Carstens wrote:
> > Are any events generated for memory add?
> 
> Looks like uevents are only genereted when memory gets registered and
> unregistered, but not when when it gets set online or offline.
> To achieve that you would need to add similar code to
> store_mem_state()/memory_block_change_state() in drivers/base/memory.c
> like we have it already in store_online() in drivers/base/cpu.c 

Instead of doing it at that low a level, perhaps we should be generating
events when 'totalram_pages' changes.  That way, we'll also trigger
events when things like ballooning happen.

-- Dave


  parent reply	other threads:[~2011-10-27 12:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-26 16:08 kdump: No udev events for memory hotplug? Michael Holzheu
2011-10-26 19:24 ` Vivek Goyal
2011-10-27  7:30   ` Heiko Carstens
2011-10-27  9:32     ` [PATCH] kdump: Add udev events for memory online/offline Michael Holzheu
2011-10-28 22:41       ` Andrew Morton
2011-10-28 22:57         ` Dave Hansen
2011-10-28 22:46       ` Andrew Morton
2011-10-31 13:21         ` [PATCH v2] " Michael Holzheu
2011-11-14  2:37           ` WANG Cong
2011-10-27 12:45     ` Dave Hansen [this message]
2011-10-27 13:18       ` kdump: No udev events for memory hotplug? Américo Wang
2011-10-27  7:45 ` Américo Wang

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=1319719533.23600.55.camel@nimitz \
    --to=haveblue@us.ibm.com \
    --cc=ebiederm@xmission.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=holzheu@linux.vnet.ibm.com \
    --cc=kay.sievers@vrfy.org \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=vgoyal@redhat.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