All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacob Gorm Hansen <jacobg@diku.dk>
To: Jacob Gorm Hansen <jacobg@diku.dk>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>Ian Pratt
	<Ian.Pratt@cl.cam.ac.uk>,
	xen-devel <xen-devel@lists.sourceforge.net>
Subject: Re: Failure to get memory for GATT table, again
Date: Wed, 02 Feb 2005 13:28:05 -0800	[thread overview]
Message-ID: <420145E5.9000301@diku.dk> (raw)
In-Reply-To: <20050202005555.GD15851@diku.dk>

Jacob Gorm Hansen wrote:
> On Wed, Feb 02, 2005 at 12:01:41AM -0000, Ian Pratt wrote:
> 
> 
>>dma_alloc_coherent should be calling xen_contig_mem which should turn
>>the pages into ones that are owned by dom0 and contiguous. Add some
>>dubugging to xen_contig_mem to see if you're getting there.
> 
> 
> xen_contig_mem is called correctly, and page ownerships are set to be dom0.
> However, the mmu-update that goes wrong attempts to do a MMUEXT_SET_FOREIGNDOM
> to a domain with number 32753, and that fails because the owner is 0. Who is
> in domain 32753, and why does dom0 wish to map these pages to a foreign domain?

Just to recap, this seems like a bug in Xen or Xenlinux. 
MMUEXT_SET_FOREIGNDOM seems to expect the granted pages to be owned by 
the grantee already, instead of the granter. I've disabled the check in 
Xen, and fglrx now proceeds to take down the machine when I start X. 
Perhaps it would be better to spend the time on the open drivers at 
http://r300.sourceforge.net/ , or wait for ATI to discover Xen.

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

  reply	other threads:[~2005-02-02 21:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-02  0:01 Failure to get memory for GATT table, again Ian Pratt
2005-02-02  0:55 ` Jacob Gorm Hansen
2005-02-02 21:28   ` Jacob Gorm Hansen [this message]
  -- 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-01 21:25 Ian Pratt
2005-02-01 22:15 ` Jacob Gorm Hansen
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
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=420145E5.9000301@diku.dk \
    --to=jacobg@diku.dk \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    /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.