From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: [Qemu-devel] [PULL 07/10] nvdimm: set non-volatile on the memory region
Date: Tue, 30 Oct 2018 20:50:08 +0100 [thread overview]
Message-ID: <1540929011-19894-8-git-send-email-pbonzini@redhat.com> (raw)
In-Reply-To: <1540929011-19894-1-git-send-email-pbonzini@redhat.com>
From: Marc-André Lureau <marcandre.lureau@redhat.com>
qemu-system-x86_64 -machine pc,nvdimm -m 2G,slots=4,maxmem=16G -enable-kvm -monitor stdio -object memory-backend-file,id=mem1,share=on,mem-path=/tmp/foo,size=1G -device nvdimm,id=nvdimm1,memdev=mem1
HMP info mtree command reflects the flag with "nv-" prefix on memory type:
(qemu) info mtree
0000000100000000-000000013fffffff (prio 0, nv-i/o): alias nvdimm-memory @/objects/mem1 0000000000000000-000000003fffffff
(qemu) info mtree -f
0000000100000000-000000013fffffff (prio 0, nv-ram): /objects/mem1
Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Message-Id: <20181003114454.5662-3-marcandre.lureau@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
---
hw/mem/nvdimm.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/hw/mem/nvdimm.c b/hw/mem/nvdimm.c
index 49324f3..bf2adf5 100644
--- a/hw/mem/nvdimm.c
+++ b/hw/mem/nvdimm.c
@@ -116,6 +116,7 @@ static void nvdimm_prepare_memory_region(NVDIMMDevice *nvdimm, Error **errp)
nvdimm->nvdimm_mr = g_new(MemoryRegion, 1);
memory_region_init_alias(nvdimm->nvdimm_mr, OBJECT(dimm),
"nvdimm-memory", mr, 0, pmem_size);
+ memory_region_set_nonvolatile(nvdimm->nvdimm_mr, true);
nvdimm->nvdimm_mr->align = align;
}
--
1.8.3.1
next prev parent reply other threads:[~2018-10-30 19:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 19:50 [Qemu-devel] [PULL 00/10] Misc patches for 2018-10-30 Paolo Bonzini
2018-10-30 19:50 ` [Qemu-devel] [PULL 01/10] icount: fix deadlock when all cpus are sleeping Paolo Bonzini
2018-10-30 19:50 ` [Qemu-devel] [PULL 02/10] x86: hv_evmcs CPU flag support Paolo Bonzini
2018-10-30 19:50 ` [Qemu-devel] [PULL 03/10] i386: clarify that the Q35 machine type implements a P35 chipset Paolo Bonzini
2018-10-30 19:50 ` [Qemu-devel] [PULL 04/10] MAINTAINERS: remove or downgrade myself to reviewer from some subsystems Paolo Bonzini
2018-10-30 19:50 ` [Qemu-devel] [PULL 05/10] target/i386: Clear RF on SYSCALL instruction Paolo Bonzini
2018-10-30 19:50 ` [Qemu-devel] [PULL 06/10] memory: learn about non-volatile memory region Paolo Bonzini
2018-10-30 19:50 ` Paolo Bonzini [this message]
2018-10-30 19:50 ` [Qemu-devel] [PULL 08/10] memory-mapping: skip non-volatile memory regions in GuestPhysBlockList Paolo Bonzini
2018-11-05 15:37 ` Laszlo Ersek
2018-11-06 10:04 ` Paolo Bonzini
2018-10-30 19:50 ` [Qemu-devel] [PULL 09/10] scripts/dump-guest-memory: Synchronize with guest_phys_blocks_region_add Paolo Bonzini
2018-11-05 15:46 ` Laszlo Ersek
2018-11-06 10:06 ` Paolo Bonzini
2018-10-30 19:50 ` [Qemu-devel] [PULL 10/10] lsi53c895a: check message length value is valid Paolo Bonzini
2018-11-01 12:06 ` [Qemu-devel] [PULL 00/10] Misc patches for 2018-10-30 Peter Maydell
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=1540929011-19894-8-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).