[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v3 0/4] SysFS driver for QEMU fw_cfg device
|
From: |
Paolo Bonzini |
|
Subject: |
Re: [Qemu-devel] [PATCH v3 0/4] SysFS driver for QEMU fw_cfg device |
|
Date: |
Mon, 5 Oct 2015 13:48:52 +0200 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 |
On 05/10/2015 12:00, Mark Rutland wrote:
> Some of the keys in the example look like they'd come from other sources
> (e.g. the *-tables entries), while others look like kernel/bootloader
> configuration options (e.g. etc/boot-fail-wait, bootorder) -- I'm
> concerned about redundancy here.
The redundancy is because the firmware and the bootloader actually
_consume_ these fw_cfg strings to produce the others (the ACPI tables,
the kernel configuration options).
On the other hand, hiding some strings just because they ought to have
been consumed already makes little sense.
Paolo
- Re: [Qemu-devel] [PATCH v3 1/4] firmware: introduce sysfs driver for QEMU's fw_cfg device, (continued)
- Re: [Qemu-devel] [PATCH v3 0/4] SysFS driver for QEMU fw_cfg device,
Paolo Bonzini <=
[Qemu-devel] [PATCH v3 4/4] firmware: create directory hierarchy for sysfs fw_cfg entries, Gabriel L. Somlo, 2015/10/08
[Qemu-devel] [PATCH v3 3/4] kobject: export kset_find_obj() for module use, Gabriel L. Somlo, 2015/10/08