From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Brook Subject: Re: [Qemu-devel] [RFC PATCH 3/6] RAMBlock: Add a name field Date: Wed, 9 Jun 2010 15:09:01 +0100 Message-ID: <201006091509.01731.paul@codesourcery.com> References: <20100608191447.4451.47795.stgit@localhost.localdomain> <4C0F81F2.4030106@redhat.com> <4C0F9DD8.5000400@codemonkey.ws> Mime-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Cc: Avi Kivity , qemu-devel@nongnu.org, chrisw@redhat.com, Alex Williamson , kvm@vger.kernel.org, quintela@redhat.com To: Anthony Liguori Return-path: Received: from mail.codesourcery.com ([38.113.113.100]:40313 "EHLO mail.codesourcery.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753128Ab0FIOKB (ORCPT ); Wed, 9 Jun 2010 10:10:01 -0400 In-Reply-To: <4C0F9DD8.5000400@codemonkey.ws> Sender: kvm-owner@vger.kernel.org List-ID: > Keep in mind, this has to be a stable string across versions of qemu > since this is savevm/migration. Are we absolutely confident that the > full qdev path isn't going to change? I'm more confident that a unique > device name is going to be static across qemu versions. The actual representation of the device address is a secondary issue. The important point is that ram blocks should be associated with devices[*], and matched in exactly the same way. Devices should not be duplicating this on an ad-hoc basis. Paul [*] Ignore that we don't currently have a root system device node. A null device will suffice for now.