From: Jacob Gorm Hansen <jacobg@diku.dk>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.sourceforge.net>
Subject: Re: Failure to get memory for GATT table, again
Date: Tue, 1 Feb 2005 23:15:53 +0100 [thread overview]
Message-ID: <20050201221553.GA15851@diku.dk> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D12365F@liverpoolst.ad.cl.cam.ac.uk>
On Tue, Feb 01, 2005 at 09:25:33PM -0000, Ian Pratt wrote:
> > >>(file=/mnt/hda3/home/jacobg/xeno-unstable.bk/xen/include/asm/mm.h,
> > > > >>line=157) Error pfn 0003ff40: ed=fc599260, sd=fc5996a0,
> > > > caf=80000002,
> > > > >>taf=f0000001
> > >
> > > I suspect that sd is actually 'dom_xen', but it would be useful to
> > > verify this.
> > > Also, please print out max_page and post the e820 map for
> > the machine.
> >
> > here is the error again, with max_page added:
> >
> > (XEN)
> > (file=/mnt/hda3/home/jacobg/xeno-unstable.bk/xen/include/asm/m
> > m.h, line=161) Error pfn 0003ff40: ed=fc599260, sd=fc5996a0,
> > caf=80000002, taf=f0000001 max_page 0003ff74
> > (XEN) 0000000000100000 - 000000003ff74000 (usable)
>
> I bet the fglrx driver just does get_free_pages rather than the proper
> dma_alloc_coherent.
hmm, actually it seems the case is that dma_alloc_coherent() falls back to
calling __get_free_pages(), because dev->dma_mem is NULL. When the returned
address gets converted into a bus address, the resulting address seems to be
within Xen-space :-(
Why is calling __get_free_pages() a problem?
Jacob
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next prev parent reply other threads:[~2005-02-01 22:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 21:25 Failure to get memory for GATT table, again Ian Pratt
2005-02-01 22:15 ` Jacob Gorm Hansen [this message]
2005-02-01 22:45 ` Ian Pratt
2005-02-01 22:52 ` Jacob Gorm Hansen
2005-02-01 23:18 ` Ian Pratt
2005-02-01 23:29 ` Jacob Gorm Hansen
-- strict thread matches above, loose matches on Subject: below --
2005-02-02 22:38 Ian Pratt
2005-02-02 23:55 ` Jacob Gorm Hansen
2005-02-02 0:01 Ian Pratt
2005-02-02 0:55 ` Jacob Gorm Hansen
2005-02-02 21:28 ` Jacob Gorm Hansen
2005-02-01 16:39 Ian Pratt
2005-02-01 20:08 ` Jacob Gorm Hansen
2005-02-01 7:27 Ian Pratt
2005-02-01 8:23 ` Jacob Gorm Hansen
2005-02-01 8:46 ` Jacob Gorm Hansen
2005-02-01 8:59 ` Jacob Gorm Hansen
2005-02-01 4:29 Jacob Gorm Hansen
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=20050201221553.GA15851@diku.dk \
--to=jacobg@diku.dk \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/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.