Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1239520
| From | Peter Maydell <peter.maydell@linaro.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v3 0/4] SysFS driver for QEMU fw_cfg device |
| Date | 2015-10-05 15:00 +0200 |
| Message-ID | <qgdwZ-7MJ-9@gated-at.bofh.it> (permalink) |
| References | <qfEIV-8ui-3@gated-at.bofh.it> <qgaSu-4bV-11@gated-at.bofh.it> <qgdnj-7Bp-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 5 October 2015 at 13:40, Gabriel L. Somlo <somlo@cmu.edu> wrote: > In addition, Michael's comment earlier in the thread suggests that > even my current acpi version isn't sufficiently "orthodox" w.r.t. > ACPI, and I should be providing the hardware access routine as > an ACPI/AML routine, to avoid race conditions with the rest of ACPI, > and for encapsulation. I.e. it's even rude to use the fw_cfg node's > ACPI _CRS method (the part where I'd be treating it like a DT stand-in > only to query fw_cfg's hardware specifics). If you want to try to support "firmware might also be reading fw_cfg at the same time as the kernel" this is a (painful) problem regardless of how the kernel figures out whether a fw_cfg device is present. I had assumed that one of the design assumptions of this series was that firmware would only read the fw_cfg before booting the guest kernel and never touch it afterwards. If it might touch it later then letting the guest kernel also mess with fw_cfg seems like a really bad idea. thanks -- PMM -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH v3 0/4] SysFS driver for QEMU fw_cfg device "Gabriel L. Somlo" <somlo@cmu.edu> - 2015-10-04 01:50 +0200
Re: [PATCH v3 0/4] SysFS driver for QEMU fw_cfg device Mark Rutland <mark.rutland@arm.com> - 2015-10-05 12:10 +0200
Re: [PATCH v3 0/4] SysFS driver for QEMU fw_cfg device Paolo Bonzini <pbonzini@redhat.com> - 2015-10-05 13:50 +0200
Re: [PATCH v3 0/4] SysFS driver for QEMU fw_cfg device Mark Rutland <mark.rutland@arm.com> - 2015-10-05 14:30 +0200
Re: [PATCH v3 0/4] SysFS driver for QEMU fw_cfg device "Gabriel L. Somlo" <somlo@cmu.edu> - 2015-10-05 14:50 +0200
Re: [PATCH v3 0/4] SysFS driver for QEMU fw_cfg device Mark Rutland <mark.rutland@arm.com> - 2015-10-05 15:00 +0200
Re: [PATCH v3 0/4] SysFS driver for QEMU fw_cfg device "Gabriel L. Somlo" <somlo@cmu.edu> - 2015-10-05 15:30 +0200
Re: [PATCH v3 0/4] SysFS driver for QEMU fw_cfg device "Gabriel L. Somlo" <somlo@cmu.edu> - 2015-10-05 14:50 +0200
Re: [PATCH v3 0/4] SysFS driver for QEMU fw_cfg device Peter Maydell <peter.maydell@linaro.org> - 2015-10-05 15:00 +0200
Re: [PATCH v3 0/4] SysFS driver for QEMU fw_cfg device "Gabriel L. Somlo" <somlo@cmu.edu> - 2015-10-05 15:20 +0200
Re: [PATCH v3 0/4] SysFS driver for QEMU fw_cfg device Paolo Bonzini <pbonzini@redhat.com> - 2015-10-05 15:20 +0200
Re: [PATCH v3 0/4] SysFS driver for QEMU fw_cfg device Mark Rutland <mark.rutland@arm.com> - 2015-10-05 15:10 +0200
Re: [PATCH v3 0/4] SysFS driver for QEMU fw_cfg device Laszlo Ersek <lersek@redhat.com> - 2015-10-06 09:20 +0200
csiph-web