From mboxrd@z Thu Jan 1 00:00:00 1970 From: Juan Quintela Subject: Minutes for KVM call 2013-01-15 Date: Tue, 15 Jan 2013 17:16:51 +0100 Message-ID: <874niito98.fsf@elfo.mitica> Reply-To: quintela@redhat.com Mime-Version: 1.0 Content-Type: text/plain To: qemu-devel qemu-devel , KVM devel mailing list , Andreas =?utf-8?Q?F=C3=A4rber?= Return-path: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org List-Id: kvm.vger.kernel.org * cpu hot plug - use qdev propierties conected to a set of socket objects (anthony) - cpusets are the wrong interface (anthony) - make a link between cpu <-> socket instead of a propierty? - how far are we from being able to describe a cpu with -device? (didn't heare the answer, andreas?) - perhaps the best approach? - After soft-freeze, exceptions depend on the maintainer - After hard-freeze, no exceptions -device don't require a bus, just an implementation detail, we can change that - use cpuset as an intermediate step until full vision is implemented - several approaches from where we are now, to have something before we get a full solution At this point, Andreas agreed to write a better summary of the discussion and suggestions O:-) Later, Juan. From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:53222) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tv9C6-0004Re-Br for qemu-devel@nongnu.org; Tue, 15 Jan 2013 11:17:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Tv9C1-00046Z-Hi for qemu-devel@nongnu.org; Tue, 15 Jan 2013 11:16:58 -0500 Received: from mx1.redhat.com ([209.132.183.28]:43514) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tv9C1-00046O-Ad for qemu-devel@nongnu.org; Tue, 15 Jan 2013 11:16:53 -0500 From: Juan Quintela Date: Tue, 15 Jan 2013 17:16:51 +0100 Message-ID: <874niito98.fsf@elfo.mitica> MIME-Version: 1.0 Content-Type: text/plain Subject: [Qemu-devel] Minutes for KVM call 2013-01-15 Reply-To: quintela@redhat.com List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel qemu-devel , KVM devel mailing list , Andreas =?utf-8?Q?F=C3=A4rber?= * cpu hot plug - use qdev propierties conected to a set of socket objects (anthony) - cpusets are the wrong interface (anthony) - make a link between cpu <-> socket instead of a propierty? - how far are we from being able to describe a cpu with -device? (didn't heare the answer, andreas?) - perhaps the best approach? - After soft-freeze, exceptions depend on the maintainer - After hard-freeze, no exceptions -device don't require a bus, just an implementation detail, we can change that - use cpuset as an intermediate step until full vision is implemented - several approaches from where we are now, to have something before we get a full solution At this point, Andreas agreed to write a better summary of the discussion and suggestions O:-) Later, Juan.