From: Glauber de Oliveira Costa <gcosta-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org,
virtualization-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
marcelot-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: [PATCH/RFC 0/2] CPU hotplug virtio driver
Date: Wed, 9 Jan 2008 08:21:04 -0200 [thread overview]
Message-ID: <11998740663306-git-send-email-gcosta@redhat.com> (raw)
I'm sending a first draft of my proposed cpu hotplug driver for kvm/virtio
The first patch is the kernel module, while the second, the userspace pci device.
The host boots with the maximum cpus it should ever use, through the -smp parameter.
Due to real machine constraints (which qemu copies), i386 does not allow for any addition
of cpus after boot, so this is the most general way.
I do however, include an "attempt_buffer" in the userspace part. It's purpose is to
allow tools like virt-manager to set a max_cpus (-smp), and a desired number of cpus
in their configuration files. (and AFAICT, there's is no easy way for them to tell when the
backend driver is up and running)
Other than that, it should be pretty much straightforward.
Looking forward for your comments
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
next reply other threads:[~2008-01-09 10:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 10:21 Glauber de Oliveira Costa [this message]
2008-01-09 10:21 ` [PATCH] cpu hotplug driver: kernel module Glauber de Oliveira Costa
2008-01-09 10:42 ` [kvm-devel] [PATCH/RFC 0/2] CPU hotplug virtio driver Avi Kivity
[not found] ` <11998740663306-git-send-email-gcosta-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2008-01-09 10:21 ` [PATCH] cpu hotplug driver: kernel module Glauber de Oliveira Costa
2008-01-09 10:21 ` [PATCH] cpu hotplug driver: userspace back end Glauber de Oliveira Costa
[not found] ` <11998740731943-git-send-email-gcosta-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2008-01-09 10:21 ` Glauber de Oliveira Costa
2008-01-09 10:42 ` [PATCH/RFC 0/2] CPU hotplug virtio driver Avi Kivity
2008-01-09 14:12 ` [kvm-devel] " Glauber de Oliveira Costa
[not found] ` <4784A50E.6050302-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-09 14:12 ` Glauber de Oliveira Costa
2008-01-09 11:27 ` Christian Borntraeger
2008-01-09 14:21 ` [kvm-devel] " Glauber de Oliveira Costa
[not found] ` <4784D882.1030104-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2008-01-09 14:37 ` Avi Kivity
[not found] ` <4784DC29.1020907-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-22 4:11 ` Dong, Eddie
2008-01-22 4:11 ` [kvm-devel] " Dong, Eddie
2008-01-09 14:37 ` Avi Kivity
2008-01-09 11:27 ` Christian Borntraeger
-- strict thread matches above, loose matches on Subject: below --
2008-01-09 10:21 Glauber de Oliveira Costa
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=11998740663306-git-send-email-gcosta@redhat.com \
--to=gcosta-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=marcelot-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=virtualization-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.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.