From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [Qemu-devel] KVM call agenda for tuesday 31 Date: Thu, 09 Feb 2012 16:37:04 -0600 Message-ID: <4F344A90.6020705@codemonkey.ws> References: <87ehuhrpel.fsf@elfo.elfo> <4F272A92.2010609@suse.de> <4F272D8C.8020608@codemonkey.ws> <4F27E98E.2080501@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= , KVM devel mailing list , Mitsyanko Igor , Developers qemu-devel , quintela@redhat.com To: Peter Maydell Return-path: Received: from mail-pz0-f46.google.com ([209.85.210.46]:56031 "EHLO mail-pz0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758415Ab2BIWhJ (ORCPT ); Thu, 9 Feb 2012 17:37:09 -0500 Received: by daed14 with SMTP id d14so1836817dae.19 for ; Thu, 09 Feb 2012 14:37:08 -0800 (PST) In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 02/09/2012 04:23 PM, Peter Maydell wrote: > Ping re the VMState and variable sized arrays issue. I don't > see any consensus in this discussion for a different approach, > so should we just commit Mitsyanko's patchset? I don't know if I mentioned this, but do we really need variable sizes? Can we just use a fixed size (pre-allocated) array and then use a VMSTA= TE_SUB_ARRAY? If it's truly variable size with no upper bound, then that's actually a= security=20 problem since it implies a guest can do unbounded memory allocation. Regards, Anthony Liguori > > - PMM > > On 31 January 2012 13:15, Andreas F=C3=A4rber wrot= e: >> Am 31.01.2012 00:53, schrieb Anthony Liguori: >>> On 01/30/2012 05:41 PM, Andreas F=C3=A4rber wrote: >>>> Am 30.01.2012 19:55, schrieb Juan Quintela: >>>>> Please send in any agenda items you are interested in covering. >> >>>> VMState: >>>> Anthony specifically said that VMState were not affected by QOM an= d that >>>> patches should not be deferred until the merge. Yet there's no rev= iew >>>> and/or decision-making for a month now. Ping^2 for AHCI+SDHC. >>> >>> Do you have pointers (to pending VMState patches)? >> >> http://patchwork.ozlabs.org/patch/137732/ (PATCH v4) >> >> It's basically about how to deal with variable-sized arrays. (Alex >> mentioned it on one call around November.) I found ways to deal with >> subsets of arrays embedded within the struct and variable-sized list= of >> pointers to structs but no solution for a malloc()'ed array of struc= ts. >> Maybe I'm just too stupid to see. Anyway, no one commented since Xma= s. >> >> Igor posted (and refined for v2) a patch with a callback-based appro= ach >> that I find promising. From my view, unofficially Juan is the VMStat= e >> guy, he's been cc'ed. Are we lacking an official maintainer that car= es? >> Or is Juan the official, undocumented maintainer but simply busy? >> >> SUSE's interest is making AHCI migratable, and my VMState workaround= for >> that is simply ugly: >> >> http://patchwork.ozlabs.org/patch/133066/ (RFC) >> >> Therefore I'm waiting for some resolution. >> >> Regards, >> Andreas >