Received: by 10.213.65.68 with SMTP id h4csp2132471imn; Sun, 8 Apr 2018 20:31:51 -0700 (PDT) X-Google-Smtp-Source: AIpwx4/o4VZOaYDGwI8bukSMvxMhKjZUnPRuCTujxVkUiwwz71xy8c7krEPCUWirQcDuDI5Qd0+a X-Received: by 10.98.133.28 with SMTP id u28mr27833884pfd.190.1523244711846; Sun, 08 Apr 2018 20:31:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523244711; cv=none; d=google.com; s=arc-20160816; b=QEGn3L1qMoDRuee4HSuvHntzxkO3GWQSctVeTteIl3EAVdiAjRfn2MOF8dzEleS8Pm K3UmdpakQxcSb6DBozfs4TXz/hfuXZEFMrNzjeDVGyEZD3InZf9ngKbOJSMBzqEmZWc0 FOoytlW32XzTI9gFdJVmBddTWBJC2LycyG05zsRuF5Qt3IoVCURvBzaFgDLu8klT23Sj BQJ1cKbOnvsmIVia3qM89Dsq8depxkY+kJJOsQhzVODh6WV7aWB1acamoGhhxpIvTZ7/ edTgG+rlX9exS2LRvLkMPIV4JjBacJS5nYOCB40epvBPSKu07KPzq1dnYYDBiJNKQna8 eLcw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature:arc-authentication-results; bh=ojGjEp2G6gUmbq7Kwc6AeFh6cLbKWB3Nqf59cKAAelU=; b=XVKGD64paB1JHmuyJYG2D7gzNPKG0VmZyQXqJJfLa+flcCPiQ6CkowNIRDwqksaxVQ 4yvjTUUbrYuACKm3/LvCefcRNky+svcTswE6piRNMKZ90sk1xFL+jouIxjKsWgXqFuge lNQWB4KjzHsCM5dqqVztSnMZIcw/AcpxnFKLCLGA2X4nSqKBMYvGYxr0xF3cNfHIpuOe 6vN8h8fQxrUNiitxJc7JTukKhJbKvePVusOLbqCgfIha4TrG3QZvQ3xQcTmXg0U+eXt8 EPwiylZt8MvxgVrNG0N7o7BDo1MVATPYV5kapPXnUhte9DRIs32KkLc9sLc/9kNNwdep uE6A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=dfy7kqDK; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c143si10335761pfc.197.2018.04.08.20.31.14; Sun, 08 Apr 2018 20:31:51 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=dfy7kqDK; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754382AbeDID0M (ORCPT + 99 others); Sun, 8 Apr 2018 23:26:12 -0400 Received: from mail-pf0-f196.google.com ([209.85.192.196]:36904 "EHLO mail-pf0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753904AbeDID0H (ORCPT ); Sun, 8 Apr 2018 23:26:07 -0400 Received: by mail-pf0-f196.google.com with SMTP id p6so1462646pfn.4; Sun, 08 Apr 2018 20:26:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=ojGjEp2G6gUmbq7Kwc6AeFh6cLbKWB3Nqf59cKAAelU=; b=dfy7kqDKVr8Wx/iimoFSvSk4Om3RElENoBcffCUBzVpb7GVJYA4+OuzNUD87buZDDZ Qo4yDaa+fUmXMYzAlbKJ9H085Of9psUyjKroKMxt8xJBHz8wgZSB73k4g5E97iJnwqzb Lqs6vIGsszxUeY4a39nCplV7X28MyTGXMVKt5Du/oQyo++pDUHRoxp1lTWtx0SracLg4 TdiePDSIk3kRgtdkuyLN5ysSBQWuGT0I1HLpFu7S+mKJ1YaouenGkkv3PS7yemNXlfPT +BI4Su6HgEvEtZRqdH9r0Z6hHr0sWLt1EG/RHDiEmkT0jjEdgjdJcm0WW1+HSBjA63d6 1TSA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=ojGjEp2G6gUmbq7Kwc6AeFh6cLbKWB3Nqf59cKAAelU=; b=BQpczesnHJrHmU2lfYTMQXzFFxU7c4HQdtYb0Sx+fmLm+WSJFHWqKa7yyGSiajLSvj 8RILsP1rPhVevjwXwgfNuXoywLjBQW2Qd9c7W6dg13Rgqd52wIWSn95/NOYKZlcDZLap UoC6e9Cjb+PGOhAXeDOD5+FL3DdEirq8PoKkxs8Fue0Y/chjycG/EMzhxFk/vhBEYxbE LV1mY99Ji7OFeDWILxuFNX7jKsTSOJyszWoDtNTk0hNCOVsriUyxWASIBCLo4kCAey6B y5uyRv/IsRCXsKaMWpbpe/7fkj9GiUbjnDDPDX6+IPEC2rnj/fpKJQoCwudT/fPkEDCU HM2Q== X-Gm-Message-State: AElRT7H/8GHaqYo9r2AB/LpZb907+mvCSUI8RvIgGSUWP9ifB4H6mc3D xy+sPcJKtQuvwCYq+0ZQOKtqu6KW X-Received: by 10.99.100.197 with SMTP id y188mr23529466pgb.277.1523244367373; Sun, 08 Apr 2018 20:26:07 -0700 (PDT) Received: from localhost (1-65-149-183.static.netvigator.com. [1.65.149.183]) by smtp.gmail.com with ESMTPSA id y2sm19851874pgv.38.2018.04.08.20.26.05 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 08 Apr 2018 20:26:06 -0700 (PDT) Date: Mon, 9 Apr 2018 11:26:01 +0800 From: Stefan Hajnoczi To: Pankaj Gupta Cc: David Hildenbrand , kwolf@redhat.com, haozhong zhang , jack@suse.cz, xiaoguangrong eric , kvm@vger.kernel.org, riel@surriel.com, linux-nvdimm@ml01.01.org, mst@redhat.com, ross zwisler , linux-kernel@vger.kernel.org, qemu-devel@nongnu.org, hch@infradead.org, pbonzini@redhat.com, stefanha@redhat.com, niteshnarayanlal@hotmail.com, marcel@redhat.com, imammedo@redhat.com, dan j williams , nilal@redhat.com Subject: Re: [Qemu-devel] [RFC] qemu: Add virtio pmem device Message-ID: <20180409032601.GA1648@stefanha-x1.localdomain> References: <20180405104834.10457-1-pagupta@redhat.com> <20180405104834.10457-4-pagupta@redhat.com> <416823501.16310251.1522930166070.JavaMail.zimbra@redhat.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cWoXeonUoKmBZSoM" Content-Disposition: inline In-Reply-To: <416823501.16310251.1522930166070.JavaMail.zimbra@redhat.com> User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 05, 2018 at 08:09:26AM -0400, Pankaj Gupta wrote: > > Will this raw file already have the "disk information header" (no idea > > how that stuff is called) encoded? Are there any plans/possible ways to > >=20 > > a) automatically create the headers? (if that's even possible) >=20 > Its raw. Right now we are just supporting raw format. =20 >=20 > As this is direct mapping of memory into guest address space, I don't > think we can have an abstraction of headers for block specific features. > Or may be we can get opinion of others(Qemu block people) it is at all po= ssible? memdev and the block layer are completely separate. The block layer isn't designed for memory-mapped access. I think it makes sense to use memdev here. If the user wants a block device, they should use an emulated block device, not virtio-pmem, because buffering is necessary anyway when an image file format is used. Stefan --cWoXeonUoKmBZSoM Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJayt1JAAoJEJykq7OBq3PI+GkH/1E+ci/o0GU4EORh4j1KOyFX JtWmDNcdJfKLdUonRX6ZCns34at7dTNf0U6nFlqzDB5bkMdh3H8Tid/8u57Q9MdI Y2e1Xr/IxugahIok4g5c9bN43zNWnKzGF+G/OMuCDe76oLpAm9GccKl/M2EaiXo3 rLACtHLAv+t8FNmFHw4BTz2Nt5zW6D3YiAj/M/wdk9N/z/QnbN4glWWbI8ukmNMc +e7n/yZH4TmJikN6BAvRvCrT4EemU9LpXloM5z5qXGJkJaNn+9ZQQCjwaJXdyOKt OTKLvVMdOt3x+0JxnSnisMkPtmIJtuHJY0bmjYfnrn9fh1blM9SQ8Q3nXVHQv9E= =9Dfp -----END PGP SIGNATURE----- --cWoXeonUoKmBZSoM--