From: Juan Quintela <quintela@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: "KVM devel mailing list" <kvm@vger.kernel.org>,
qemu-devel@nongnu.org, "Igor Mammedov" <imammedo@redhat.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: KVM call agenda for Tuesda, August 28th
Date: Tue, 28 Aug 2012 15:43:17 +0200 [thread overview]
Message-ID: <87r4qrf7yi.fsf@elfo.mitica> (raw)
In-Reply-To: <20120828133028.GB6223@otherpad.lan.raisama.net> (Eduardo Habkost's message of "Tue, 28 Aug 2012 10:30:28 -0300")
Eduardo Habkost <ehabkost@redhat.com> wrote:
> On Tue, Aug 28, 2012 at 12:54:54AM +0200, Juan Quintela wrote:
>>
>> Hi
>>
>> Please send in any agenda items you are interested in covering.
>
> - *-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
And I was about to cancel de call. Only problem is that I have been
told that lot of people is on San Diego, but we can try to see if there
is enough quorum (I didn't realize the San Diego "problem").
Later, Juan.
next prev parent reply other threads:[~2012-08-28 13:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 22:54 KVM call agenda for Tuesda, August 28th Juan Quintela
2012-08-28 13:30 ` Eduardo Habkost
2012-08-28 13:43 ` Juan Quintela [this message]
2012-08-28 13:48 ` [Qemu-devel] " Eduardo Habkost
2012-08-28 13:55 ` Peter Maydell
2012-08-28 14:27 ` [Qemu-devel] " Eduardo Habkost
2012-08-28 17:59 ` Andreas Färber
2012-08-28 18:03 ` Eduardo Habkost
2012-08-28 19:15 ` Anthony Liguori
2012-08-28 19:28 ` Eduardo Habkost
2012-08-28 19:59 ` [Qemu-devel] " Anthony Liguori
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=87r4qrf7yi.fsf@elfo.mitica \
--to=quintela@redhat.com \
--cc=afaerber@suse.de \
--cc=ehabkost@redhat.com \
--cc=imammedo@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).