From: Andrew Oakley <andrew@ado.is-a-geek.net>
To: Joerg Roedel <joro@8bytes.org>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [git pull] IOMMU Updates for v3.7-rc1
Date: Wed, 10 Oct 2012 20:11:31 +0100 [thread overview]
Message-ID: <20121010201131.091d5a1f@ado-amd-gentoo.moore.slainvet.net> (raw)
In-Reply-To: <20121010133249.GC16151@8bytes.org>
On Wed, 10 Oct 2012 15:32:49 +0200
Joerg Roedel <joro@8bytes.org> wrote:
> On Wed, Oct 10, 2012 at 09:58:23AM +0100, Andrew Oakley wrote:
> > On Wed, 10 Oct 2012 09:30:22 +0200
> > Joerg Roedel <joro@8bytes.org> wrote:
>
> > AMD-Vi: DEV_SPECIAL(IOAPIC[2]) devid: 00:00.1
>
> Okay, got it. This is the problem. The device id seems to be wrong.
> The BIOS should configure your IOAPIC as device id 00:14.0 and not
> 00:00.1. The current checking code does not check for this particular
> situation. But the attached diff should change that. Can you please
> test it and reports if the machine boots for you? Interrupt remapping
> will be disabled automatically, though.
Yes, that detects the problem and disables the interrupt remapping (the
kernel boots).
If I modify the devid for the IOAPIC in init_iommu_from_acpi then it
also seems to work. I haven't managed to get vfio/qemu working yet but
it seems to be unrelated ("Invalid ROM contents", same thing happens
when I try to dump the rom with stable kernels).
Thanks
--
Andrew Oakley
next prev parent reply other threads:[~2012-10-10 19:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 15:23 [git pull] IOMMU Updates for v3.7-rc1 Joerg Roedel
2012-10-09 21:45 ` Andrew Oakley
2012-10-10 7:30 ` Joerg Roedel
2012-10-10 8:58 ` Andrew Oakley
2012-10-10 13:32 ` Joerg Roedel
2012-10-10 19:11 ` Andrew Oakley [this message]
2012-10-10 22:02 ` Andrew Oakley
2012-10-10 22:05 ` [PATCH] iommu/amd: Workaround wrong IOAPIC devid in IVRS andrew
2012-10-11 9:32 ` [git pull] IOMMU Updates for v3.7-rc1 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=20121010201131.091d5a1f@ado-amd-gentoo.moore.slainvet.net \
--to=andrew@ado.is-a-geek.net \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
/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).