All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joerg.roedel@amd.com>
To: Alexander Duyck <alexander.h.duyck@intel.com>
Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
	Jesse Brandeburg <jesse.brandeburg@intel.com>,
	Bruce Allan <bruce.w.allan@intel.com>,
	Carolyn Wyborny <carolyn.wyborny@intel.com>,
	Don Skidmore <donald.c.skidmore@intel.com>,
	Greg Rose <gregory.v.rose@intel.com>,
	Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>,
	John Ronciak <john.ronciak@intel.com>,
	<e1000-devel@lists.sourceforge.net>,
	<linux-kernel@vger.kernel.org>
Subject: Re: IO_PAGE_FAULTS with igb or igbvf on AMD IOMMU system
Date: Mon, 25 Jun 2012 13:20:45 +0200	[thread overview]
Message-ID: <20120625112045.GS2624@amd.com> (raw)
In-Reply-To: <4FE25346.901@intel.com>

Hi,
On Wed, Jun 20, 2012 at 03:48:38PM -0700, Alexander Duyck wrote:
> On 06/20/2012 02:48 AM, Joerg Roedel wrote:

> If you are working on a recent kernel you should be able to overcome the
> BIOS issues.  I believe there are the options "pci=assign-busses" if the
> BIOS doesn't place enough buses on the bridge to support SR-IOV, and
> there is "pci=realloc" which will reassign the MMIO resources to make
> enough room for VF MMIO bars.

Thanks for all your help, it turned out to be a bug in the AMD IOMMU
driver. The pdev->dev didn't get the right dma_ops struct assigned so
that mapping requests actually never made it to the IOMMU driver. This
only happened with hotplugged and VFs of SR-IOV devices. Too bad, but I
sent a fix for that and it work now again. Thanks again for your help.

Regards,

	Joerg

-- 
AMD Operating System Research Center

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


      reply	other threads:[~2012-06-25 11:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-19 10:20 IO_PAGE_FAULTS with igb or igbvf on AMD IOMMU system Joerg Roedel
2012-06-19 18:19 ` Alexander Duyck
2012-06-20  9:48   ` Joerg Roedel
2012-06-20 16:51     ` Rose, Gregory V
2012-06-20 22:48     ` Alexander Duyck
2012-06-25 11:20       ` Joerg Roedel [this message]

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=20120625112045.GS2624@amd.com \
    --to=joerg.roedel@amd.com \
    --cc=alexander.h.duyck@intel.com \
    --cc=bruce.w.allan@intel.com \
    --cc=carolyn.wyborny@intel.com \
    --cc=donald.c.skidmore@intel.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=gregory.v.rose@intel.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=john.ronciak@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.p.waskiewicz.jr@intel.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.