From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MPFhf-0003Si-7U for qemu-devel@nongnu.org; Fri, 10 Jul 2009 08:59:51 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MPFha-0003L5-EO for qemu-devel@nongnu.org; Fri, 10 Jul 2009 08:59:50 -0400 Received: from [199.232.76.173] (port=57888 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MPFha-0003Kt-9M for qemu-devel@nongnu.org; Fri, 10 Jul 2009 08:59:46 -0400 Received: from qw-out-1920.google.com ([74.125.92.144]:62089) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MPFhZ-0000s7-Sd for qemu-devel@nongnu.org; Fri, 10 Jul 2009 08:59:45 -0400 Received: by qw-out-1920.google.com with SMTP id 5so260130qwc.4 for ; Fri, 10 Jul 2009 05:59:45 -0700 (PDT) Message-ID: <4A573B3F.1010900@codemonkey.ws> Date: Fri, 10 Jul 2009 07:59:43 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 6/6] use uint32_t for ioport port and value instead of int. References: <1246530731-14597-1-git-send-email-yamahata@valinux.co.jp> <1246530731-14597-7-git-send-email-yamahata@valinux.co.jp> <4A564003.5080707@codemonkey.ws> <20090710082121.GB5471@const.bordeaux.inria.fr> <20090710084508.GM12665%yamahata@valinux.co.jp> <20090710085434.GK5471@const.bordeaux.inria.fr> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Tristan Gingold Cc: Isaku Yamahata , Samuel Thibault , qemu-devel@nongnu.org Tristan Gingold wrote: > > On Jul 10, 2009, at 10:54 AM, Samuel Thibault wrote: > >> Isaku Yamahata, le Fri 10 Jul 2009 17:45:08 +0900, a écrit : >>> void cpu_out[bwl](CPUState *env, int64_t addr, int{8, 16, 32}_t val); >> >> uint16_t addr, and uint* for val >> >>> uint{8, 16, 32}_t cpu_inw(CPUState *env, int16_t addr); >> >> uint16_t addr > > Some machines allow more than 2**16 ports (guess which :-) But I thought that PIO on ia64 ended up being MMIO or something funky like that? Would it really end up using this code path? Regards, Anthony Liguori