On Tue, 5 Jan 2016 02:52:02 +0800 Xiao Guangrong <guangrong.xiao@xxxxxxxxxxxxxxx> wrote: > This patchset is against commit 5530427f0ca (acpi: extend aml_and() to > accept target argument) on pci branch of Michael's git tree > and can be found at: > https://github.com/xiaogr/qemu.git nvdimm-acpi-v1 > > This is the second part of vNVDIMM implementation which implements the > BIOS patched dsm memory and introduces the framework that allows QEMU > to emulate DSM method > > Thanks to Michael's idea, we do not reserve any memory for NVDIMM ACPI, > instead we let BIOS allocate the memory and patch the address to the > offset we want > > IO port is still enabled as it plays as the way to notify QEMU and pass > the patched dsm memory address, so that IO port region, 0x0a18 - 0xa20, > is reserved and it is divided into two 32 bits ports and used to pass > the low 32 bits and high 32 bits of dsm memory address to QEMU > > Thanks Igor's idea, this patchset also extends DSDT/SSDT to revision 2 > to apply 64 bit operations, in order to keeping compatibility, old > version (<= 2.5) still uses revision 1. Since 64 bit operations breaks > old guests (such as windows XP), we should keep the 64 bits stuff in > the private place where common ACPI operation does not touch it > general notes: 1. could you split out AML API additions/changes into separate patches? even if series nvdims patches couldn't be accepted on next respin, AML API patches could be good and we could pick them up just for API completeness. That also would make them easier to review and reduces count of patches you'd need to respin. 2. add test case for NVDIMM table blob, see tests/bios-tables-test.c at the beginning of series. 3. make V=1 check would show you ASL diff your patches are introducing, it will save you from booting real guest and dumping/decompiling tables manually. 4. at the end of series add NVDIMM table test blob with new table. you can use tests/acpi-test-data/rebuild-expected-aml.sh to make it 5. if make check by some miracle passes with these patches, dump NVDIMM table in guest and try to decompile and then compile it back with IASL, it will show you what needs to be fixed. PS: under NVDIMM table I mean SSDT NVMDIM table. > Igor Mammedov (1): > pc: acpi: bump DSDT/SSDT compliance revision to v2 > > Xiao Guangrong (5): > nvdimm acpi: initialize the resource used by NVDIMM ACPI > nvdimm acpi: introduce patched dsm memory > acpi: allow using acpi named offset for OperationRegion > nvdimm acpi: let qemu handle _DSM method > nvdimm acpi: emulate dsm method > > hw/acpi/Makefile.objs | 2 +- > hw/acpi/aml-build.c | 45 +++++++- > hw/acpi/ich9.c | 32 +++++ > hw/acpi/nvdimm.c | 276 ++++++++++++++++++++++++++++++++++++++++++-- > hw/acpi/piix4.c | 3 + > hw/i386/acpi-build.c | 41 ++++--- > hw/i386/pc.c | 8 +- > hw/i386/pc_piix.c | 5 + > hw/i386/pc_q35.c | 8 +- > include/hw/acpi/aml-build.h | 6 +- > include/hw/acpi/ich9.h | 2 + > include/hw/i386/pc.h | 19 ++- > include/hw/mem/nvdimm.h | 44 ++++++- > 13 files changed, 449 insertions(+), 42 deletions(-) > -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
