From: Juan Quintela <quintela@redhat.com>
To: "qemu-devel qemu-devel" <qemu-devel@nongnu.org>,
"KVM devel mailing list" <kvm@vger.kernel.org>,
"Andreas Färber" <afaerber@suse.de>
Subject: Minutes for KVM call 2013-01-15
Date: Tue, 15 Jan 2013 17:16:51 +0100 [thread overview]
Message-ID: <874niito98.fsf@elfo.mitica> (raw)
* 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.
WARNING: multiple messages have this Message-ID (diff)
From: Juan Quintela <quintela@redhat.com>
To: "qemu-devel qemu-devel" <qemu-devel@nongnu.org>,
"KVM devel mailing list" <kvm@vger.kernel.org>,
"Andreas Färber" <afaerber@suse.de>
Subject: [Qemu-devel] Minutes for KVM call 2013-01-15
Date: Tue, 15 Jan 2013 17:16:51 +0100 [thread overview]
Message-ID: <874niito98.fsf@elfo.mitica> (raw)
* 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.
next reply other threads:[~2013-01-15 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 16:16 Juan Quintela [this message]
2013-01-15 16:16 ` [Qemu-devel] Minutes for KVM call 2013-01-15 Juan Quintela
2013-01-30 10:58 ` vCPU hotplug roadmap (was: Minutes for KVM call 2013-01-15) Andreas Färber
2013-01-30 12:49 ` Eduardo Habkost
2013-01-30 13:02 ` vCPU hotplug roadmap Andreas Färber
2013-01-30 13:18 ` Igor Mammedov
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=874niito98.fsf@elfo.mitica \
--to=quintela@redhat.com \
--cc=afaerber@suse.de \
--cc=kvm@vger.kernel.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.