From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Roedel, Joerg" <Joerg.Roedel@amd.com>
Subject: Re: AMD_IOV: IO_PAGE_FALT trying to pass through
	Mellanox ConnectX HCA (debian testing)
Date: Mon, 7 Feb 2011 18:03:31 +0100
Message-ID: <20110207170330.GR2106@amd.com>
References: <20110128185809.GA24465@countzero.vandewege.net>
	<20110128192742.GB23494@dumpdata.com>
	<20110128203858.GA26814@countzero.vandewege.net>
	<20110131184503.GB11939@dumpdata.com>
	<20110131195154.GA19572@countzero.vandewege.net>
	<20110131200322.GA30160@dumpdata.com>
	<20110203232433.GA6745@countzero.vandewege.net>
	<20110207164133.GD18151@dumpdata.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <20110207164133.GD18151@dumpdata.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "joro@8bytes.org" <joro@8bytes.org>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, Ward Vandewege <ward@gnu.org>
List-Id: xen-devel@lists.xenproject.org

On Mon, Feb 07, 2011 at 11:41:33AM -0500, Konrad Rzeszutek Wilk wrote:
> Any idea what this error might signify?
> > (XEN) AMD_IOV: IO_PAGE_FALT: domain:3, device id:0x200, fault address:0x7e7ca000
> > (XEN) AMD_IOV: IO_PAGE_FALT: domain:3, device id:0x200, fault address:0x7e7ca040
> > (XEN) AMD_IOV: IO_PAGE_FALT: domain:3, device id:0x200, fault address:0x7e7ca080
> > (XEN) AMD_IOV: IO_PAGE_FALT: domain:3, device id:0x200, fault address:0x7e7ca0c0
> 
> We have been stabing in the dark enabling certain knobs, .. but I am
> just curious - the fault address - that is the real physical address right?
> From the looks of it looks like a normal RAM region, not the PCI BAR space - the
> AMD VI chipset doesn't really distinguish between those, or does it?

The fault-address is io-virtual, so this is not a ram physical address.
Basically this is the address the device sent a request to and which the
IOMMU tried to re-map. You should look into the guest memory layout to
find out what might be at those addresses.

		Joerg

-- 
AMD Operating System Research Center

Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632