nvdimm.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Linux NVDIMM <nvdimm@lists.linux.dev>
Subject: Re: qemu-emulated nfit devices disappeared
Date: Thu, 4 Nov 2021 10:19:53 -0700	[thread overview]
Message-ID: <YYQWOU//1oz0EMIu@infradead.org> (raw)
In-Reply-To: <YYQVq80QS77KkFV0@infradead.org>

On Thu, Nov 04, 2021 at 10:17:31AM -0700, Christoph Hellwig wrote:
> On Thu, Nov 04, 2021 at 10:09:37AM -0700, Dan Williams wrote:
> > Hmm, so the driver has 2 modes "labeled" and "label-less", in the
> > labeled mode it waits for an explicit:
> > 
> >     ndctl create-namespace
> > 
> > ...to provision region capacity into a namespace. In label-less mode
> > it just assumes that the boundaries of the region are the boundaries
> > of the namespace. In this case it looks like the driver found a label
> > index block with no namespaces defined so it's waiting for one to be
> > created. Are you saying that the only thing you changed from a working
> > config with defined namespace to this one was a kernel change? I.e.
> > the content of those memory-backend files has not changed?
> 
> Well, the config change is the only thing I though of as relevant.
> The content of those files actually changes all the time, as I also
> use them as the backing store for my qemu configs that use block
> devices.  E.g. the previous run they did show up as NVMe devices.

Ok, blowing the files away and recreating them makes the pmem
devices show up again.

  reply	other threads:[~2021-11-04 17:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-04  7:27 qemu-emulated nfit devices disappeared Christoph Hellwig
2021-11-04 16:00 ` Dan Williams
2021-11-04 16:04   ` Christoph Hellwig
2021-11-04 17:09     ` Dan Williams
2021-11-04 17:17       ` Christoph Hellwig
2021-11-04 17:19         ` Christoph Hellwig [this message]
2021-11-04 17:21           ` Dan Williams

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=YYQWOU//1oz0EMIu@infradead.org \
    --to=hch@infradead.org \
    --cc=dan.j.williams@intel.com \
    --cc=nvdimm@lists.linux.dev \
    /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).