From: Glauber de Oliveira Costa <gcosta@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
Marcelo Tosatti <marcelo@kvack.org>
Cc: kvm-devel@lists.sourceforge.net,
virtualization@lists.linux-foundation.org
Subject: Re: [kvm-devel] [PATCH/RFC 0/2] CPU hotplug virtio driver
Date: Wed, 09 Jan 2008 12:21:54 -0200 [thread overview]
Message-ID: <4784D882.1030104@redhat.com> (raw)
In-Reply-To: <200801091227.12261.borntraeger@de.ibm.com>
Christian Borntraeger wrote:
> Am Mittwoch, 9. Januar 2008 schrieb Glauber de Oliveira Costa:
>> 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.
>
> I personally prefer to use non paravirtualized cpu hotplug and implement the
> existing interfaces instead in the hypervisor. (sigp/sclp for s390 and
> maybe acpi for x86 etc.). This is not a performance critical operation.
>
>
> Christian
It's barely "paravirtualized". It's a device driver talking to a
hardware from the guest POV, not much different than acpi itself is, but
sanner. The only difference is that acpi support "already exists", but
virtio is a lot easier, and it wouldn't take long to write a driver like
that for windows or anything else (not that I am volunteering ;-)).
Also, in the future the interface can be extended in ways acpi can't
handle. (and just because nobody will change the hardware to embrace new
things that fast)
That said, if acpi is really the preference here, and this patches have
chance, no problem. But it will take me a little more time to implement
them ;-)
next prev parent reply other threads:[~2008-01-09 14:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 10:21 [PATCH/RFC 0/2] CPU hotplug virtio driver Glauber de Oliveira Costa
[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
[not found] ` <11998740731943-git-send-email-gcosta-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2008-01-09 10:21 ` [PATCH] cpu hotplug driver: userspace back end Glauber de Oliveira Costa
2008-01-09 10:42 ` [PATCH/RFC 0/2] CPU hotplug virtio driver Avi Kivity
[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 ` Glauber de Oliveira Costa [this message]
[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
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=4784D882.1030104@redhat.com \
--to=gcosta@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=marcelo@kvack.org \
--cc=virtualization@lists.linux-foundation.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