From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:35088) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rrt0J-0007Fl-Op for qemu-devel@nongnu.org; Mon, 30 Jan 2012 10:18:54 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Rrt0D-0002VE-Dm for qemu-devel@nongnu.org; Mon, 30 Jan 2012 10:18:47 -0500 Received: from mx1.redhat.com ([209.132.183.28]:3124) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rrt0D-0002V8-0P for qemu-devel@nongnu.org; Mon, 30 Jan 2012 10:18:41 -0500 Message-ID: <4F26B4C5.1080002@redhat.com> Date: Mon, 30 Jan 2012 16:18:29 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <1327927984-7884-1-git-send-email-pbonzini@redhat.com> <4F269D96.8000106@codemonkey.ws> <4F26A31D.7030704@redhat.com> <4F26A924.20900@codemonkey.ws> In-Reply-To: <4F26A924.20900@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC PATCH] generalize QOM path resolution List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: qemu-devel@nongnu.org On 01/30/2012 03:28 PM, Anthony Liguori wrote: >> >> You are not going to have anyway a link. That makes it fine to >> resolve a >> link and a link according to different rules. > > I think we agreed (in IRC) that we can handle this by changing > qdev_resolve_path() to take an optional TYPE argument which will cause > qdev_resolve_path() to only succeed if the resulting object implements > TYPE. > > This can be used to disambiguate partial path matches such that a > link property would only attempt to do partial path > resolutions on objects that have BlockDriverState in their parent > hierarchy. Yes. Paolo