From mboxrd@z Thu Jan  1 00:00:00 1970
From: Juan Quintela <quintela@redhat.com>
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 <qemu-devel@nongnu.org>, KVM devel mailing list
	<kvm@vger.kernel.org>, Andreas =?utf-8?Q?F=C3=A4rber?= <afaerber@suse.de>
Return-path: <qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=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.