qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Vishal Verma <vishal.l.verma@intel.com>,
	Wei Yang <richardw.yang@linux.intel.com>,
	Ross Zwisler <ross.zwisler@linux.intel.com>,
	Haozhong Zhang <haozhong.zhang@intel.com>,
	Dan Williams <dan.j.williams@intel.com>,
	Jeff Moyer <jmoyer@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Microsoft and Intel NVDIMM ACPI _DSM interfaces status?
Date: Wed, 17 Mar 2021 11:49:31 +0000	[thread overview]
Message-ID: <YFHsy8599w7KT1SB@stefanha-x1.localdomain> (raw)

[-- Attachment #1: Type: text/plain, Size: 725 bytes --]

Hi,
Microsoft and Intel developed two different ACPI NVDIMM _DSM interfaces.

The specs for the Intel interface are available here:
https://pmem.io/documents/NVDIMM_DSM_Interface_Example.pdf

This is the interface that QEMU emulates. It has been reported that
Windows 2016 Server and 2019 Server guests do not recognize QEMU's
emulated NVDIMM devices using the Microsoft driver.

I'd like to understand the path forward that will allow both Linux and
Windows guests to successfully use QEMU's emulated NVDIMM device
(https://gitlab.com/qemu-project/qemu/-/blob/master/hw/acpi/nvdimm.c).

Are/have these two interfaces being/been unified?

Should QEMU emulate both of them to make running Windows guests easy?

Thanks,
Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2021-03-17 11:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17 11:49 Stefan Hajnoczi [this message]
2021-03-17 22:45 ` Microsoft and Intel NVDIMM ACPI _DSM interfaces status? Laszlo Ersek
2021-03-18  2:00   ` Dexuan Cui
2021-03-18 19:30     ` Stefan Hajnoczi
2021-03-17 23:52 ` Dan Williams
2021-03-18 19:28   ` Stefan Hajnoczi

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=YFHsy8599w7KT1SB@stefanha-x1.localdomain \
    --to=stefanha@redhat.com \
    --cc=dan.j.williams@intel.com \
    --cc=haozhong.zhang@intel.com \
    --cc=jmoyer@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richardw.yang@linux.intel.com \
    --cc=ross.zwisler@linux.intel.com \
    --cc=vishal.l.verma@intel.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).