All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: "Kevin O'Connor" <kevin@koconnor.net>
Cc: kvm@vger.kernel.org
Subject: Re: cpu hotplug
Date: Tue, 21 Sep 2010 08:42:57 +0200	[thread overview]
Message-ID: <20100921064257.GM3008@redhat.com> (raw)
In-Reply-To: <20100921010716.GD16648@morn.localdomain>

On Mon, Sep 20, 2010 at 09:07:16PM -0400, Kevin O'Connor wrote:
> On Mon, Sep 20, 2010 at 08:50:17AM +0200, Gleb Natapov wrote:
> > On Sun, Sep 19, 2010 at 06:03:31PM -0400, Kevin O'Connor wrote:
> > > I was wrong.  The "cpu_set x offline" does send an event to the guest
> > > OS.  SeaBIOS even forwards the event along - as far as I can tell a
> > > Notify(CPxx, 3) event is generated by SeaBIOS.
> > > 
> > > My Windows 7 ultimate beta seems to receive the event okay (it pops up
> > > a dialog box which says you can't unplug cpus).
> > > 
> > It may react to Eject() method.
> 
> The eject method is called by the OS to notify the host.  Right now
> SeaBIOS's eject method doesn't do anything.
> 
Yes. What I meant is it may react on presence of Eject() method. In my
experience Windows consider all devices with Eject() method as
hot-pluggable. But actually IIRC Windows 7 gave me this dialog box with
BOCHS BIOS too and there we didn't have Eject() method.

> > > Unfortunately, my test linux guest OS (FC13) doesn't seem to do
> > > anything with the unplug Notify event.  I've tried with the original
> > > FC13 and with a fully updated version - no luck.
> > > 
> > > So, I'm guessing this has something to do with the guest OS.
> > > 
> > Can you verify that _STA() return zero after cpu unplug?
> 
> I've verified that.  I've also verified that Linux doesn't call the
> _STA method after Notify(CPxx, 3).  It does call _STA on startup and
> after a Notify(CPxx, 1) event.  So, the Linux kernel in my FC13 guest
> just seems to be ignoring Notify(3) events.  (According to ACPI spec,
> the guest should shutdown the cpu and then call the eject method.)
> 
In older kernels _STA was called on Notify(3), but recently cpu hot-plug
in Linux was changed. Can you check what happens if you'll call
Notify(1) on unplug? Spec says that the value is:

 Device Check. Used to notify OSPM that the device either
 appeared or disappeared.

so may be it should be called on hot-plug and hot-unplug.

--
			Gleb.

  reply	other threads:[~2010-09-21  6:42 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-17 21:39 cpu hotplug Conrad Wood
2010-09-18 14:32 ` Kevin O'Connor
2010-09-18 15:14   ` Conrad Wood
2010-09-18 18:27   ` Conrad Wood
2010-09-19  6:38     ` Gleb Natapov
2010-09-19 10:41       ` Conrad Wood
2010-09-19 10:46         ` Gleb Natapov
2010-09-19 11:09           ` Conrad Wood
2010-09-19 11:13             ` Gleb Natapov
2010-09-19 11:32               ` Conrad Wood
2010-09-19 11:39                 ` Gleb Natapov
2010-09-19 11:51                   ` Conrad Wood
2010-09-19 11:59                     ` Gleb Natapov
2010-09-19 12:18                       ` Conrad Wood
2010-09-19 15:20                       ` Avi Kivity
2010-09-19 15:22                         ` Gleb Natapov
2010-09-19 13:26       ` Kevin O'Connor
2010-09-19 13:29         ` Conrad Wood
2010-09-19 13:31           ` Gleb Natapov
2010-09-19 13:35             ` Conrad Wood
2010-09-19 13:40               ` Gleb Natapov
2010-09-19 13:46                 ` Kevin O'Connor
2010-09-19 13:50                   ` Gleb Natapov
2010-09-19 14:07                     ` Conrad Wood
2010-09-19 14:14                       ` Kevin O'Connor
2010-09-19 14:36                       ` Gleb Natapov
2010-09-19 15:16                         ` Conrad Wood
2010-09-19 15:19                           ` Gleb Natapov
2010-09-19 15:37                             ` Conrad Wood
2010-09-19 15:41                               ` Gleb Natapov
2010-09-19 15:44                                 ` Conrad Wood
2010-09-19 15:53                                   ` Gleb Natapov
2010-09-19 16:04                                     ` Kevin O'Connor
2010-09-19 16:12                                       ` Gleb Natapov
2010-09-19 22:03                                         ` Kevin O'Connor
2010-09-20  6:50                                           ` Gleb Natapov
2010-09-21  1:07                                             ` Kevin O'Connor
2010-09-21  6:42                                               ` Gleb Natapov [this message]
2010-09-21  9:38                                               ` Gleb Natapov
2010-09-19 16:24                                       ` Conrad Wood
2010-09-19 21:57                                         ` Kevin O'Connor
2010-09-20  6:48                                           ` Gleb Natapov
2010-09-19 13:38           ` Kevin O'Connor
2010-09-19 13:39             ` Conrad Wood
  -- strict thread matches above, loose matches on Subject: below --
2017-01-01 10:03 CPU HOTPLUG Ozgur O Kilic

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=20100921064257.GM3008@redhat.com \
    --to=gleb@redhat.com \
    --cc=kevin@koconnor.net \
    --cc=kvm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.