WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] xen kernel 2.6.18 bug with a d-link DFE 580TX - pci hide

To: Michael Kapp <tquarkk@xxxxxxxxxx>
Subject: Re: [Xen-devel] xen kernel 2.6.18 bug with a d-link DFE 580TX - pci hide
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Sun, 26 Oct 2008 21:02:22 +0000
Cc: xen-dev <xen-devel@xxxxxxxxxxxxxxxxxxx>, Frank Mundinger <f.mundinger@xxxxxxx>
Delivery-date: Sun, 26 Oct 2008 14:02:52 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4904C24F.4050308@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Ack3riO6Yn19aqOhEd2swwAWy6hiGQ==
Thread-topic: [Xen-devel] xen kernel 2.6.18 bug with a d-link DFE 580TX - pci hide
User-agent: Microsoft-Entourage/11.4.0.080122
On 26/10/08 19:17, "Michael Kapp" <tquarkk@xxxxxxxxxx> wrote:

>> The network card is only capable of 32-bit DMA. So for addresses above 4GB a
>> bounce buffer is required (DMA to/from bounce buffer; then copy to/from
>> proper high-memory buffer using host CPU). The swiotlb is basically a
>> pre-allocated bounce-buffer area. Because it is pre-allocated it is a waste
>> of memory if it isn't used and, since domUs do not normally perform real
>> physical I/O directly, we therefore by default only create a swiotlb for
>> dom0. You then have to override on the cmdline if this default doesn't
>> actually work (as in this case).
> 
> ...and why is it not possible (from the dom0 point of view) to detect
> this behaviour while starting the domU, reading it's conf and stop the
> boot process with a warning?

IOMMU_BUG_ON() is supposed to printk a suitable warnign before actually
crashing. Not sure why that didn't work for you.

 -- Keir



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