[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v2] vl.c: disallow command line fw cfg without o

From: Laszlo Ersek
Subject: Re: [Qemu-devel] [PATCH v2] vl.c: disallow command line fw cfg without opt/
Date: Thu, 17 Mar 2016 14:49:35 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0

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

Anyway, I agree that RFQDNs leave a few characters for the actual knob
names, and they are mostly unique.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]