From: Joerg Roedel <joro@8bytes.org>
To: Shuah Khan <shuahkhan@gmail.com>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
Joerg Roedel <joerg.roedel@amd.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
Shuah Khan <shuah.khan@hp.com>
Subject: Re: [PATCH] iommu: moving initialization earlier
Date: Fri, 11 Jan 2013 15:50:59 +0100 [thread overview]
Message-ID: <20130111145059.GJ25591@8bytes.org> (raw)
In-Reply-To: <CAKocOOP=V=kZ=4661YSs4b+7GLcNqzVvvhb+ONBO=LiR3txvTA@mail.gmail.com>
On Thu, Jan 10, 2013 at 01:40:17PM -0700, Shuah Khan wrote:
> I am currently debugging IO_PAGE_FAULTS on 3.6.11 (happens on all
> pre-3.7 releases). I root-caused the reason 3.7 works is because in
> 3.7 amd iommu driver moving up the early iommu initialization from
> irq_remap_ops with the irq remapping feature.
Have you investigated the reason for those IO_PAGE_FAULTS? I guess they
come from the USB controlers and happen between the time the IOMMU is
enabled and the USB controlers are taken over by the Linux kernel from
the BIOS.
But I don't see why this patch can have any impact on the IO_PAGE_FAULTS
you are seeing.
Joerg
next prev parent reply other threads:[~2013-01-11 14:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 7:51 [PATCH] iommu: moving initialization earlier Alexey Kardashevskiy
2013-01-10 17:09 ` Joerg Roedel
2013-01-10 20:40 ` Shuah Khan
2013-01-10 23:16 ` Shuah Khan
2013-01-11 14:50 ` Joerg Roedel [this message]
2013-01-11 16:56 ` Shuah Khan
-- strict thread matches above, loose matches on Subject: below --
2012-12-13 2:29 [PATCH] vfio powerpc: enabled on powernv platform Benjamin Herrenschmidt
2012-12-13 6:28 ` [PATCH] iommu: moving initialization earlier Alexey Kardashevskiy
2012-12-13 15:48 ` Alex Williamson
2012-12-16 11:20 ` Joerg Roedel
2013-01-04 8:21 ` Alexey Kardashevskiy
2013-01-06 9:49 ` Joerg Roedel
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=20130111145059.GJ25591@8bytes.org \
--to=joro@8bytes.org \
--cc=aik@ozlabs.ru \
--cc=benh@kernel.crashing.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joerg.roedel@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shuah.khan@hp.com \
--cc=shuahkhan@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).