On Tue, Sep 18, 2012 at 8:56 PM, Devin Heitmueller
wrote:
>> You can see the original thread where this was found, together with a
>> working patch, here:
>>
>> http://lists.xen.org/archives/html/xen-devel/2012-01/msg01927.html
>
> As far as I can read, the patch has never been confirmed to work.
On Tue, Sep 18, 2012 at 2:34 PM, Javier Marcet wrote:
> I can't say how happy I am that you were wrong in your guess. Quoting
> Konrad Rzeszutek Wilk:
Well, you haven't proven me wrong yet. :-)
> """
> The issue as I understand is that the DVB drivers allocate their
> buffers from 0->4GB most (
On Tue, Sep 18, 2012 at 5:40 AM, Devin Heitmueller
wrote:
Hi Devin,
> This is a very common problem when attempting to use any PCI/PCIe
> tuner under a hypervisor. Essentially the issue is all of the
> virtualization solutions provide very poor interrupt latency, which
> results in the data bei
On Tue, Sep 18, 2012 at 5:40 AM, Devin Heitmueller
wrote:
>> Initially I thought Xen would be the cause of the problem, but after
>> having written on
>> the Xen development mailing list and talked about it with a couple
>> developers, it isn't
>> very clear where the problem is. So far I haven't
On Mon, Sep 17, 2012 at 8:05 PM, Javier Marcet wrote:
> Initially I thought Xen would be the cause of the problem, but after
> having written on
> the Xen development mailing list and talked about it with a couple
> developers, it isn't
> very clear where the problem is. So far I haven't been able
Hi,
I recently began to investigate the Xen hypervisor. One key piece of
the server I'm
using is its DVB tuners. I'm using a Terratec Cinergy T PCIe Dual.
When running on bare metal it works relatively well (it has other bugs
I'll report later),
but when running on a dom0 under the Xen hypervisor