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:41:14 +0200 [thread overview]
Message-ID: <20100919154113.GZ3008@redhat.com> (raw)
In-Reply-To: <1284910638.9521.242.camel@frechmops.schnuffi.conrad.localdomain>
On Sun, Sep 19, 2010 at 05:37:18PM +0200, Conrad Wood wrote:
>
> > > 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.
>
> The Management App does know which one should be inserted or ejected.
> I see now way of enforcing it though.
>
> This is what I had in mind: (simplified)
>
> 1. Management App increase cpus
> 2. kvm (as instructed by app): insert cpu x
> 3. guest os: online cpu x
> 4. do some stuff in the guest...
> 5. guest os: offline cpu x
> 6. Management App decrease cpus
> 7. kvm (as instructed by app): eject cpu x
>
> However after step 7 the guest can turn the cpu online again by issuing
> echo 1 >/sys/devices/.../cpuX/online
There will be no /sys/devices/.../cpuX/online in guest after step 7.
> If the guest does so, the Management App has no way of knowing and thus
> cannot provide accurate logs - that is why it is so important.
>
> Conrad
>
>
--
Gleb.
next prev parent reply other threads:[~2010-09-19 15:41 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 [this message]
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=20100919154113.GZ3008@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 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.