From: Wei Yang <richardw.yang@linux.intel.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
ross.zwisler@linux.intel.com,
Xiao Guangrong <xiaoguangrong.eric@gmail.com>,
Wei Yang <richardw.yang@linux.intel.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] docs/nvdimm: add example on persistent backend setup
Date: Thu, 1 Aug 2019 08:35:39 +0800 [thread overview]
Message-ID: <20190801003539.GA6721@richard> (raw)
In-Reply-To: <CAJSP0QV0rvpJU3Ct7khcHgUQ9cCQAfUyJz5m6kQDNjA1dcc8EA@mail.gmail.com>
On Tue, Jul 30, 2019 at 07:03:45AM +0100, Stefan Hajnoczi wrote:
>On Tue, Jul 30, 2019 at 1:52 AM Wei Yang <richardw.yang@linux.intel.com> wrote:
>>
>> Hi, Stefan
>>
>> Thanks for your comments :-)
>>
>> On Mon, Jul 29, 2019 at 02:58:59PM +0100, Stefan Hajnoczi wrote:
>> >On Wed, Jul 24, 2019 at 03:03:07PM +0800, Wei Yang wrote:
>> >> Persistent backend setup requires some knowledge about nvdimm and ndctl
>> >> tool. Some users report they may struggle to gather these knowledge and
>> >> have difficulty to setup it properly.
>> >>
>> >> Here we provide two examples for persistent backend and gives the link
>> >> to ndctl. By doing so, user could try it directly and do more
>> >> investigation on persistent backend setup with ndctl.
>> >>
>> >> Signed-off-by: Wei Yang <richardw.yang@linux.intel.com>
>> >> ---
>> >> docs/nvdimm.txt | 28 ++++++++++++++++++++++++++++
>> >> 1 file changed, 28 insertions(+)
>> >>
>> >> diff --git a/docs/nvdimm.txt b/docs/nvdimm.txt
>> >> index b531cacd35..baba7a940d 100644
>> >> --- a/docs/nvdimm.txt
>> >> +++ b/docs/nvdimm.txt
>> >> @@ -171,6 +171,32 @@ guest software that this vNVDIMM device contains a region that cannot
>> >> accept persistent writes. In result, for example, the guest Linux
>> >> NVDIMM driver, marks such vNVDIMM device as read-only.
>> >>
>> >> +Backend File Setup Example
>> >> +..........................
>>
>> Here I use '-' because I want to say this is a sub-section of "Guest Data
>> Persistence".
>>
>> Actually, I struggled a little to pick up a proper character. Do you think '-'
>> is the proper one?
>
>This is a .txt file without syntax. Whatever you choose might be
>confusing to someone. If you use a separate '-' section like the rest
>of the document then that avoids confusion.
>
Sure, let me change it. Thanks :)
>Stefan
--
Wei Yang
Help you, Help me
prev parent reply other threads:[~2019-08-01 0:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 7:03 [Qemu-devel] [PATCH] docs/nvdimm: add example on persistent backend setup Wei Yang
2019-07-24 7:28 ` Pankaj Gupta
2019-07-24 8:53 ` Wei Yang
2019-07-24 10:08 ` Pankaj Gupta
2019-07-24 10:17 ` Pankaj Gupta
2019-07-24 14:52 ` Wei Yang
2019-07-25 4:43 ` Pankaj Gupta
2019-07-25 4:46 ` Pankaj Gupta
2019-07-29 13:58 ` Stefan Hajnoczi
2019-07-30 0:51 ` Wei Yang
2019-07-30 6:03 ` Stefan Hajnoczi
2019-08-01 0:35 ` Wei Yang [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=20190801003539.GA6721@richard \
--to=richardw.yang@linux.intel.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=ross.zwisler@linux.intel.com \
--cc=stefanha@gmail.com \
--cc=xiaoguangrong.eric@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.