From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MsX1z-00070z-2A for qemu-devel@nongnu.org; Tue, 29 Sep 2009 03:21:51 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MsX1u-0006ua-6B for qemu-devel@nongnu.org; Tue, 29 Sep 2009 03:21:50 -0400 Received: from [199.232.76.173] (port=46246 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MsX1t-0006uG-W5 for qemu-devel@nongnu.org; Tue, 29 Sep 2009 03:21:46 -0400 Received: from mx20.gnu.org ([199.232.41.8]:4481) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MsX1t-0005iE-K6 for qemu-devel@nongnu.org; Tue, 29 Sep 2009 03:21:45 -0400 Received: from mx1.redhat.com ([209.132.183.28]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MsX1s-0002rL-NZ for qemu-devel@nongnu.org; Tue, 29 Sep 2009 03:21:45 -0400 Date: Tue, 29 Sep 2009 09:19:45 +0200 From: "Michael S. Tsirkin" Subject: Re: [Qemu-devel] Re: [PATCHv2] qemu: target library, use it in msix Message-ID: <20090929071945.GD25389@redhat.com> References: <20090927082020.GA23513@redhat.com> <4ABF4110.80300@redhat.com> <20090927114459.GA24031@redhat.com> <4ABF52A5.5080409@redhat.com> <20090927120041.GB24031@redhat.com> <4ABF585D.7000201@redhat.com> <20090927140841.GA24769@redhat.com> <4ABF7359.8050404@redhat.com> <20090927142129.GA24851@redhat.com> <4ABF7619.7000103@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4ABF7619.7000103@redhat.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Blue Swirl , qemu-devel@nongnu.org On Sun, Sep 27, 2009 at 04:26:33PM +0200, Avi Kivity wrote: > On 09/27/2009 04:21 PM, Michael S. Tsirkin wrote: >> >>> How can the caller (except in your special case) know if it has a >>> quantity that will fit in 32 bits? >>> >> It's actually not unusual for devices to limit addressing to 32 bit, whatever >> the bus supports. For example, the value might come from a 32 bit pci >> bar, even on a 64 bit system this will get values 0 to 4G. >> > > What if the caller is a device that doesn't intentionally cripple itself? That will need a 64 bit version, even if target is 32 bit. > -- > Do not meddle in the internals of kernels, for they are subtle and quick to panic.