From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53246) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1agYJ0-0005Bk-W8 for qemu-devel@nongnu.org; Thu, 17 Mar 2016 09:49:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1agYJ0-0008V8-5E for qemu-devel@nongnu.org; Thu, 17 Mar 2016 09:49:38 -0400 Received: from mx1.redhat.com ([209.132.183.28]:47415) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1agYJ0-0008V3-05 for qemu-devel@nongnu.org; Thu, 17 Mar 2016 09:49:38 -0400 References: <1458053080-29170-1-git-send-email-mst@redhat.com> <87fuvpv2jv.fsf@blackfin.pond.sub.org> <20160317143531-mutt-send-email-mst@redhat.com> <56EAB17A.1000400@redhat.com> From: Laszlo Ersek Message-ID: <56EAB5EF.40606@redhat.com> Date: Thu, 17 Mar 2016 14:49:35 +0100 MIME-Version: 1.0 In-Reply-To: <56EAB17A.1000400@redhat.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v2] vl.c: disallow command line fw cfg without opt/ List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini , "Michael S. Tsirkin" , Markus Armbruster Cc: "Gabriel L. Somlo" , qemu-devel@nongnu.org, Gerd Hoffmann On 03/17/16 14:30, Paolo Bonzini wrote: > On 17/03/2016 14:13, Michael S. Tsirkin wrote: >> OVMF: >> Can use the compatible opt/ovmf/ for now. [snip] >> Long term: Gradually transition OVMF to look up paths in usr/org.uefi/: >> if nothing is found there, look up in opt/ovmf/ for backwards >> compatibility. > > Agreed except it would be org.tianocore.edk2.ovmf/ rather than usr/org.uefi. > > Likewise SeaBIOS would switch from etc/ to an org.seabios/ prefix (for > stuff usable from both Coreboot and QEMU, e.g. > org.seabios/bootsplash.bmp) or org.qemu/ (for stuff that is specific to > QEMU). I think it's feasible (in the long term) to make OVMF look for "standard" fw_cfg files under "org.qemu/", and for the OVMF-specific knobs under "org.tianocore.edk2.ovmf/". (The longest knob name OVMF uses at the moment is 24 chars; it would fit.) It's just that I don't see how a user is any more likely to randomly pick "opt/ovmf/" for his own ad-hoc purposes than to pick "org.tianocore.edk2.ovmf/". Anyway, I agree that RFQDNs leave a few characters for the actual knob names, and they are mostly unique. Thanks Laszlo