From: Bastian Blank <waldi@debian.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
xen-devel@lists.xensource.com,
pkg-xen-devel@lists.alioth.debian.org,
Maciej Sosnowski <maciej.sosnowski@intel.com>,
linux-kernel@vger.kernel.org, William Dauchy <wdauchy@gmail.com>,
Konrad Rzeszutek Wilk <konrad@darnok.org>,
Dave Jiang <dave.jiang@intel.com>
Subject: Re: [Pkg-xen-devel] ioatdma: Boot process hangs then reboots when using Xen + Linux 3.2
Date: Fri, 2 Mar 2012 21:08:26 +0100 [thread overview]
Message-ID: <20120302200826.GA4728@wavehammer.waldi.eu.org> (raw)
In-Reply-To: <CABE8wwvd-R1VkyFL-eZYDB9O05zyWkVQ8pXuMb8GcdAW=5qT3A@mail.gmail.com>
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@debian.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
next prev parent reply other threads:[~2012-03-02 20:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 13:31 regression ioatdma 3.3 William Dauchy
2012-01-27 14:47 ` Konrad Rzeszutek Wilk
2012-01-27 15:02 ` William Dauchy
2012-02-19 22:31 ` Jonathan Nieder
2012-02-20 18:16 ` Jonathan Nieder
2012-02-25 7:46 ` Thomas Goirand
2012-02-25 21:13 ` William Dauchy
2012-03-02 5:57 ` ioatdma: Boot process hangs then reboots when using Xen + Linux 3.2 Jonathan Nieder
2012-03-02 6:42 ` Dan Williams
2012-03-02 16:21 ` [Pkg-xen-devel] " Bastian Blank
2012-03-02 16:44 ` Dan Williams
2012-03-02 17:57 ` Bastian Blank
2012-03-02 19:31 ` Dan Williams
2012-03-02 20:08 ` Bastian Blank [this message]
2012-03-02 20:16 ` Dan Williams
2012-03-02 20:56 ` Bastian Blank
2012-03-02 21:17 ` Dan Williams
2012-03-05 15:26 ` Thomas Goirand
2012-03-05 15:38 ` Dan Williams
2012-03-06 9:20 ` Thomas Goirand
2012-03-06 10:33 ` Bastian Blank
2012-03-06 14:14 ` Dan Williams
2012-03-06 14:39 ` Ian Campbell
2012-03-13 16:49 ` [Xen-devel] " Konrad Rzeszutek Wilk
2012-03-11 22:06 ` Jonathan Nieder
2012-03-23 23:55 ` Dan Williams
2012-03-24 1:29 ` William Dauchy
2012-03-24 2:25 ` William Dauchy
2012-03-24 3:34 ` Williams, Dan J
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=20120302200826.GA4728@wavehammer.waldi.eu.org \
--to=waldi@debian.org \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=jrnieder@gmail.com \
--cc=konrad@darnok.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.sosnowski@intel.com \
--cc=pkg-xen-devel@lists.alioth.debian.org \
--cc=wdauchy@gmail.com \
--cc=xen-devel@lists.xensource.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).