All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Michael A. Collins" <mike@ark-net.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: Intel S3420GPLX VT-d VF question
Date: Wed, 8 Dec 2010 11:32:18 -0500	[thread overview]
Message-ID: <20101208163217.GA18739@dumpdata.com> (raw)
In-Reply-To: <30410a64d335f82097af217b0ed7d060@mail.ark-net.org>

On Tue, Dec 07, 2010 at 11:52:24PM -0500, Michael A. Collins wrote:
> I have successfully booted xen on Fedora 14 x86_64 with iommu=force

Ok.. Um, what Fedora kernel are we taking about here? Do you have
the full serial log?
> on the kernel line, I can unbind a pci device and rebind to pci-stub
> and see it with xm pci-list-assignable-devices.  That's cool.  Now I
> have an Intel 82576 dual-port ET Adapter that supports SR-IOV and
> started configuring everything to enable it's virtual functions:
> added pci_pt_e820_access=on to the module line that contains the
> vmlinuz

Why? It doesn't automatically load without that parameter?
> created igb.conf under /etc/modprobe.d with options igb max_vfs=7
> added blacklist igbvf to /etc/modprobe.d/blacklist.conf

Why blacklist it?
> 
> I was under the impression that I should see some kind of message
> about MMCONFIG in xm dmesg, but there isn't anything.  I do a xm
> dmesg | grep -i pci and it finds nothing with MMCONFIG.  I guess my

Huh? Why? Do you see the 7 ethernet PCI device being created?

> next question is what do I do next?  How do I troubleshoot further?

What are you trying to troubleshoot? Did you lspci output change
after you loaded the igbvf?

> Below is the VT-d messages from xm dmesg:
> (XEN) Intel VT-d Snoop Control supported.
> (XEN) Intel VT-d DMA Passthrough not supported.
> (XEN) Intel VT-d Queued Invalidation supported.
> (XEN) Intel VT-d Interrupt Remapping not supported.
> 
> Does MMCONFIG have something to do with the fact the Interrupt
> Remapping not supported message is displayed?

No. It just means your VT-D chipset does not support interrupt
remapping.

> Mike
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  reply	other threads:[~2010-12-08 16:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-08  4:52 Intel S3420GPLX VT-d VF question Michael A. Collins
2010-12-08 16:32 ` Konrad Rzeszutek Wilk [this message]
2010-12-08 17:12   ` Michael A. Collins
2010-12-08 17:50     ` Konrad Rzeszutek Wilk
2010-12-09 13:26       ` Michael A. Collins
2010-12-10  3:18       ` Michael A. Collins
2010-12-21  2:24         ` Michael A. Collins
2010-12-22 20:10           ` Konrad Rzeszutek Wilk
2010-12-23  0:47             ` Michael A. Collins
2010-12-24  5:38           ` Zhuo Song
2010-12-27  0:49             ` Michael A. Collins
2010-12-30  3:19               ` Zhuo Song
2010-12-18  4:42       ` Michael A. Collins

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=20101208163217.GA18739@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=mike@ark-net.org \
    --cc=xen-devel@lists.xensource.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.