From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56739) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bHW0U-0000XW-Pt for qemu-devel@nongnu.org; Mon, 27 Jun 2016 08:51:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bHW0T-0005tn-Ol for qemu-devel@nongnu.org; Mon, 27 Jun 2016 08:51:18 -0400 References: <1466740739-7240-1-git-send-email-eblake@redhat.com> <1466740739-7240-3-git-send-email-eblake@redhat.com> <5a03a995-2be3-66cc-89af-c3b4f42c3568@redhat.com> From: Eric Blake Message-ID: <5771213C.5090209@redhat.com> Date: Mon, 27 Jun 2016 06:51:08 -0600 MIME-Version: 1.0 In-Reply-To: <5a03a995-2be3-66cc-89af-c3b4f42c3568@redhat.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="e2n5hR5MbFKAE41E9l0O5L0uR8VmcvmA5" Subject: Re: [Qemu-devel] [PATCH 2/2] raw_bsd: Convert to byte-based interface List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini , qemu-devel@nongnu.org Cc: qemu-block@nongnu.org, kwolf@redhat.com, Max Reitz This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --e2n5hR5MbFKAE41E9l0O5L0uR8VmcvmA5 From: Eric Blake To: Paolo Bonzini , qemu-devel@nongnu.org Cc: qemu-block@nongnu.org, kwolf@redhat.com, Max Reitz Message-ID: <5771213C.5090209@redhat.com> Subject: Re: [PATCH 2/2] raw_bsd: Convert to byte-based interface References: <1466740739-7240-1-git-send-email-eblake@redhat.com> <1466740739-7240-3-git-send-email-eblake@redhat.com> <5a03a995-2be3-66cc-89af-c3b4f42c3568@redhat.com> In-Reply-To: <5a03a995-2be3-66cc-89af-c3b4f42c3568@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 06/27/2016 06:19 AM, Paolo Bonzini wrote: >=20 >=20 > On 24/06/2016 05:58, Eric Blake wrote: >> Since the raw format driver is just passing things through, we can >> do byte-based read and write if the underlying protocol does >> likewise. >> >> There's one tricky part - if we probed the image format, we document >> that we restrict operations on the initial sector. Rather than >> trying to handle a read-modify-write on the first sector, it's >> easiest to just include in our restrictions that partial writes to >> the first sector are not permitted. >=20 > Can we just set the alignment to at least 512 if probed? It's the > practical guest alignment anyway. Interesting idea; should be fairly easy to attempt. --=20 Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org --e2n5hR5MbFKAE41E9l0O5L0uR8VmcvmA5 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Public key at http://people.redhat.com/eblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJXcSE8AAoJEKeha0olJ0Nq2v4H/1GlVFIYSIXE5a+EIwfasbtJ Eme5iKkW5biKc58LuQjoy3MeNJ9/6Ai9MMTzeAzXEkmIlwbwogg7rmgC7Bc73XQj FaWcqFPtiaLvePXou070BaZO3xTejh0YZeP0gxbZkS6Abv27Of2TIBR397rHlOZm 5AKel2HZo1xZe26ReyODySuskoc1JSTf6E7ij79703/QfF6+uAlqiudAAGfyJkWM NA62Q71R4iu0iNTWh+PhOJJ/6LCT5jBe+y7JGEmDY/iW48WEk0/68oQmlLMqMaK2 Eep3dVieychCdk1OH695IU4pDepUmh4VVIdxmVxLKPMHUV2V2eRJ5+Sp8cW+Jd8= =XNer -----END PGP SIGNATURE----- --e2n5hR5MbFKAE41E9l0O5L0uR8VmcvmA5--