From: "Michael S. Tsirkin" <mst@redhat.com>
To: Xiao Guangrong <guangrong.xiao@linux.intel.com>
Cc: ehabkost@redhat.com, kvm@vger.kernel.org, gleb@kernel.org,
mtosatti@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com,
imammedo@redhat.com, pbonzini@redhat.com,
dan.j.williams@intel.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH v2 00/11] NVDIMM ACPI: introduce the framework of QEMU emulated
Date: Thu, 4 Feb 2016 18:24:54 +0200 [thread overview]
Message-ID: <20160204182310-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <1452624610-46945-1-git-send-email-guangrong.xiao@linux.intel.com>
On Wed, Jan 13, 2016 at 02:49:59AM +0800, Xiao Guangrong wrote:
> This patchset is against commit 8a1be662a69 (virtio: fix error message for
> number of queues) on pci branch of Michael's git tree
> and can be found at:
> https://github.com/xiaogr/qemu.git nvdimm-acpi-v2
Looks good, thanks!
There's been a bunch of changes in my tree so
this no longer applies.
Pls rebase and repost, and I'll apply.
> Changelog:
> These changes are based on Igor's comments:
> - drop ssdt.rev2 support as the memory address allocated by BIOS/OVMF
> are always 32 bits
> - support to test NVDIMM tables (NFIT and NVDIMM SSDT)
> - add _CRS to report its operation region
> - make AML APIs change be the separated patches
>
> 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
>
> Xiao Guangrong (11):
> tests: acpi: test multiple SSDT tables
> tests: acpi: test NVDIMM tables
> acpi: add aml_create_field()
> acpi: add aml_concatenate()
> acpi: allow using object as offset for OperationRegion
> nvdimm acpi: initialize the resource used by NVDIMM ACPI
> nvdimm acpi: introduce patched dsm memory
> nvdimm acpi: let qemu handle _DSM method
> nvdimm acpi: emulate dsm method
> nvdimm acpi: add _CRS
> tests: acpi: update nvdimm ssdt table
>
> hw/acpi/Makefile.objs | 2 +-
> hw/acpi/aml-build.c | 33 +++-
> hw/acpi/nvdimm.c | 255 +++++++++++++++++++++++++++-
> 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 | 5 +-
> include/hw/i386/pc.h | 5 +-
> include/hw/mem/nvdimm.h | 36 +++-
> tests/acpi-test-data/pc/NFIT | Bin 0 -> 224 bytes
> tests/acpi-test-data/pc/NFIT.bridge | Bin 0 -> 224 bytes
> tests/acpi-test-data/pc/SSDT | Bin 2486 -> 2885 bytes
> tests/acpi-test-data/pc/SSDT-NVDIMM | Bin 0 -> 403 bytes
> tests/acpi-test-data/pc/SSDT-NVDIMM.bridge | Bin 0 -> 403 bytes
> tests/acpi-test-data/pc/SSDT.bridge | Bin 4345 -> 4745 bytes
> tests/acpi-test-data/q35/NFIT | Bin 0 -> 224 bytes
> tests/acpi-test-data/q35/NFIT.bridge | Bin 0 -> 224 bytes
> tests/acpi-test-data/q35/SSDT | Bin 691 -> 1090 bytes
> tests/acpi-test-data/q35/SSDT-NVDIMM | Bin 0 -> 403 bytes
> tests/acpi-test-data/q35/SSDT-NVDIMM.bridge | Bin 0 -> 403 bytes
> tests/acpi-test-data/q35/SSDT.bridge | Bin 708 -> 1107 bytes
> tests/bios-tables-test.c | 58 +++++--
> 23 files changed, 400 insertions(+), 56 deletions(-)
> create mode 100644 tests/acpi-test-data/pc/NFIT
> create mode 100644 tests/acpi-test-data/pc/NFIT.bridge
> create mode 100644 tests/acpi-test-data/pc/SSDT-NVDIMM
> create mode 100644 tests/acpi-test-data/pc/SSDT-NVDIMM.bridge
> create mode 100644 tests/acpi-test-data/q35/NFIT
> create mode 100644 tests/acpi-test-data/q35/NFIT.bridge
> create mode 100644 tests/acpi-test-data/q35/SSDT-NVDIMM
> create mode 100644 tests/acpi-test-data/q35/SSDT-NVDIMM.bridge
>
> --
> 1.8.3.1
next prev parent reply other threads:[~2016-02-04 16:25 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 18:49 [Qemu-devel] [PATCH v2 00/11] NVDIMM ACPI: introduce the framework of QEMU emulated Xiao Guangrong
2016-01-12 18:50 ` [Qemu-devel] [PATCH v2 01/11] tests: acpi: test multiple SSDT tables Xiao Guangrong
2016-01-12 18:50 ` [Qemu-devel] [PATCH v2 02/11] tests: acpi: test NVDIMM tables Xiao Guangrong
2016-02-04 16:20 ` Michael S. Tsirkin
2016-02-14 5:36 ` Xiao Guangrong
2016-01-12 18:50 ` [Qemu-devel] [PATCH v2 03/11] acpi: add aml_create_field() Xiao Guangrong
2016-02-08 10:47 ` Igor Mammedov
2016-02-14 5:41 ` Xiao Guangrong
2016-01-12 18:50 ` [Qemu-devel] [PATCH v2 04/11] acpi: add aml_concatenate() Xiao Guangrong
2016-02-08 10:51 ` Igor Mammedov
2016-02-14 5:52 ` Xiao Guangrong
2016-02-14 5:55 ` Xiao Guangrong
2016-02-15 9:02 ` Igor Mammedov
2016-02-15 10:32 ` Xiao Guangrong
2016-01-12 18:50 ` [Qemu-devel] [PATCH v2 05/11] acpi: allow using object as offset for OperationRegion Xiao Guangrong
2016-02-08 10:57 ` Igor Mammedov
2016-01-12 18:50 ` [Qemu-devel] [PATCH v2 06/11] nvdimm acpi: initialize the resource used by NVDIMM ACPI Xiao Guangrong
2016-02-04 16:22 ` Michael S. Tsirkin
2016-02-08 11:03 ` Igor Mammedov
2016-02-14 5:57 ` Xiao Guangrong
2016-02-15 9:11 ` Igor Mammedov
2016-02-15 9:18 ` Michael S. Tsirkin
2016-02-15 10:13 ` Xiao Guangrong
2016-02-15 10:30 ` Michael S. Tsirkin
2016-02-15 10:47 ` Igor Mammedov
2016-02-15 11:22 ` Xiao Guangrong
2016-02-15 11:45 ` Michael S. Tsirkin
2016-02-15 13:32 ` Igor Mammedov
2016-02-15 15:53 ` Xiao Guangrong
2016-02-15 17:24 ` Igor Mammedov
2016-02-15 18:35 ` Xiao Guangrong
2016-02-16 11:00 ` Igor Mammedov
2016-02-17 2:04 ` Xiao Guangrong
2016-02-17 17:26 ` Michael S. Tsirkin
2016-02-18 4:03 ` Xiao Guangrong
2016-02-18 10:05 ` Igor Mammedov
2016-02-19 8:08 ` Michael S. Tsirkin
2016-02-19 8:43 ` Dan Williams
2016-02-22 10:30 ` Xiao Guangrong
2016-02-22 10:34 ` Xiao Guangrong
2016-02-18 10:20 ` Michael S. Tsirkin
2016-02-15 11:36 ` Michael S. Tsirkin
2016-01-12 18:50 ` [Qemu-devel] [PATCH v2 07/11] nvdimm acpi: introduce patched dsm memory Xiao Guangrong
2016-01-12 18:50 ` [Qemu-devel] [PATCH v2 08/11] nvdimm acpi: let qemu handle _DSM method Xiao Guangrong
2016-01-12 18:50 ` [Qemu-devel] [PATCH v2 09/11] nvdimm acpi: emulate dsm method Xiao Guangrong
2016-01-12 18:50 ` [Qemu-devel] [PATCH v2 10/11] nvdimm acpi: add _CRS Xiao Guangrong
2016-01-12 18:50 ` [Qemu-devel] [PATCH v2 11/11] tests: acpi: update nvdimm ssdt table Xiao Guangrong
2016-01-20 2:21 ` [Qemu-devel] [PATCH v2 00/11] NVDIMM ACPI: introduce the framework of QEMU emulated Xiao Guangrong
2016-01-28 4:42 ` Xiao Guangrong
2016-02-04 16:24 ` Michael S. Tsirkin [this message]
2016-02-14 5:38 ` Xiao Guangrong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160204182310-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=ehabkost@redhat.com \
--cc=gleb@kernel.org \
--cc=guangrong.xiao@linux.intel.com \
--cc=imammedo@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=stefanha@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).