From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eduardo Habkost Subject: Re: [Qemu-devel] KVM call agenda for Tuesda, August 28th Date: Tue, 28 Aug 2012 10:48:07 -0300 Message-ID: <20120828134807.GC6223@otherpad.lan.raisama.net> References: <87ipc4gd35.fsf@elfo.mitica> <20120828133028.GB6223@otherpad.lan.raisama.net> <87r4qrf7yi.fsf@elfo.mitica> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Igor Mammedov , qemu-devel@nongnu.org, KVM devel mailing list , Andreas =?iso-8859-1?Q?F=E4rber?= To: Juan Quintela Return-path: Received: from mx1.redhat.com ([209.132.183.28]:18267 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752877Ab2H1NrG (ORCPT ); Tue, 28 Aug 2012 09:47:06 -0400 Content-Disposition: inline In-Reply-To: <87r4qrf7yi.fsf@elfo.mitica> Sender: kvm-owner@vger.kernel.org List-ID: On Tue, Aug 28, 2012 at 03:43:17PM +0200, Juan Quintela wrote: > Eduardo Habkost 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"). No problem. We can try to get that discussed on the list, or wait until next week. -- Eduardo