From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:34396) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZX4Ei-0004kW-WC for qemu-devel@nongnu.org; Wed, 02 Sep 2015 05:21:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZX4Ef-0001fV-1H for qemu-devel@nongnu.org; Wed, 02 Sep 2015 05:21:45 -0400 Received: from mx1.redhat.com ([209.132.183.28]:39821) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZX4Ee-0001fP-Rb for qemu-devel@nongnu.org; Wed, 02 Sep 2015 05:21:40 -0400 References: <1441012133-8154-1-git-send-email-markmb@redhat.com> <1441012217-8213-1-git-send-email-markmb@redhat.com> <1441012217-8213-2-git-send-email-markmb@redhat.com> <20150901174508.GD13375@HEDWIG.INI.CMU.EDU> <20150901191303.GE13375@HEDWIG.INI.CMU.EDU> <1441181329.10161.8.camel@redhat.com> From: Laszlo Ersek Message-ID: <55E6BFA1.8020402@redhat.com> Date: Wed, 2 Sep 2015 11:21:37 +0200 MIME-Version: 1.0 In-Reply-To: <1441181329.10161.8.camel@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v2 1/5] fw_cfg: document fw_cfg_modify_iXX() update functions List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann , Peter Maydell Cc: Drew , Stefan Hajnoczi , "Gabriel L. Somlo" , QEMU Developers , Kevin O'Connor , =?UTF-8?Q?Marc_Mar=c3=ad?= On 09/02/15 10:08, Gerd Hoffmann wrote: > On Di, 2015-09-01 at 21:10 +0100, Peter Maydell wrote: >> On 1 September 2015 at 20:13, Gabriel L. Somlo wrote: >>> Also, since I'll be tinkering with fw_cfg again, and you mentioned >>> using DT on arm and ACPI on x86 to auto-detect the presence (and location) >>> of fw_cfg from the guest-side in a related thread: >> >> I meant DT or ACPI on ARM, actually. I don't know what the x86 >> approach is for fw_cfg but I think it's just "known address". > > Yes, "known address". And given that the firmware actually loads the > acpi tables via fw_cfg that is very unlikely to change. Adding it to > the acpi tables might be useful nevertheless so the guest os knows the > ioports are in use. > > I think on arm the acpi situation is the same, but I think firmware > detecting the location via DT should work without chicken&egg problems. First of all I apologize for lagging severely behind this thread; in practice I can't read emails longer than 20 lines or so. This one qualifies, so I'll respond: Yes, on qemu-system-(arm|aarch64) -M virt, detecting the fw_cfg registers via DT should continue to work without any dependencies. Thanks Laszlo