From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from linux.microsoft.com (linux.microsoft.com [13.77.154.182]) by smtp.subspace.kernel.org (Postfix) with ESMTP id AA15D70 for ; Wed, 21 Jul 2021 22:08:51 +0000 (UTC) Received: by linux.microsoft.com (Postfix, from userid 1096) id 53AC920B7178; Wed, 21 Jul 2021 15:08:51 -0700 (PDT) DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com 53AC920B7178 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.microsoft.com; s=default; t=1626905331; bh=8OseoXILN4vqLqt6LUZc31dEZZN6YDFZTDi1RrRQrRE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=MR4eLP/K1Gt3KvhTJ5ZI/hWRufLYQpUa7GXhHrHr7cqiVDubimuESO40yCvIYO6mx fpn59lEm+GT3Cg1v88yff5tlNaSFIDaACjwA3SDHOVoZDhBEJKVsUBQQOnrLOlzfBD lfchgpO9Y/J4GMIyfCj+TA9SZR/HjHl4KihNGMAw= Date: Wed, 21 Jul 2021 15:08:51 -0700 From: Taylor Stark To: Pankaj Gupta Cc: Pankaj Gupta , Dan Williams , Vishal Verma , Dave Jiang , Ira Weiny , nvdimm@lists.linux.dev, apais@microsoft.com, tyhicks@microsoft.com, jamorris@microsoft.com, benhill@microsoft.com, sunilmut@microsoft.com, grahamwo@microsoft.com, tstark@microsoft.com, "Michael S . Tsirkin" Subject: Re: [PATCH v2 1/2] virtio-pmem: Support PCI BAR-relative addresses Message-ID: <20210721220851.GB19842@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> References: <20210715223505.GA29329@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> <20210720063510.GB8476@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> Precedence: bulk X-Mailing-List: nvdimm@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) On Tue, Jul 20, 2021 at 08:51:04AM +0200, Pankaj Gupta wrote: > > > > > > > > - virtio_cread_le(vpmem->vdev, struct virtio_pmem_config, > > > > - start, &vpmem->start); > > > > - virtio_cread_le(vpmem->vdev, struct virtio_pmem_config, > > > > - size, &vpmem->size); > > > > + /* Retrieve the pmem device's address and size. It may have been supplied > > > > + * as a PCI BAR-relative shared memory region, or as a guest absolute address. > > > > + */ > > > > + have_shm_region = virtio_get_shm_region(vpmem->vdev, &pmem_region, > > > > + VIRTIO_PMEM_SHMCAP_ID_PMEM_REGION); > > > > > > Current implementation of Virtio pmem device in Qemu does not expose > > > it as PCI BAR. > > > So, can't test it. Just curious if device side implementation is also > > > tested for asynchronous > > > flush case? > > > > > > Thanks, > > > Pankaj > > > > Yes, I tested the async flush case as well. We basically call > > FlushFileBuffers on the backing file, which is Windows' equivalent of > > fsync. I also briefly tested with qemu to ensure that still works with > > the patch. > > Thank you for the confirmation. This sounds really good. > I am also getting back to pending items for virtio-pmem. > > On a side question: Do you guys have any or plan for Windows guest > implementation > for virtio-pmem? Unfortunately, my team doesn't currently have any plans to add a Windows virtio-pmem implementation. My team is primarily focused on virtualization in client environments, which is a little different than server environments. For our Windows-based scenarios, dynamically sized disks are important. It's tricky to get that to work with pmem+DAX given that Windows isn't state separated.