All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerome Glisse <jglisse@redhat.com>
To: airlied@gmail.com
Cc: thellstrom@vmware.com, skeggsb@gmail.com, dri-devel@lists.sf.net
Subject: TTM changes + support for unmappable VRAM
Date: Sat, 20 Feb 2010 00:45:49 +0100	[thread overview]
Message-ID: <1266623158-2404-1-git-send-email-jglisse@redhat.com> (raw)

This patchset add a new infrastructure to deal with memory mapping,
with the new interface the driver is responsible for providing io
address at which a buffer is accessible. This would be usefull for
separate aperture configuration but also for future hw which likely
have more advanced feature when it comes to aperture handling.

This patchset absolutely need the TTM fixes Thomas posted couple
weeks ago (thread name last minute range validation fixes) this is
at least needed for radeon unmappable patch otherwise you will get
Xorg faulting all over. This patchset have received limited testing
on radeon (the unmappable bo move seems to work properly, no corruption)
and have just been compile tested on nouveau and vmwgfx.

I wish this to get them included in 2.6.34, comment & review are welcome

Cheers,
Jerome


------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--

             reply	other threads:[~2010-02-19 23:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-19 23:45 Jerome Glisse [this message]
2010-02-19 23:45 ` [PATCH 1/9] drm/ttm: add ttm_fault callback to allow driver to handle bo placement Jerome Glisse
2010-02-19 23:45   ` [PATCH 2/9] drm/radeon/kms: add support for new fault callback Jerome Glisse
2010-02-19 23:45     ` [PATCH 3/9] drm/nouveau/kms: add support for new TTM " Jerome Glisse
2010-02-19 23:45       ` [PATCH 4/9] drm/vmwgfx: " Jerome Glisse
2010-02-19 23:45         ` [PATCH 5/9] drm/radeon/kms: don't initialize TTM io memory manager field Jerome Glisse
2010-02-19 23:45           ` [PATCH 6/9] drm/nouveau/kms: " Jerome Glisse
2010-02-19 23:45             ` [PATCH 7/9] drm/vmwgfx: " Jerome Glisse
2010-02-19 23:45               ` [PATCH 8/9] drm/ttm: remove io_ field from TTM Jerome Glisse
2010-02-19 23:45                 ` [PATCH 9/9] drm/radeon/kms: enable use of unmappable VRAM Jerome Glisse

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=1266623158-2404-1-git-send-email-jglisse@redhat.com \
    --to=jglisse@redhat.com \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.sf.net \
    --cc=skeggsb@gmail.com \
    --cc=thellstrom@vmware.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 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.