From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony PERARD Subject: Re: [PATCH 2/2] libxl: Have flexarray using the GC Date: Mon, 1 Oct 2012 15:23:43 +0100 Message-ID: <5069A76F.8040901@citrix.com> References: <1348666294-18182-1-git-send-email-anthony.perard@citrix.com> <1348666294-18182-3-git-send-email-anthony.perard@citrix.com> <20581.56805.294140.556698@mariner.uk.xensource.com> <5069A56B.4000605@citrix.com> <20585.42493.151224.551455@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20585.42493.151224.551455@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Jackson Cc: Ian Campbell , Xen Devel List-Id: xen-devel@lists.xenproject.org On 10/01/2012 03:17 PM, Ian Jackson wrote: > Anthony PERARD writes ("Re: [Xen-devel] [PATCH 2/2] libxl: Have flexarray using the GC"): >> > On 09/28/2012 06:27 PM, Ian Jackson wrote: >>> > > If gc is NOGC then this does the wrong thing. Callers should be able >>> > > to specify NOGC for a flexarray which they want to survive across >>> > > multiple calls into libxl. >> > >> > I'm not sure I see your point here. If a something needs a NOGC'ed >> > flexarray, then flexarray_make(NOGC, x, x) will give this. > So then you put the flexarray in some long-term data structure, which > survives the call to libxl and therefore the gc. Is it safe for > NOGC's gc*, derived from the now-destroyed actual gc, to be embedded > in the flexarray and reused later in a different libxl call with a > different gc (but the same ctx) ? Ah, I now see the issue, a pointer that lead nowhere :S. Thanks, -- Anthony PERARD