From: Katarzyna Dec <katarzyna.dec@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t v4 0/4] Refactoring of *_fill libraries
Date: Tue, 10 Apr 2018 12:37:31 +0200 [thread overview]
Message-ID: <20180410103731.GD23949@kdec5-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20180410082045.ci456hznpyl6rvv5@platvala-desk.ger.corp.intel.com>
On Tue, Apr 10, 2018 at 11:20:45AM +0300, Petri Latvala wrote:
> On Tue, Apr 10, 2018 at 10:12:28AM +0200, Katarzyna Dec wrote:
> > This series is removing duplications in gpgpu_fill and media_fill
> > libraries. As a first step I moved gpgpu and media helper functions
> > to gpu_fill library. In second patch I adjusted code to our coding
> > style. In the third not obvious duplications were removed (like
> > adding in gen7 functions conditions for future gens). Last patch
> > adds missing parameters that make GPU hang on gen9 and gen9+.
> >
> > In first version of this series there was a comment about moving
> > batch_alloc/copy etc. functions to intel_batchbuffer library.
> > Because there is a lot of code to review already this change will
> > be introduced in another series (rendercopy, media_fill, gpgpu_fill
> > and media_spin code is affected by this).
> >
> > It is possible that more changes around gen*_media.h and media_spin
> > is needed, but this will be done as a next step.
> >
> > v2: Removed not obvious duplications. Adjusted code to review comments.
> > v3: Series needed reorganization because it introduced bug to ALP,
> > which was hard to find. That is why patch 1 is now almost only moving functions to gpu_fill with removing duplications, such as the same functions. Also applied comments from review.
> > v4: Added #defines and copyrights to new gpu_fill library. Changed functions
> > order in gpu_fill library.
>
>
> If you mean the header guards with #defines, they need to be there in
> patch 1 already. Patch 1 alone doesn't build.
>
>
> --
> Petri Latvala
You're right, I added it to wrong patch. I will fix it :)
Kasia
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2018-04-10 10:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 8:12 [igt-dev] [PATCH i-g-t v4 0/4] Refactoring of *_fill libraries Katarzyna Dec
2018-04-10 8:12 ` [igt-dev] [PATCH i-g-t v4 1/4] lib: Move common gpgpu/media fill functions to gpu_fill library Katarzyna Dec
2018-04-10 8:12 ` [igt-dev] [PATCH i-g-t v4 2/4] lib: Remove duplications in " Katarzyna Dec
2018-04-10 8:12 ` [igt-dev] [PATCH i-g-t v4 3/4] lib/gpgpu_fill: Add missing configuration parameters for gpgpu_fill Katarzyna Dec
2018-04-10 8:12 ` [igt-dev] [PATCH i-g-t v4 4/4] lib: Adjust refactored gpu_fill library to our coding style Katarzyna Dec
2018-04-10 8:20 ` [igt-dev] [PATCH i-g-t v4 0/4] Refactoring of *_fill libraries Petri Latvala
2018-04-10 10:37 ` Katarzyna Dec [this message]
2018-04-10 8:41 ` [igt-dev] ✗ Fi.CI.BAT: warning for Refactoring of *_fill libraries (rev3) Patchwork
-- strict thread matches above, loose matches on Subject: below --
2018-04-09 15:42 [igt-dev] [PATCH i-g-t] lib/gen6_render: Refactoring lib Lukasz Kalamarz
2018-04-10 10:48 ` [igt-dev] [PATCH i-g-t v4 0/4] Refactoring of *_fill libraries Katarzyna Dec
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=20180410103731.GD23949@kdec5-desk.ger.corp.intel.com \
--to=katarzyna.dec@intel.com \
--cc=igt-dev@lists.freedesktop.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