linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: chenfan <chen.fan.fnst@cn.fujitsu.com>
To: linux-hotplug@vger.kernel.org
Subject: a problem of preparing before cpu hot remove
Date: Wed, 31 Jul 2013 03:56:27 +0000	[thread overview]
Message-ID: <1375242987.26515.72.camel@localhost.localdomain> (raw)

Hi All,

Recently, I'm implementing cpu hot-remove for QEMU. I has a question
that there is no chance for applications to prepare vcpu-hotremove
before cpu down. 
For example, if user specify cpu-pin for some applications, and its cpu
is removed, there is no notification to udev for preparing to do some
repin before cpu down. the applications would not change setting before
cpu down.

I want to know that whether there is a scenario that can notify the
applications for preparing before cpu down. and if preparing fails, I
want the cpu remove failure.

Thanks,
Chen


             reply	other threads:[~2013-07-31  3:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-31  3:56 chenfan [this message]
2013-07-31  4:06 ` a problem of preparing before cpu hot remove Greg KH

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=1375242987.26515.72.camel@localhost.localdomain \
    --to=chen.fan.fnst@cn.fujitsu.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 read-only IMAP folder(s) and NNTP newsgroup(s).