From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:41794) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1abUVa-00073z-UD for qemu-devel@nongnu.org; Thu, 03 Mar 2016 09:45:43 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1abUVX-0004Qn-Ii for qemu-devel@nongnu.org; Thu, 03 Mar 2016 09:45:42 -0500 References: <1456392739-30336-1-git-send-email-caoj.fnst@cn.fujitsu.com> <56CF020A.8030704@cn.fujitsu.com> From: Paolo Bonzini Message-ID: <56D84E0E.5000801@redhat.com> Date: Thu, 3 Mar 2016 15:45:34 +0100 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] doc/memory.txt: fix typo List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell , Cao jin Cc: QEMU Trivial , QEMU Developers On 25/02/2016 15:24, Peter Maydell wrote: > Probably what happened > was that when the API was being designed it started off with an > 'unaligned' field, and then later the field name and semantics > were changed but the docs weren't updated to match. My point was > that just changing the name without looking at the behaviour we're > actually implementing isn't correct. Peter, are you okay with adding your S-o-b and authorship to this patch? I'll add a Reported-by for Cao jin, too. Paolo diff --git a/docs/memory.txt b/docs/memory.txt index d0aca05..e44d081 100644 --- a/docs/memory.txt +++ b/docs/memory.txt @@ -297,8 +297,9 @@ various constraints can be supplied to control how these callbacks are called: - .valid.min_access_size, .valid.max_access_size define the access sizes (in bytes) which the device accepts; accesses outside this range will have device and bus specific behaviour (ignored, or machine check) - - .valid.aligned specifies that the device only accepts naturally aligned - accesses. Unaligned accesses invoke device and bus specific behaviour. + - .valid.unaligned specifies that the *device being modelled* supports + unaligned accesses; if false, unaligned accesses will invoke the + appropriate bus or CPU specific behaviour. - .impl.min_access_size, .impl.max_access_size define the access sizes (in bytes) supported by the *implementation*; other access sizes will be emulated using the ones available. For example a 4-byte write will be @@ -307,4 +308,4 @@ various constraints can be supplied to control how these callbacks are called: accesses; if false, unaligned accesses will be emulated by two aligned accesses. - .old_mmio can be used to ease porting from code using - cpu_register_io_memory(). It should not be used in new code. + cpu_register_io_memory() and the like. It should not be used in new code.