linux-kernel - Re: [PATCH] gpu: host1x: do not check previously handled gathers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 23 Jan 2014 18:31:22 +0100
From:	Erik Faye-Lund <kusmabite@...il.com>
To:	linux-tegra@...r.kernel.org
Cc:	thierry.reding@...il.com, tbergstrom@...dia.com,
	dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
	Erik Faye-Lund <kusmabite@...il.com>
Subject: Re: [PATCH] gpu: host1x: do not check previously handled gathers

Ping?

On Tue, Jan 7, 2014 at 9:03 PM, Erik Faye-Lund <kusmabite@...il.com> wrote:
> When patching gathers, we don't need to check against
> gathers with lower indices than the current one, as
> they are guaranteed to already have been handled.
>
> Signed-off-by: Erik Faye-Lund <kusmabite@...il.com>
> ---
>
> Here's a trivial optimization I have been running with for a while.
>
>  drivers/gpu/host1x/job.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/host1x/job.c b/drivers/gpu/host1x/job.c
> index de5ec33..e965805 100644
> --- a/drivers/gpu/host1x/job.c
> +++ b/drivers/gpu/host1x/job.c
> @@ -534,7 +534,7 @@ int host1x_job_pin(struct host1x_job *job, struct device *dev)
>
>                 g->base = job->gather_addr_phys[i];
>
> -               for (j = 0; j < job->num_gathers; j++)
> +               for (j = i + 1; j < job->num_gathers; j++)
>                         if (job->gathers[j].bo == g->bo)
>                                 job->gathers[j].handled = true;
>
> --
> 1.8.1.2
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/