From: Gleb Natapov <gleb@redhat.com>
To: Conrad Wood <linux-kvm@conradwood.net>
Cc: "Kevin O'Connor" <kevin@koconnor.net>, kvm@vger.kernel.org
Subject: Re: cpu hotplug
Date: Sun, 19 Sep 2010 17:19:16 +0200 [thread overview]
Message-ID: <20100919151916.GX3008@redhat.com> (raw)
In-Reply-To: <1284909384.9521.228.camel@frechmops.schnuffi.conrad.localdomain>
On Sun, Sep 19, 2010 at 05:16:24PM +0200, Conrad Wood wrote:
> [..]
>
> > Lets establish some terminology to understand each other better:
> > Lets use CPU inserted/ejected to refer to cpu being available/not
> > available to a guest.
> > Lest use CPU online/offline to refer to cpu been used by a guest OS.
> >
> > CPU hot-plug works like this:
> > cpu is inserted (plugged into cpu socket on MB)
> > guest OS is notifies through ACPI
> > guest OS starts to use newly added CPU (makes it online)
> >
> > CPU hot-unplug works like this:
> > guest OS is notifies through ACPI that cpu is going to be removed
> > guest OS stops to use cpu (makes it offline)
> > cpu is ejected (removed from a socket on MB) (kvm never does that part)
> >
> > So which part do you want to know about from a host?
> >
> > You can't really know from a host if cpu is used by guest OS (if it is
> > online/offline in s guest in our terminology)
> >
> > inserted/ejected is management action (it can't be initiated by a
> > guest), so you can keep track of it by yourself. KVM doesn't do it
> > for you right now. More precisely it does, but doesn't have a way to
> > quire it.
>
> I need to know if a cpu is currently inserted or ejected.
>
The only way to do that currently is to track it in your management app.
> I gather a cpu which is currently "inserted", may potentially be used by
> a guest os. (Wether he actually uses a cpu, puts it online or offline,
> isn't my concern).
>
> The amount of time and number of cpus available to a guest is what I
> like to keep track of.
>
> Conrad
>
--
Gleb.
next prev parent reply other threads:[~2010-09-19 15:19 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 [this message]
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
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=20100919151916.GX3008@redhat.com \
--to=gleb@redhat.com \
--cc=kevin@koconnor.net \
--cc=kvm@vger.kernel.org \
--cc=linux-kvm@conradwood.net \
/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).