All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: "Christian Borntraeger" <borntraeger@de.ibm.com>,
	"qemu-develQEMU Developer" <qemu-devel@nongnu.org>,
	"KVM devel mailing list" <kvm@vger.kernel.org>,
	"Andreas Färber" <afaerber@suse.de>,
	"Bharata B Rao" <bharata@linux.vnet.ibm.com>,
	"Matthew Rosato" <mjrosato@linux.vnet.ibm.com>,
	"David Hildenbrand" <dahi@linux.vnet.ibm.com>,
	"David Gibson" <david@gibson.dropbear.id.au>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Paul Mackerras" <paulus@samba.org>
Subject: Re: KVM call for agenda for 2016-02-16
Date: Wed, 17 Feb 2016 23:51:47 +0100	[thread overview]
Message-ID: <87mvqz54sc.fsf@emacs.mitica> (raw)
In-Reply-To: <20160217204047.GD10796@thinpad.lan.raisama.net> (Eduardo Habkost's message of "Wed, 17 Feb 2016 18:40:47 -0200")

Eduardo Habkost <ehabkost@redhat.com> wrote:
> On Tue, Feb 16, 2016 at 12:54:57PM +0100, Christian Borntraeger wrote:
>> So my quick and dirty summary of CPU as _I_ understand it
>> (and I only have some part time bandwidth at the moment for that)
>> 
>> x86 has cpu hotplug. Some history
>> qemu-kvm had cpu_set in the past
>> qemu has cpu_add for a while now
>> libvirt code uses cpu_add cross-platform out of the box
>> 
>> proposal to use device_add. Currently this has the following issues that
>> we need to discuss:
>> - will require capability checking and dual code in libvirt (and libvirt updates)
>> - Power has some constraints that are hard to model with just device add
>> 	- David Gibson proposes a two layer interface
>> 		- low level: device add cpu-package
>> 		- high level
>> - David Hildenbrand has some concerns regarding CPU models (with base model + feature
>>   on/off), as device_add needs instantiatable type
>> - devel_del: s390 has no interface for cpu removal (Matts latest patches reset the 
>> machine just like z/VM - until we have some interface)
>> - anything else? (cpu hotplug on ARM or MIPS?)
>> 
>> Would be good to use todays call to have a plan how to finish things soon.
>> (maybe even for 2.6)
>
> Did the call happen? I am away from work for most days during the
> next 2 weeks, so I couldn't attend.

Yeap.  I sent some minutes, but they are kind of incoherent, I hope that
Andreas or Christian fill the holes...

Later, Juan.

  reply	other threads:[~2016-02-17 22:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10 15:42 KVH call for agenda for 2016-02-16 Juan Quintela
2016-02-10 15:48 ` Christian Borntraeger
2016-02-12 17:28   ` Andreas Färber
2016-02-16 11:54 ` KVM " Christian Borntraeger
2016-02-17 20:40   ` Eduardo Habkost
2016-02-17 22:51     ` Juan Quintela [this message]
2016-02-22 19:02       ` [Qemu-devel] " Thomas Huth
2016-02-23  9:59         ` Juan Quintela

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=87mvqz54sc.fsf@emacs.mitica \
    --to=quintela@redhat.com \
    --cc=afaerber@suse.de \
    --cc=bharata@linux.vnet.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=dahi@linux.vnet.ibm.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=ehabkost@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mjrosato@linux.vnet.ibm.com \
    --cc=paulus@samba.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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.