From: "Roedel, Joerg" <Joerg.Roedel@amd.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>
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 [thread overview]
Message-ID: <20110207170330.GR2106@amd.com> (raw)
In-Reply-To: <20110207164133.GD18151@dumpdata.com>
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
next prev parent reply other threads:[~2011-02-07 17:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 18:58 AMD_IOV: IO_PAGE_FALT trying to pass through Mellanox ConnectX HCA (debian testing) Ward Vandewege
2011-01-28 19:27 ` Konrad Rzeszutek Wilk
2011-01-28 20:38 ` Ward Vandewege
2011-01-31 18:45 ` Konrad Rzeszutek Wilk
2011-01-31 19:51 ` Ward Vandewege
2011-01-31 20:03 ` Konrad Rzeszutek Wilk
2011-02-03 23:24 ` Ward Vandewege
2011-02-07 16:41 ` Konrad Rzeszutek Wilk
2011-02-07 17:03 ` Roedel, Joerg [this message]
2011-02-07 17:42 ` Ward Vandewege
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110207170330.GR2106@amd.com \
--to=joerg.roedel@amd.com \
--cc=joro@8bytes.org \
--cc=konrad.wilk@oracle.com \
--cc=ward@gnu.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.