From: Jan Kiszka <jan.kiszka@web.de>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: Device assignment, shared IRQs, uio_pci_generic
Date: Mon, 01 Nov 2010 12:27:06 +0100 [thread overview]
Message-ID: <4CCEA40A.1010004@web.de> (raw)
In-Reply-To: <4CCD85B7.1030904@web.de>
[-- Attachment #1: Type: text/plain, Size: 966 bytes --]
Am 31.10.2010 16:05, Jan Kiszka wrote:
> Still not working here are ehci, ath9k and e1000e when passed through.
> They receive IRQs, but somehow the Linux guest drivers are unhappy about
> the device states (the e1000e detects "Hardware Unit Hang" e.g.). This
> is independent of my patches. Anyone any ideas? Improper configurations
> of the BIOS? I stumbled over this in the kernel log:
>
> DMAR: BIOS has allocated no shadow GTT; disabling IOMMU for graphics
>
Argh, no one told me that there is CONFIG_DMAR_DEFAULT_ON and that you
have to pass "intel_iommu=on" if that config switch is off like here.
Moreover, I somehow assumed "iommu=0" on the command line means "use
IOMMU with index 0" (don't ask me why). Usability deserves some patches
- later.
So it's starting to work, already accessed some devices (ath9k did a
successful scan), but now it's crashing in intel_iommu_attach_device.
Looks like use after release. Sigh.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
prev parent reply other threads:[~2010-11-01 11:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-30 15:58 Device assignment, shared IRQs, uio_pci_generic Jan Kiszka
2010-10-30 17:06 ` Alex Williamson
2010-10-31 15:05 ` Jan Kiszka
2010-11-01 11:27 ` Jan Kiszka [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=4CCEA40A.1010004@web.de \
--to=jan.kiszka@web.de \
--cc=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.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.