From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:45871) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YhaS2-0004wI-BN for qemu-devel@nongnu.org; Mon, 13 Apr 2015 05:14:47 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YhaDY-000822-SD for qemu-devel@nongnu.org; Mon, 13 Apr 2015 04:59:47 -0400 Received: from mail.emea.novell.com ([130.57.118.101]:50440) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yha1h-0001Iy-76 for qemu-devel@nongnu.org; Mon, 13 Apr 2015 04:47:29 -0400 Message-Id: <552B9EBE02000078000715AC@mail.emea.novell.com> Date: Mon, 13 Apr 2015 09:47:26 +0100 From: "Jan Beulich" References: <55159192020000780006EBB7@mail.emea.novell.com> <55191C34.2000807@redhat.com> In-Reply-To: <55191C34.2000807@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: Re: [Qemu-devel] MemoryRegionOps' {min,max}_access_size fields List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: qemu-devel@nongnu.org >>> On 30.03.15 at 11:49, wrote: > On 27/03/2015 17:21, Jan Beulich wrote: >> And then the way access_with_adjusted_size() works, it looks to >> me as if with .impl.min_access_size set to greater than 1 >> unaligned accesses could still reach the actual read or write >> handler, as only the access size would get bumped, but no >> adjustment be made to the address. >=20 > I don't understand what you mean exactly. Do you have an example? access_size_min =3D 4 together with size =3D 1 yield access_size =3D 4, but for a not 4-byte-aligned address (which still is properly aligned for the original 1-byte access) access() will be called with a mis- aligned address/size pair. Jan