From: Xiao Guangrong <guangrong.xiao@linux.intel.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
pbonzini@redhat.com, imammedo@redhat.com
Cc: ehabkost@redhat.com, kvm@vger.kernel.org, mst@redhat.com,
gleb@kernel.org, mtosatti@redhat.com, qemu-devel@nongnu.org,
stefanha@redhat.com, dan.j.williams@intel.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH v8 0/5] implement vNVDIMM
Date: Sat, 5 Dec 2015 12:29:52 +0800 [thread overview]
Message-ID: <56626840.3050501@linux.intel.com> (raw)
In-Reply-To: <5661C171.20306@virtuozzo.com>
On 12/05/2015 12:38 AM, Vladimir Sementsov-Ogievskiy wrote:
> On 16.11.2015 13:50, Xiao Guangrong wrote:
>> NVDIMM (A Non-Volatile Dual In-line Memory Module) is going to be supported
>> on Intel's platform.
>
> Hi.
>
> One question: do this mean, that your qemu emulated nvidimm - pmem solution will work only on Intel
> host?
Currently, it is only enabled in x86 emulator, however, it can be easily enabled on
other platform which supports acpi.
BTW, you also need to check the linux kernel driver, nfit.ko, which is currently only
working on x86 IIUC:
config ACPI_NFIT
tristate "ACPI NVDIMM Firmware Interface Table (NFIT)"
depends on PHYS_ADDR_T_64BIT
depends on BLK_DEV
depends on ARCH_HAS_MMIO_FLUSH
select LIBNVDIMM
help
Infrastructure to probe ACPI 6 compliant platforms for
NVDIMMs (NFIT) and register a libnvdimm device tree. In
addition to storage devices this also enables libnvdimm to pass
ACPI._DSM messages for platform/dimm configuration.
To compile this driver as a module, choose M here:
the module will be called nfit.
$ git grep ARCH_HAS_MMIO_FLUSH
arch/x86/Kconfig: select ARCH_HAS_MMIO_FLUSH
drivers/acpi/Kconfig: depends on ARCH_HAS_MMIO_FLUSH
lib/Kconfig:config ARCH_HAS_MMIO_FLUSH
You should check ARCH_HAS_MMIO_FLUSH on your platform.
Thanks!
prev parent reply other threads:[~2015-12-05 4:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 10:50 [Qemu-devel] [PATCH v8 0/5] implement vNVDIMM Xiao Guangrong
2015-11-16 10:50 ` [Qemu-devel] [PATCH v8 1/5] nvdimm: implement NVDIMM device abstract Xiao Guangrong
2015-11-16 10:51 ` [Qemu-devel] [PATCH v8 2/5] acpi: support specified oem table id for build_header Xiao Guangrong
2015-11-16 10:51 ` [Qemu-devel] [PATCH v8 3/5] nvdimm acpi: build ACPI NFIT table Xiao Guangrong
2015-11-30 10:30 ` Michael S. Tsirkin
2015-11-30 12:29 ` Xiao Guangrong
2015-11-16 10:51 ` [Qemu-devel] [PATCH v8 4/5] nvdimm acpi: build ACPI nvdimm devices Xiao Guangrong
2015-11-30 10:30 ` Michael S. Tsirkin
2015-11-30 12:21 ` Xiao Guangrong
2015-11-30 10:32 ` Michael S. Tsirkin
2015-11-30 12:31 ` Xiao Guangrong
2015-11-16 10:51 ` [Qemu-devel] [PATCH v8 5/5] nvdimm: add maintain info Xiao Guangrong
2015-11-18 1:59 ` [Qemu-devel] [PATCH v8 0/5] implement vNVDIMM Xiao Guangrong
2015-11-18 19:18 ` Eduardo Habkost
2015-11-18 20:44 ` Michael S. Tsirkin
2015-11-19 2:39 ` Xiao Guangrong
2015-11-19 8:21 ` Michael S. Tsirkin
2015-11-23 8:53 ` Stefan Hajnoczi
2015-11-30 8:51 ` Stefan Hajnoczi
2015-11-30 12:34 ` Xiao Guangrong
2015-11-30 10:38 ` Michael S. Tsirkin
2015-11-30 12:33 ` Xiao Guangrong
2015-12-04 16:38 ` Vladimir Sementsov-Ogievskiy
2015-12-05 4:29 ` Xiao Guangrong [this message]
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=56626840.3050501@linux.intel.com \
--to=guangrong.xiao@linux.intel.com \
--cc=dan.j.williams@intel.com \
--cc=ehabkost@redhat.com \
--cc=gleb@kernel.org \
--cc=imammedo@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=stefanha@redhat.com \
--cc=vsementsov@virtuozzo.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).