From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54178) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZAagN-0003NL-Ej for qemu-devel@nongnu.org; Thu, 02 Jul 2015 05:21:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZAagJ-00011u-5Z for qemu-devel@nongnu.org; Thu, 02 Jul 2015 05:21:23 -0400 Received: from mail-wg0-x231.google.com ([2a00:1450:400c:c00::231]:35302) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZAagI-00011i-VQ for qemu-devel@nongnu.org; Thu, 02 Jul 2015 05:21:19 -0400 Received: by wgjx7 with SMTP id x7so57579434wgj.2 for ; Thu, 02 Jul 2015 02:21:18 -0700 (PDT) Date: Thu, 2 Jul 2015 10:20:44 +0100 From: Stefan Hajnoczi Message-ID: <20150702092044.GB20198@stefanha-thinkpad.redhat.com> References: <1435762232-15543-1-git-send-email-guangrong.xiao@linux.intel.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/NkBOFFp2J2Af1nK" Content-Disposition: inline In-Reply-To: <1435762232-15543-1-git-send-email-guangrong.xiao@linux.intel.com> Subject: Re: [Qemu-devel] [PATCH 00/16] implement vNVDIMM List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Xiao Guangrong Cc: ehabkost@redhat.com, kvm@vger.kernel.org, mst@redhat.com, gleb@kernel.org, mtosatti@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com, imammedo@redhat.com, pbonzini@redhat.com, rth@twiddle.net --/NkBOFFp2J2Af1nK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 01, 2015 at 10:50:16PM +0800, Xiao Guangrong wrote: > =3D=3D=3D=3D=3D=3D Background =3D=3D=3D=3D=3D=3D > NVDIMM (A Non-Volatile Dual In-line Memory Module) is going to be support= ed > on Intel's platform. They are discovered via ACPI and configured by _DSM > method of NVDIMM device in ACPI. There has some supporting documents which > can be found at: > ACPI 6: http://www.uefi.org/sites/default/files/resources/ACPI_6.0.pdf > NVDIMM Namespace: http://pmem.io/documents/NVDIMM_Namespace_Spec.pdf > DSM Interface Example: http://pmem.io/documents/NVDIMM_DSM_Interface_Exam= ple.pdf > Driver Writer's Guide: http://pmem.io/documents/NVDIMM_Driver_Writers_Gui= de.pdf >=20 > Currently, the NVDIMM driver has been merged into upstream Linux Kernel a= nd > this patchset tries to enable it in virtualization field =46rom a device model perspective, have you checked whether it makes sense to integrate nvdimms into the pc-dimm and hostmem code that is used for memory hotplug and NUMA? The NVDIMM device in your patches is a completely new TYPE_DEVICE so it doesn't share any interfaces or code with existing memory devices. Maybe that is the right solution here because NVDIMMs have different characteristics, but I'm not sure. --/NkBOFFp2J2Af1nK Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVlQJsAAoJEJykq7OBq3PI3xoH/2tHPkKsg2DMzNGtaiy2mPYt wf8EbJtHJSw6Mc7jRJzI4T2f8NSFBgbce67JmnM0PF+t28nxyMANSQtq2It0UelC AmWDxGEXbRyf8CZFfangqFvwOLElNyUNKqOG0xE5jD0oThXj13H7SavP29ZntQNC YKFqgrCBSMwvW9AiyGRqf1QLDANxVtRvQ0bT6XKynddCxeHhtLf1wLVkK8Osekaz QKqo+r8xv8xBML37bMuUbvwqURXTZQ4Eh8lLOeez4Z3O6iXZ6+uw/C41bA3IBWsK r8Xuu9TldnusvywZND49rqFumKasFwrS80X9Y1q4wk/oR7/j1N3UFUeAe7H/MqE= =WTGO -----END PGP SIGNATURE----- --/NkBOFFp2J2Af1nK--