All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Sander Eikelenboom <linux@eikelenboom.it>,
	Jiang Liu <jiang.liu@linux.intel.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: <xen-devel@lists.xenproject.org>, <linux-kernel@vger.kernel.org>
Subject: Re: 3.19-rc4: Xen pci-passthrough regression, bisected to commit cffe0a2b5a34c95a4dadc9ec7132690a5b0f6687 "x86, irq: Keep balance of IOAPIC pin reference count"
Date: Wed, 14 Jan 2015 14:58:33 +0000	[thread overview]
Message-ID: <54B68419.9010503@citrix.com> (raw)
In-Reply-To: <74756708.20150114151521@eikelenboom.it>

On 14/01/15 14:15, Sander Eikelenboom wrote:
> Hi Gerry / David / Konrad,
> 
> Some more testing uncovered another issue under Xen, this time with PCI-passthrough.

What device?  In particular what interrupts is it using?

> I have bisected it to the following commit: 
> cffe0a2b5a34c95a4dadc9ec7132690a5b0f6687 "x86, irq: Keep balance of IOAPIC pin reference count"
> 
> It causes these symptoms:
> 
> - On Intel
>   - Running on Xen with pci devices seized on host boot with xen-pciback.hide= parameter
>   - Running a HVM guest with PCI passthrough of two devices (NIC + wireless NIC)
>   - While the driver loads fine, the device isn't working properly, looking in /proc/interrupts in the guest
>     shows that it doesn't receive any interrupts.
>   - Reverting this particular commit (in the dom0 kernel only) makes the device receive interrupts and work properly again.
> 
> - On AMD (more subtle symptom) 
>   - Running on Xen with pci devices seized on host boot with xen-pciback.hide= parameter
>   - Running a HVM guest with PCI passthrough of one devices (videograbber)
>   - While the driver loads fine and the device looks like it's working, the videostream isn't stable and it skips or repeats frames.
>   - Reverting this particular commit (in the dom0 kernel only) makes the device work properly again with a stable videostream.
> 
> --
> Sander
> 


  reply	other threads:[~2015-01-14 14:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-14 14:15 3.19-rc4: Xen pci-passthrough regression, bisected to commit cffe0a2b5a34c95a4dadc9ec7132690a5b0f6687 "x86, irq: Keep balance of IOAPIC pin reference count" Sander Eikelenboom
2015-01-14 14:58 ` David Vrabel [this message]
2015-01-14 16:17   ` Sander Eikelenboom
2015-01-14 16:17   ` Sander Eikelenboom
2015-01-15 11:20     ` Jiang Liu
2015-01-15 11:20     ` Jiang Liu
2015-01-14 14:58 ` David Vrabel
  -- strict thread matches above, loose matches on Subject: below --
2015-01-14 14:15 Sander Eikelenboom

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=54B68419.9010503@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=jiang.liu@linux.intel.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@eikelenboom.it \
    --cc=xen-devel@lists.xenproject.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.