From: Juan Quintela <quintela@redhat.com>
To: KVM devel mailing list <kvm@vger.kernel.org>, qemu-devel@nongnu.org
Subject: [Qemu-devel] KVM call minutes for Tuesday, August 28th
Date: Tue, 28 Aug 2012 16:28:09 +0200 [thread overview]
Message-ID: <87k3wjf5vq.fsf@elfo.mitica> (raw)
Hi
As almost everybody was at LinuxCon, we only started talking about the
cpu patches from Eduardo and decided to left things for the list/next
week.
- cpu patches until 1.2
* get a new tree somewhere
- 1.3 discussion will wait until 1.2 is out
people too busy right now
- Remember than KVM Forum abstracts deadline is this Friday (August
31th)
Thanks, Juan.
This were the topics asked from Eduardo:
- *-user and qdev (recent RFCs didn't get many comments in the list, and
I don't see a conclusion);
- 1.2 branching, or creation of a "cpu-next" tree where "good to be
merged" patches can live until 1.2 is done;
- CPU code roadmap[1].
[1] For reference, this is the list of pending work that I want to
target for 1.3:
- -cpu help fix
- CPU DeviceState
- move CPU models to C
- kill cpudef
- unduplicate feature names
- CPU properties
- CPU model classes
- Fix -cpu host to use GET_SUPPORTED_CPUID properly
- Fix -cpu check/enforce brokenness
(including lots of refactoring of the currently-broken feature-flag
checking code)
- APIC ID threads/cores topology fix
Thanks, Juan.
reply other threads:[~2012-08-28 14:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87k3wjf5vq.fsf@elfo.mitica \
--to=quintela@redhat.com \
--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 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).