nvdimm.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: Taylor Stark <tstark@linux.microsoft.com>
Cc: Vishal L Verma <vishal.l.verma@intel.com>,
	Dave Jiang <dave.jiang@intel.com>,
	 "Weiny, Ira" <ira.weiny@intel.com>,
	Linux NVDIMM <nvdimm@lists.linux.dev>,
	apais@microsoft.com,  tyhicks@microsoft.com,
	jamorris@microsoft.com, benhill@microsoft.com,
	 sunilmut@microsoft.com, grahamwo@microsoft.com,
Subject: Re: [PATCH v2 0/2] virtio-pmem: Support PCI BAR-relative addresses
Date: Tue, 24 Aug 2021 17:35:48 -0700	[thread overview]
Message-ID: <CAPcyv4gKqK6Mi6-PT0Mo=P=gBvMkA2zK1Huo3f2aAKYAP3SCVg@mail.gmail.com> (raw)
In-Reply-To: <20210715223324.GA29063@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>

On Thu, Jul 15, 2021 at 3:34 PM Taylor Stark <tstark@linux.microsoft.com> wrote:
> Changes from v1 [1]:
>  - Fixed a bug where the guest might touch pmem region prior to the
>    backing file being mapped into the guest's address space.
> [1]: https://www.mail-archive.com/linux-nvdimm@lists.01.org/msg23736.html
> ---
> These patches add support to virtio-pmem to allow the pmem region to be
> specified in either guest absolute terms or as a PCI BAR-relative address.
> This is required to support virtio-pmem in Hyper-V, since Hyper-V only
> allows PCI devices to operate on PCI memory ranges defined via BARs.
> Taylor Stark (2):
>   virtio-pmem: Support PCI BAR-relative addresses
>   virtio-pmem: Set DRIVER_OK status prior to creating pmem region

Are these patches still valid? I am only seeing one of them on the list.

  reply	other threads:[~2021-08-25  0:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-15 22:33 [PATCH v2 0/2] virtio-pmem: Support PCI BAR-relative addresses Taylor Stark
2021-08-25  0:35 ` Dan Williams [this message]
2021-08-25 21:56   ` Taylor Stark
2021-08-25 22:05     ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAPcyv4gKqK6Mi6-PT0Mo=P=gBvMkA2zK1Huo3f2aAKYAP3SCVg@mail.gmail.com' \
    --to=dan.j.williams@intel.com \
    --cc=apais@microsoft.com \
    --cc=benhill@microsoft.com \
    --cc=dave.jiang@intel.com \
    --cc=grahamwo@microsoft.com \
    --cc=ira.weiny@intel.com \
    --cc=jamorris@microsoft.com \
    --cc=nvdimm@lists.linux.dev \
    --cc=sunilmut@microsoft.com \
    --cc=tstark@linux.microsoft.com \
    --cc=tstark@microsoft.com \
    --cc=tyhicks@microsoft.com \
    --cc=vishal.l.verma@intel.com \


* 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).