xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen 4.4 development update: Is PVH a blocker?
Date: Mon, 16 Dec 2013 10:09:06 -0500	[thread overview]
Message-ID: <20131216150906.GA14038@phenom.dumpdata.com> (raw)
In-Reply-To: <10210502196.20131213215514@eikelenboom.it>

> >> * qemu-upstream not freeing pirq
> >>  > http://www.gossamer-threads.com/lists/xen/devel/281498
> >>  > http://marc.info/?l=xen-devel&m=137265766424502
> >>  status: patches posted; latest patches need testing
> >>  Not a blocker.
> 
> > I can't test it, b/c qemu-upstream does not work with PCI passthrough
> > anymore.
> 
> Strange, pci passthrough in general works for me on "simple" pci devices (usb cards, videograbber) with latest qemu-upstream and seabios upstream.
> (if you have no need for pci rombars, no vga passthrough, no need for specifying funky things about which virtual functions to passthrough)
> 
> What are you trying to passthrough ?

-bash-4.1# lspci -s 01:00.0 -v 
01:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
        Subsystem: Intel Corporation Gigabit ET Dual Port Server Adapter
        Flags: fast devsel, IRQ 16
        Memory at fbc20000 (32-bit, non-prefetchable) [disabled] [size=128K]
        Memory at fb800000 (32-bit, non-prefetchable) [disabled] [size=4M]
        I/O ports at e020 [disabled] [size=32]
        Memory at fbc44000 (32-bit, non-prefetchable) [disabled] [size=16K]
        Expansion ROM at fb400000 [disabled] [size=4M]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
        Capabilities: [70] MSI-X: Enable- Count=10 Masked-
        Capabilities: [a0] Express Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Device Serial Number 00-1b-21-ff-ff-45-d9-ac
        Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
        Capabilities: [160] Single Root I/O Virtualization (SR-IOV)
        Kernel driver in use: pciback
        Kernel modules: igb


> What problems do you have / errors do you see ?
> 

http://www.gossamer-threads.com/lists/xen/devel/309476?do=post_view_threaded

  reply	other threads:[~2013-12-16 15:09 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-13 19:21 Xen 4.4 development update: Is PVH a blocker? George Dunlap
2013-12-13 19:39 ` Konrad Rzeszutek Wilk
2013-12-13 20:55   ` Sander Eikelenboom
2013-12-16 15:09     ` Konrad Rzeszutek Wilk [this message]
2013-12-16 17:24       ` Sander Eikelenboom
2013-12-16 17:46         ` Konrad Rzeszutek Wilk
2013-12-16 17:59           ` Sander Eikelenboom
2013-12-16 19:34             ` Konrad Rzeszutek Wilk
2013-12-16 19:46               ` Sander Eikelenboom
2013-12-17 14:35                 ` Konrad Rzeszutek Wilk
2013-12-17 15:03                   ` Sander Eikelenboom
2013-12-17 21:35                     ` Konrad Rzeszutek Wilk
2013-12-17 21:52                       ` Sander Eikelenboom
2013-12-17 15:04               ` Anthony Liguori
2013-12-17 15:18                 ` Konrad Rzeszutek Wilk
2013-12-16 10:51   ` Ian Campbell
2013-12-16 15:12     ` Konrad Rzeszutek Wilk
2013-12-16 15:24       ` Konrad Rzeszutek Wilk
2013-12-16 15:43       ` Ian Campbell
2013-12-13 19:43 ` Konrad Rzeszutek Wilk
2013-12-16 10:50   ` George Dunlap
2013-12-16 10:54   ` Ian Campbell
2013-12-16 15:10     ` Konrad Rzeszutek Wilk
2013-12-19 14:06   ` Ian Campbell
2013-12-19 14:15     ` Processed: " xen
2013-12-16  8:47 ` Jan Beulich
2013-12-16 23:45   ` Mukesh Rathor
2013-12-17  8:25     ` Jan Beulich
2013-12-17 11:58   ` Tim Deegan
2013-12-17 14:13     ` George Dunlap

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=20131216150906.GA14038@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=linux@eikelenboom.it \
    --cc=xen-devel@lists.xen.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).