[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 6/6] pc_sysfw: change rom_only default to 0
From: |
Markus Armbruster |
Subject: |
Re: [Qemu-devel] [PATCH 6/6] pc_sysfw: change rom_only default to 0 |
Date: |
Mon, 29 Apr 2013 16:00:02 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.1 (gnu/linux) |
Jordan Justen <address@hidden> writes:
> Now KVM can support a flash memory. This feature depends on
> KVM_CAP_READONLY_MEM, which was introduced in Linux 3.7.
>
> Signed-off-by: Jordan Justen <address@hidden>
> ---
> hw/block/pc_sysfw.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/block/pc_sysfw.c b/hw/block/pc_sysfw.c
> index e88d67e..c5067c1 100644
> --- a/hw/block/pc_sysfw.c
> +++ b/hw/block/pc_sysfw.c
> @@ -258,7 +258,7 @@ void pc_system_firmware_init(MemoryRegion *rom_memory)
> }
>
> static Property pcsysfw_properties[] = {
> - DEFINE_PROP_UINT8("rom_only", PcSysFwDevice, rom_only, 1),
> + DEFINE_PROP_UINT8("rom_only", PcSysFwDevice, rom_only, 0),
> DEFINE_PROP_END_OF_LIST(),
> };
Do we still need the pc-sysfw.rom_only entry in include/hw/i386/pc.h
PC_COMPAT_1_4?
- [Qemu-devel] [PATCH 3/6] kvm: workaround a possible KVM bug when using KVM_MEM_READONLY, (continued)
Re: [Qemu-devel] [PATCH 6/6] pc_sysfw: change rom_only default to 0,
Markus Armbruster <=
[Qemu-devel] [PATCH 5/6] pc_sysfw: allow flash memory to be used with KVM, Jordan Justen, 2013/04/28
[Qemu-devel] [PATCH 2/6] kvm: support using KVM_MEM_READONLY flag for readonly regions, Jordan Justen, 2013/04/28