From: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
To: Andy Clayton <xen.nospam@q3aiml.net>
Cc: Jason <xen@jasonandjessi.com>, xen-devel@lists.xensource.com
Subject: Re: IVTV and Xen
Date: Mon, 1 May 2006 07:45:35 +0100 [thread overview]
Message-ID: <3ac635b4dd93e7696042238ab96f940b@cl.cam.ac.uk> (raw)
In-Reply-To: <44559A93.7050504@q3aiml.net>
On 1 May 2006, at 06:20, Andy Clayton wrote:
>> Has anyone had any luck getting IVTV .61 working in xen (Im on 3.0
>> unstable changeset Fri Mar 31
>> 00:26:07 2006 +0100 9494:8a8361994904 because of some unrelated
>> driver issues with another device).
>> I keep getting a DMA issue. If this is fixed in a later rev, I will
>> upgrade but that will be a
>> pretty major undertaking on this particular machine, so I thought I
>> would ask for others experience
>> first. This is what I get when the module inserts, this ia DomU
>> kernel BTW.
>>
> It has been a while, but I think I had a similar error with ivtv that
> could be fixed by passing "swiotlb=force" to the kernel (extra in the
> configs). This was with an unstable changeset in between 3.0.1 and
> 3.0.2.
We've never enabled swiotlb by default for domUs, even when they're
driver domains. So you will definitely need 'swiotlb=force'. You could
try 'swiotlb=16,force' for a 16MB swiotlb (the default is 64MB which
may burn an unnecessary amount of RAM).
-- Keir
next prev parent reply other threads:[~2006-05-01 6:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-01 3:29 IVTV and Xen Jason
2006-05-01 5:20 ` Andy Clayton
2006-05-01 6:45 ` Keir Fraser [this message]
2006-05-02 1:14 ` Jason
2006-05-02 7:45 ` Muli Ben-Yehuda
2006-05-02 8:07 ` Jason
2006-05-02 7:46 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2006-05-01 13:40 jason
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=3ac635b4dd93e7696042238ab96f940b@cl.cam.ac.uk \
--to=keir.fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
--cc=xen.nospam@q3aiml.net \
--cc=xen@jasonandjessi.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.