[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120302200826.GA4728@wavehammer.waldi.eu.org>
Date: Fri, 2 Mar 2012 21:08:26 +0100
From: Bastian Blank <waldi@...ian.org>
To: Dan Williams <dan.j.williams@...el.com>
Cc: Jonathan Nieder <jrnieder@...il.com>,
xen-devel@...ts.xensource.com,
pkg-xen-devel@...ts.alioth.debian.org,
Maciej Sosnowski <maciej.sosnowski@...el.com>,
linux-kernel@...r.kernel.org, William Dauchy <wdauchy@...il.com>,
Konrad Rzeszutek Wilk <konrad@...nok.org>,
Dave Jiang <dave.jiang@...el.com>
Subject: Re: [Pkg-xen-devel] ioatdma: Boot process hangs then reboots when
using Xen + Linux 3.2
On Fri, Mar 02, 2012 at 11:31:56AM -0800, Dan Williams wrote:
> On Fri, Mar 2, 2012 at 9:57 AM, Bastian Blank <waldi@...ian.org> wrote:
> > phys_complete (a 32 bit value) gets compared to struct
> > dma_async_tx_descriptor.phys, which is defined as dma_addr_t, a _64_ bit
> > value.
> The assumption is that the driver's control structures are not in high
> memory so all address values will only have 32-bits of valid data,
Can you back that up by some kernel documentation? There is a reason why
pci_alloc_pool uses dma_addr_t to store the address and _not_ unsigned
long. This are physical addresses, nothing the kernel can access
directly without a mapping.
> but
> maybe xen32 changes that assumption?
Xen changes a lot of things in the memory management. This includes that
physical != machine addresses, where i915 failed horrible.
> Can you send the log of the driver load with debug enabled?
No, I don't have that hardware.
Bastian
--
Each kiss is as the first.
-- Miramanee, Kirk's wife, "The Paradise Syndrome",
stardate 4842.6
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists