From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jerome Glisse <j.glisse@gmail.com>
Cc: Thomas Hellstrom <thellstrom@vmware.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [RFC] ttm merge ttm_backend & ttm_tt
Date: Tue, 1 Nov 2011 21:29:42 -0400 [thread overview]
Message-ID: <20111102012942.GA20327@phenom.dumpdata.com> (raw)
In-Reply-To: <CAH3drwaSWcOQTwuo22M_pwbfDdCq5MfPX4r8w03U3o9JcFPh1w@mail.gmail.com>
On Tue, Nov 01, 2011 at 09:11:37PM -0400, Jerome Glisse wrote:
> Hi,
>
> So attached is patch serie (sorry for that i am away of my normal mail
> config) which ultimately merge ttm_backend & ttm_tt it allows to get
> rid of data duplication btw the two, especialy btw ttm_tt and driver
> specific backend. So net result is less 300lines of code accross ttm
> and driver.
>
> Konrad given some of the upstream nouveau change, your patchserie
> conflict and would lead to revert some nouveau fixes. I believe the
> intention is to get the ttm-dma code into 3.3 (3.2 seems late but
> dunno). If 3.3 is the aim than i will rebase your patch on top of this
Yup. 3.3.
> serie, this should lower the number of change your serie needed.
OK.
>
> Note that this is early code, only compile tested, i just wanted to
> get feedback to know if anyone has objection on that.
Let me take a look then at them tomorrow.
>
> For quick review, first 5 patches can be ignored, they are cleanup and
> dead code removal or small fixes. The real action is in the last
> patch.
>
> Next set is to move page allocation through ttm_helper into the driver
> thus making the whole dma stuff a driver business, driver who don't
> care about dma (like vmw) could ignore it, while driver that have to
> would deal with it through ttm_helper.
>
> Cheers,
> Jerome
next prev parent reply other threads:[~2011-11-02 1:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 1:11 [RFC] ttm merge ttm_backend & ttm_tt Jerome Glisse
2011-11-02 1:29 ` Konrad Rzeszutek Wilk [this message]
2011-11-02 3:05 ` Jerome Glisse
2011-11-02 4:24 ` Konrad Rzeszutek Wilk
2011-11-02 6:42 ` Thomas Hellstrom
2011-11-02 15:04 ` Konrad Rzeszutek Wilk
2011-11-02 16:48 ` Jerome Glisse
2011-11-02 17:09 ` Konrad Rzeszutek Wilk
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=20111102012942.GA20327@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=j.glisse@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox