mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Tim Hockin <thockin@hockin.org>
Cc: Nick Piggin <piggin@cyberone.com.au>,
	Rusty Russell <rusty@au1.ibm.com>,
	linux-kernel@vger.kernel.org, torvalds@osdl.org, akpm@osdl.org,
	rml@tech9.net
Subject: Re: CPU Hotplug: Hotplug Script And SIGPWR
Date: Thu, 22 Jan 2004 16:29:39 +1100	[thread overview]
Message-ID: <20040122071637.6C38D2C0F8@lists.samba.org> (raw)
In-Reply-To: Your message of "Tue, 20 Jan 2004 23:08:44 -0800." <20040121070844.GA31807@hockin.org>

In message <20040121070844.GA31807@hockin.org> you write:
> Process A has now discarded useful potentially VALUABLE information, with no
> way to retrieve it.  The hot plug scripts do not have enough information to
> put things the way they were before.  I can't believe that anyone considers
> this to be OK.

We already established that the process which cares has to listed to
hotplug events.

Userland should handle it *before* telling the kernel to remove the
CPU.  What we're dealing with here is merely a corner case, IMHO worth
neither hysteria nor a great deal of code.

Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

  parent reply	other threads:[~2004-01-22  7:16 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040116174446.A2820@in.ibm.com>
2004-01-20  5:44 ` Rusty Russell
2004-01-20  6:33   ` Tim Hockin
2004-01-20  6:43     ` Nick Piggin
2004-01-20  6:52       ` Tim Hockin
2004-01-20  7:11         ` Nick Piggin
2004-01-20  7:30           ` Tim Hockin
2004-01-20  7:45             ` Nick Piggin
2004-01-20  7:54               ` Tim Hockin
2004-01-20  8:14                 ` Nick Piggin
2004-01-20  8:29                   ` Tim Hockin
2004-01-20  8:37                     ` Nick Piggin
2004-01-20  8:43                       ` Tim Hockin
2004-01-21  4:06                         ` Srivatsa Vaddagiri
2004-01-21  4:14                           ` Nick Piggin
2004-01-21  5:09                             ` Srivatsa Vaddagiri
2004-01-21  7:08                               ` Tim Hockin
2004-01-21 15:07                                 ` Matthias Urlichs
2004-01-22  5:29                                 ` Rusty Russell [this message]
2004-01-21  7:09                             ` Tim Hockin
2004-01-21  7:31                               ` Nick Piggin
2004-01-21  7:42                                 ` Tim Hockin
2004-01-21  8:11                             ` Rusty Russell
2004-01-21  5:07                           ` Rusty Russell
2004-01-20  8:41                   ` Stefan Smietanowski
2004-01-20  8:49                     ` Nick Piggin
2004-01-20  9:12                       ` Tim Hockin
2004-01-21  0:00                 ` Rusty Russell
2004-01-20 23:51         ` Rusty Russell
2004-01-20  7:45     ` Rusty Russell
2004-01-20  8:37       ` Tim Hockin
2004-01-20  9:29         ` Srivatsa Vaddagiri
2004-01-21  0:12         ` Rusty Russell
     [not found] <fa.f37o48p.1io5q5@ifi.uio.no>
     [not found] ` <fa.frjqvfo.170g8hq@ifi.uio.no>
2004-01-20 17:49   ` Andy Lutomirski
2004-01-21  4:33     ` Rusty Russell

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=20040122071637.6C38D2C0F8@lists.samba.org \
    --to=rusty@rustcorp.com.au \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=piggin@cyberone.com.au \
    --cc=rml@tech9.net \
    --cc=rusty@au1.ibm.com \
    --cc=thockin@hockin.org \
    --cc=torvalds@osdl.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

Powered by JetHome