[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <561263A4.2020304@redhat.com>
Date: Mon, 5 Oct 2015 13:48:52 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Mark Rutland <mark.rutland@....com>,
"Gabriel L. Somlo" <somlo@....edu>
Cc: gregkh@...uxfoundation.org, paul@...an.com, galak@...eaurora.org,
will.deacon@....com, agross@...eaurora.org, zajec5@...il.com,
hanjun.guo@...aro.org, catalin.marinas@....com,
linux-api@...r.kernel.org, linux-kernel@...r.kernel.org,
kernelnewbies@...nelnewbies.org, matt.fleming@...el.com,
lersek@...hat.com, jordan.l.justen@...el.com, mst@...hat.com,
peter.maydell@...aro.org, leif.lindholm@...aro.org,
ard.biesheuvel@...aro.org, kraxel@...hat.com, qemu-devel@...gnu.org
Subject: Re: [PATCH v3 0/4] SysFS driver for QEMU fw_cfg device
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists