From: "Andreas Färber" <afaerber@suse.de>
To: quintela@redhat.com
Cc: Eduardo Habkost <ehabkost@redhat.com>,
KVM devel mailing list <kvm@vger.kernel.org>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>,
Anthony Liguori <anthony@codemonkey.ws>,
Paolo Bonzini <pbonzini@redhat.com>,
Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Qemu-devel] KVM call agenda for 2013-07-09
Date: Mon, 08 Jul 2013 02:42:32 +0200 [thread overview]
Message-ID: <51DA0AF8.8070905@suse.de> (raw)
In-Reply-To: <8761wmc6g7.fsf@elfo.elfo>
Am 08.07.2013 01:10, schrieb Juan Quintela:
> Please, send any topic that you are interested in covering.
Static qdev vs. dynamic QOM properties and -global
(Igor's topic from two weeks ago that we couldn't cover any more)
=> needed for X86CPU subclasses (hot-add, topology, NUMA, ...)
Thanks,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-07-08 0:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-07 23:10 [Qemu-devel] KVM call agenda for 2013-07-09 Juan Quintela
2013-07-08 0:42 ` Andreas Färber [this message]
2013-07-09 13:30 ` 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=51DA0AF8.8070905@suse.de \
--to=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).