From: Andrzej Jakowski <andrzej.jakowski@linux.intel.com>
To: Stefan Hajnoczi <stefanha@gmail.com>,
Klaus Birkelund Jensen <its@irrelevant.dk>
Cc: Kevin Wolf <kwolf@redhat.com>,
Haozhong Zhang <haozhong.zhang@intel.com>,
qemu block <qemu-block@nongnu.org>,
Dave Gilbert <dgilbert@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Zhang Yi <yi.z.zhang@linux.intel.com>,
"He, Junyan" <junyan.he@intel.com>,
kbusch@kernel.org, Max Reitz <mreitz@redhat.com>
Subject: Re: [PATCH RESEND v2] block/nvme: introduce PMR support from NVMe 1.4 spec
Date: Mon, 16 Mar 2020 10:10:15 -0700 [thread overview]
Message-ID: <cf3833cc-fbd1-9930-fee1-ed9b26647f1c@linux.intel.com> (raw)
In-Reply-To: <20200316113216.GB449975@stefanha-x1.localdomain>
On 3/16/20 4:32 AM, Stefan Hajnoczi wrote:
> On Wed, Mar 11, 2020 at 11:08:27PM -0700, Klaus Birkelund Jensen wrote:
>> On Mar 11 15:54, Andrzej Jakowski wrote:
>>> On 3/11/20 2:20 AM, Stefan Hajnoczi wrote:
>>>> Please try:
>>>>
>>>> $ git grep pmem
>>>>
>>>> backends/hostmem-file.c is the backend that can be used and the
>>>> pmem_persist() API can be used to flush writes.
>>> I've reworked this patch into hostmem-file type of backend.
>>> From simple tests in virtual machine: writing to PMR region
>>> and then reading from it after VM power cycle I have observed that
>>> there is no persistency.
> Sounds like an integration bug. QEMU's NVDIMM emulation uses
> HostMemoryBackend and file contents survive guest reboot.
>
> If you would like help debugging this, please post a link to the code
> and the command-line that you are using.
>
Code is posted here
https://github.com/AndrzejJakowski/qemu/commit/3a7762a1d13ff1543d1da430748eb24e38faab6f
QEMU command line:
# below are just relevant pieces of configuration, other stuff omitted
# tried different setting (e.g. pmem=on and pmem=off)
./x86_64-softmmu/qemu-system-x86_64 ... \
-object memory-backend-file,id=mem1,share=off,pmem=on,mem-path=../nvme_pmr.bin,size=$((1*1024*1024)) \
-drive file=../nvme.bin,format=raw,if=none,id=nvme_emulated \
-device nvme,drive=nvme_emulated,serial="test serial",pmrdev=mem1
In VM:
My persisent memory region is exposed PCI BAR
Region 2: Memory at fe000000 (64-bit, prefetchable) [size=1M]
So I perform reads/writes from/to following adress 0xfe000000 (decimal 4261412864)
dd if=test.bin of=/dev/mem bs=1 count=30 seek=4261412864
dd if=/dev/mem of=test1.bin bs=1 count=30 skip=4261412864
On VMM I didn't observe that backing file has been updated and after power cycling VM
I see old junk when reading PMR region.
Also from include/qemu/pmem.h it looks like pmem_persist() will cause qemu to exit
if libpmem is not installed:
#ifndef QEMU_PMEM_H
#define QEMU_PMEM_H
#ifdef CONFIG_LIBPMEM
#include <libpmem.h>
#else /* !CONFIG_LIBPMEM */
static inline void *
pmem_memcpy_persist(void *pmemdest, const void *src, size_t len)
{
/* If 'pmem' option is 'on', we should always have libpmem support,
or qemu will report a error and exit, never come here. */
g_assert_not_reached();
return NULL;
}
static inline void
pmem_persist(const void *addr, size_t len)
{
g_assert_not_reached();
}
#endif /* CONFIG_LIBPMEM */
#endif /* QEMU_PMEM_H */
next prev parent reply other threads:[~2020-03-16 17:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 22:38 [PATCH RESEND v2] block/nvme: introduce PMR support from NVMe 1.4 spec Andrzej Jakowski
2020-03-10 9:51 ` Stefan Hajnoczi
2020-03-10 20:09 ` Andrzej Jakowski
2020-03-11 9:20 ` Stefan Hajnoczi
2020-03-11 22:54 ` Andrzej Jakowski
2020-03-12 6:08 ` Klaus Birkelund Jensen
2020-03-16 11:32 ` Stefan Hajnoczi
2020-03-16 17:10 ` Andrzej Jakowski [this message]
2020-03-17 11:23 ` Stefan Hajnoczi
2020-03-18 4:20 ` Andrzej Jakowski
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=cf3833cc-fbd1-9930-fee1-ed9b26647f1c@linux.intel.com \
--to=andrzej.jakowski@linux.intel.com \
--cc=dgilbert@redhat.com \
--cc=haozhong.zhang@intel.com \
--cc=its@irrelevant.dk \
--cc=junyan.he@intel.com \
--cc=kbusch@kernel.org \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=yi.z.zhang@linux.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).