linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Oakley <andrew@ado.is-a-geek.net>
To: Andrew Oakley <andrew@ado.is-a-geek.net>
Cc: Joerg Roedel <joro@8bytes.org>,
	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 23:02:31 +0100	[thread overview]
Message-ID: <20121010230231.2fb3c3b9@ado-amd-gentoo.moore.slainvet.net> (raw)
In-Reply-To: <20121010201131.091d5a1f@ado-amd-gentoo.moore.slainvet.net>

On Wed, 10 Oct 2012 20:11:31 +0100
Andrew Oakley <andrew@ado.is-a-geek.net> wrote:
> 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).

I've now managed to get a network card passed through and working
properly in a guest.  The bug has been reported to the vendor so
hopefully it will get fixed in a BIOS update.

I'm not sure if the fix I've got is safe or if it's really a good idea
to enable interrupt remapping with a broken BIOS.

Thanks

-- 
Andrew Oakley

  reply	other threads:[~2012-10-10 22:02 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
2012-10-10 22:02           ` Andrew Oakley [this message]
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=20121010230231.2fb3c3b9@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).