All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amit Shah <amit.shah@redhat.com>
To: Zwane Mwaikambo <zwane@infradead.org>
Cc: "Han, Weidong" <weidong.han@intel.com>, kvm@vger.kernel.org
Subject: Re: PCI passthrough = NMIs
Date: Wed, 15 Oct 2008 15:20:20 +0530	[thread overview]
Message-ID: <200810151520.20675.amit.shah@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0810141013210.24124@montezuma.windriver.com>

* On Tuesday 14 Oct 2008 22:46:37 Zwane Mwaikambo wrote:
> On Tue, 14 Oct 2008, Han, Weidong wrote:
> > Zwane Mwaikambo wrote:
> > > Hi,
> > > 	I've been trying to get a Linux guest working with PCI
> >
> > passthrough
> >
> > > of an ethernet card using the vtd branches. The device detection
> > > works and the guest reports a link, however as soon as i try and ping
> > > the guest it receives an NMI (i'm guessing this is PCI DMA related).
> > > Interrupt delivery to the guest looks fine (count increases at a low
> > > rate) and isn't shared with anything else on the host.
> > >
> > > Thanks for any hints.
> > >
> > > 	Zwane
> >
> > What do you mean "vtd branches"? Is it the vtd branch of Amit's tree?
> >
> > VT-d patches are in kvm.git, as long as you apply amit's userspace patch
> > (you can find it on mailing list), you should can assign device to
> > guest. Make sure you enable VT-d in BIOS and set CONFIG_DMAR in config,
> > and remove device driver before you assign device. NIC and USB
> > controller assignment works fine for me.
>
> I'm using the following repositories without any additional patches;
>
> git://git.kernel.org/pub/scm/linux/kernel/git/amit/kvm.git vtd
> git://git.kernel.org/pub/scm/linux/kernel/git/amit/kvm-userspace.git vtd

Can you try using Avi's kvm.git tree and the userspace tree same as above 
(it's been updated now and you'll have to use +vtd as the branch)?

That's the newest code; though I'm not sure if it will solve your problem.

> The host kernel only has the e100 network driver enabled, the guest kernel
> only has the e1000 network driver enabled. I have enabled VT-d in the BIOS
> and enabled CONFIG_DMAR in the host kernel config. I'm really beginning to
> suspect the BIOS unfortunately :(

Amiit.

      reply	other threads:[~2008-10-15  9:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-13  6:09 PCI passthrough = NMIs Zwane Mwaikambo
2008-10-13  6:35 ` Muli Ben-Yehuda
2008-10-13 15:04   ` Zwane Mwaikambo
2008-10-14  3:08     ` Sheng Yang
2008-10-14  4:39       ` Zwane Mwaikambo
2008-10-14  7:16         ` Sheng Yang
2008-10-14  7:33 ` Han, Weidong
2008-10-14 17:16   ` Zwane Mwaikambo
2008-10-15  9:50     ` Amit Shah [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=200810151520.20675.amit.shah@redhat.com \
    --to=amit.shah@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=weidong.han@intel.com \
    --cc=zwane@infradead.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 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.