From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36162) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eZBz0-0005on-KZ for qemu-devel@nongnu.org; Wed, 10 Jan 2018 03:43:39 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eZByz-0006h1-Pr for qemu-devel@nongnu.org; Wed, 10 Jan 2018 03:43:38 -0500 References: <20180108231048.23966-1-laurent@vivier.eu> <20180108231048.23966-2-laurent@vivier.eu> From: David Hildenbrand Message-ID: <66de9088-f8ed-2be4-c71a-5d149c63587b@redhat.com> Date: Wed, 10 Jan 2018 09:43:23 +0100 MIME-Version: 1.0 In-Reply-To: <20180108231048.23966-2-laurent@vivier.eu> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [qemu-s390x] [PATCH 1/6] accel/tcg: add size paremeter in tlb_fill() List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Laurent Vivier , qemu-devel@nongnu.org Cc: Peter Maydell , Eduardo Habkost , qemu-s390x@nongnu.org, Bastian Koppelmann , Anthony Green , Chris Wulff , Richard Henderson , Alexander Graf , Max Filippov , Michael Walle , qemu-arm@nongnu.org, qemu-ppc@nongnu.org, Artyom Tarasenko , Paolo Bonzini , "Edgar E . Iglesias" , Stafford Horne , Guan Xuetao , Aurelien Jarno On 09.01.2018 00:10, Laurent Vivier wrote: > The MC68040 MMU provides the size of the access that > triggers the page fault. > > This size is set in the Special Status Word which > is written in the stack frame of the access fault > exception. > > So we need the size in m68k_cpu_unassigned_access() and > m68k_cpu_handle_mmu_fault(). > > To be able to do that, this patch modifies the prototype of > handle_mmu_fault handler, tlb_fill() and probe_write(). > do_unassigned_access() already includes a size parameter. > > This patch also updates handle_mmu_fault handlers and > tlb_fill() of all targets (only parameter, no code change). > There are a couple of places where you use "1" (when no other size is available). e.g. in get_page_addr_code(). Wonder if that's the right thing to do - are there any architectures that e.g. always fetch at least 2 bytes in these conditions? Apart from that, looks sane to me (for other architectures :) ) -- Thanks, David / dhildenb