From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54398) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gaOnN-0007DF-TZ for qemu-devel@nongnu.org; Fri, 21 Dec 2018 12:41:10 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gaOnK-0007y6-K2 for qemu-devel@nongnu.org; Fri, 21 Dec 2018 12:41:09 -0500 Received: from mga06.intel.com ([134.134.136.31]:52769) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gaOnK-0007x3-9N for qemu-devel@nongnu.org; Fri, 21 Dec 2018 12:41:06 -0500 Date: Sat, 22 Dec 2018 01:37:58 +0800 From: Yu Zhang Message-ID: <20181221173758.4ohku43as4dkb355@linux.intel.com> References: <1544619939-18102-2-git-send-email-yu.c.zhang@linux.intel.com> <20181217141740.16ccfaa1@Igors-MacBook-Pro.local> <20181218092723.yhaerzm4vlzgef65@linux.intel.com> <20181218155536.2b35a037@Igors-MacBook-Pro.local> <20181219025717.6m72hq73p2haexkv@linux.intel.com> <20181219114037.5550a562@redhat.com> <20181220211801.GR19442@habkost.net> <20181221151325.39b64733@redhat.com> <20181221160944.65c5skjhkel3of7y@linux.intel.com> <20181221120320-mutt-send-email-mst@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181221120320-mutt-send-email-mst@kernel.org> Subject: Re: [Qemu-devel] [PATCH v3 1/2] intel-iommu: differentiate host address width from IOVA address width. List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: Igor Mammedov , Eduardo Habkost , qemu-devel@nongnu.org, Peter Xu , Paolo Bonzini , Richard Henderson On Fri, Dec 21, 2018 at 12:04:49PM -0500, Michael S. Tsirkin wrote: > On Sat, Dec 22, 2018 at 12:09:44AM +0800, Yu Zhang wrote: > > Well, my understanding of the vt-d spec is that the address limitation in > > DMAR are referring to the same concept of CPUID.MAXPHYSADDR. I do not think > > there's any different in the native scenario. :) > > I think native machines exist on which the two values are different. > Is that true? I think the answer is not. My understanding is that HAW(host address wdith) is the maximum physical address width a CPU can detects(by cpuid.0x80000008). I agree there are some addresses the CPU does not touch, but they are still in the physical address space, and there's only one physical address space... B.R. Yu