mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dave Airlie" <airlied@gmail.com>
To: "Linux Kernel" <linux-kernel@vger.kernel.org>,
	dri-devel <dri-devel@lists.sourceforge.net>
Subject: drm + 4GB RAM + swiotlb = drm craps out
Date: Mon, 2 Apr 2007 09:44:41 +1000	[thread overview]
Message-ID: <21d7e9970704011644n3adbef2brc6bfeb288f5d0866@mail.gmail.com> (raw)

Okay I've got a bug reported before and now again about > 4GB + radeon
blows up the DRM... on Intel hw...

What the drm currently does for the PCI GART table is it allocates a
chunk of memory (8MB) with vmalloc_32(), then when it decides to use
it it goes through every page of it calls pci_map_single() (with
PCI_DMA_TODEVICE, which is probably wrong...) with every page from the
vmalloc mapping and puts the bus addresses of the pages into the PCI
GART table on the GPU.

So when swiotlb happens, as you can guess it all falls apart as the
drm never calls sync functions at any stage...

The main problem is the ring buffer and scratch write back, these
values are read/write from both the CPU and GPU quite a lot, so this
leads me to think I should really just be using dma_alloc_coherent for
the whole lot, however this is an 8MB mapping and possibly could be
getting larger in the future and dynamic as we do dynamic PCIEGART
support for the radeons...

So I suppose I'm asking for ideas on the "correct" way to do this, and
perhaps any quick way to patch up the problem I'm seeing now by making
swiotlb not get involved ....

Regards,
Dave.

             reply	other threads:[~2007-04-01 23:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-01 23:44 Dave Airlie [this message]
2007-04-02  3:11 ` David Miller
2007-04-02  4:08   ` Dave Airlie
2007-04-02  5:08     ` David Miller
2007-04-02  5:15       ` Dave Airlie
2007-04-02  5:24         ` David Miller
2007-04-02  6:27         ` Andi Kleen
2007-04-02  5:38           ` Dave Airlie
2007-04-02  6:40             ` Andi Kleen
2007-04-02  6:52               ` Dave Airlie
2007-04-02  6:55                 ` Andi Kleen

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=21d7e9970704011644n3adbef2brc6bfeb288f5d0866@mail.gmail.com \
    --to=airlied@gmail.com \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®