Add UEFI_VARS config option, enable by default for x86_64 and aarch64.

Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Message-ID: <20250225163031.1409078-17-kraxel@redhat.com>
---
 hw/Kconfig      | 1 +
 hw/uefi/Kconfig | 3 +++
 2 files changed, 4 insertions(+)
 create mode 100644 hw/uefi/Kconfig

diff --git a/hw/Kconfig b/hw/Kconfig
index 1b4e9bb07f7d..c4dfe2e7af7c 100644
--- a/hw/Kconfig
+++ b/hw/Kconfig
@@ -37,6 +37,7 @@ source smbios/Kconfig
 source ssi/Kconfig
 source timer/Kconfig
 source tpm/Kconfig
+source uefi/Kconfig
 source ufs/Kconfig
 source usb/Kconfig
 source virtio/Kconfig
diff --git a/hw/uefi/Kconfig b/hw/uefi/Kconfig
new file mode 100644
index 000000000000..ca6c2bc46a96
--- /dev/null
+++ b/hw/uefi/Kconfig
@@ -0,0 +1,3 @@
+config UEFI_VARS
+	bool
+        default y if X86_64 || AARCH64
-- 
2.48.1

On Tue, Mar 04, 2025 at 01:48:04PM +0100, Gerd Hoffmann wrote:
> Add UEFI_VARS config option, enable by default for x86_64 and aarch64.
> 
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> Message-ID: <20250225163031.1409078-17-kraxel@redhat.com>
> ---
>  hw/Kconfig      | 1 +
>  hw/uefi/Kconfig | 3 +++
>  2 files changed, 4 insertions(+)
>  create mode 100644 hw/uefi/Kconfig
> 
> diff --git a/hw/Kconfig b/hw/Kconfig
> index 1b4e9bb07f7d..c4dfe2e7af7c 100644
> --- a/hw/Kconfig
> +++ b/hw/Kconfig
> @@ -37,6 +37,7 @@ source smbios/Kconfig
>  source ssi/Kconfig
>  source timer/Kconfig
>  source tpm/Kconfig
> +source uefi/Kconfig
>  source ufs/Kconfig
>  source usb/Kconfig
>  source virtio/Kconfig
> diff --git a/hw/uefi/Kconfig b/hw/uefi/Kconfig
> new file mode 100644
> index 000000000000..ca6c2bc46a96
> --- /dev/null
> +++ b/hw/uefi/Kconfig
> @@ -0,0 +1,3 @@
> +config UEFI_VARS
> +	bool
> +        default y if X86_64 || AARCH64

RSICV64 uses UEFI too, is something extra needed before it can be
enabled there too, as it would be desirable to introduce it on all
UEFI targets concurrently.

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

On 19/3/25 12:27, Daniel P. Berrangé wrote:
> On Tue, Mar 04, 2025 at 01:48:04PM +0100, Gerd Hoffmann wrote:
>> Add UEFI_VARS config option, enable by default for x86_64 and aarch64.
>>
>> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
>> Message-ID: <20250225163031.1409078-17-kraxel@redhat.com>
>> ---
>>   hw/Kconfig      | 1 +
>>   hw/uefi/Kconfig | 3 +++
>>   2 files changed, 4 insertions(+)
>>   create mode 100644 hw/uefi/Kconfig
>>
>> diff --git a/hw/Kconfig b/hw/Kconfig
>> index 1b4e9bb07f7d..c4dfe2e7af7c 100644
>> --- a/hw/Kconfig
>> +++ b/hw/Kconfig
>> @@ -37,6 +37,7 @@ source smbios/Kconfig
>>   source ssi/Kconfig
>>   source timer/Kconfig
>>   source tpm/Kconfig
>> +source uefi/Kconfig
>>   source ufs/Kconfig
>>   source usb/Kconfig
>>   source virtio/Kconfig
>> diff --git a/hw/uefi/Kconfig b/hw/uefi/Kconfig
>> new file mode 100644
>> index 000000000000..ca6c2bc46a96
>> --- /dev/null
>> +++ b/hw/uefi/Kconfig
>> @@ -0,0 +1,3 @@
>> +config UEFI_VARS
>> +	bool
>> +        default y if X86_64 || AARCH64
> 
> RSICV64 uses UEFI too,

and LoongArch IIRC.

> is something extra needed before it can be
> enabled there too, as it would be desirable to introduce it on all
> UEFI targets concurrently.
> 
> With regards,
> Daniel

On Wed, Mar 19, 2025 at 11:27:41AM +0000, Daniel P. Berrangé wrote:
> On Tue, Mar 04, 2025 at 01:48:04PM +0100, Gerd Hoffmann wrote:
> > diff --git a/hw/uefi/Kconfig b/hw/uefi/Kconfig
> > new file mode 100644
> > index 000000000000..ca6c2bc46a96
> > --- /dev/null
> > +++ b/hw/uefi/Kconfig
> > @@ -0,0 +1,3 @@
> > +config UEFI_VARS
> > +	bool
> > +        default y if X86_64 || AARCH64
> 
> RSICV64 uses UEFI too, is something extra needed before it can be
> enabled there too, as it would be desirable to introduce it on all
> UEFI targets concurrently.

Assuming riscv has a platform bus too a riscv version of patch #21
should do.  Also some work on the firmware side, but that can happen
independent from the qemu changes.

take care,
  Gerd