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/
Home Products Support Community News


Re: [Xen-devel] Question regarding SLAB corruption

To: Keir Fraser <keir@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Question regarding SLAB corruption
From: Lukas Hejtmanek <xhejtman@xxxxxxxxxxx>
Date: Sun, 8 Jul 2007 12:05:08 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 08 Jul 2007 03:02:12 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C2B67408.A7E4%keir@xxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20070708005423.GU3885@xxxxxxxxxxx> <C2B67408.A7E4%keir@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.16 (2007-06-11)
On Sun, Jul 08, 2007 at 10:59:20AM +0100, Keir Fraser wrote:
> It could be DMAing randomly. Is there a debug flag in the driver to provide
> verbose tracing? Or you could add tracing (or audit) the places that it
> initiates DMA and see whether the DMA addresses are correctly calculated.

Yeah, I will try to add tracing to DMA actions. However, can address bars
influence DMA actions, mainly if provided by Dom0 for DomU.

More precisely, if I bypass address bars logic (in pciback) and write the
addresses directly to the PCI config space, isn't Xen Dom0 confused and
possibly sets up DMA transfers incorrectly? I.e., which part physically sets
up the DMA -- Dom0 or DomU?

Lukáš Hejtmánek

Xen-devel mailing list