From: Dave Airlie <airlied@gmail.com>
To: Oded Gabbay <oded.gabbay@amd.com>
Cc: "Deucher, Alexander" <alexander.deucher@amd.com>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PULL] drm-amdkfd-next
Date: Thu, 22 Jan 2015 09:47:38 +1000 [thread overview]
Message-ID: <CAPM=9txhozFS39fXOHq4V5UMXHo1uFUTeAD8aZ7qxcQQWOJRBQ@mail.gmail.com> (raw)
In-Reply-To: <20150121123825.GA4033@amd.com>
On 21 January 2015 at 22:38, Oded Gabbay <oded.gabbay@amd.com> wrote:
> Hi Dave,
>
> Another pull request for 3.20.
>
> drm-amdkfd-next-2015-01-21:
>
> - Infrastructure work in amdkfd to prepare for VI support. This work mainly
> includes separating modules into ASIC-specific functionality, adding
> new properties that are relevant for VI, making sure that shared code is
> reused, etc.
>
> - Improve mechanism of submitting packets to HIQ (the kernel queue that amdkfd
> uses to issue commands to the GPU). The driver used to verify that each CS
> was read by the GPU. However, this proved to be both unnecessary and erroneous.
> Therefore, we cancelled this verification.
>
> - Moved initialization of compute VMIDs into radeon driver
>
> - Various minor fixes
CC [M] drivers/gpu/drm/amd/amdkfd/kfd_device_queue_manager_cik.o
/home/airlied/devel/kernel/drm-next/drivers/gpu/drm/amd/amdkfd/kfd_device_queue_manager.c:
In function ‘destroy_queue_nocpsch’:
/home/airlied/devel/kernel/drm-next/drivers/gpu/drm/amd/amdkfd/kfd_device_queue_manager.c:291:9:
warning: ‘mqd’ may be used uninitialized in this function
[-Wmaybe-uninitialized]
retval = mqd->destroy_mqd(mqd, q->mqd,
^
Looks valid to me, I've pulled this but please follow up ASAP with a
fix for the new warning.
Dave.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-01-21 23:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 12:38 [PULL] drm-amdkfd-next Oded Gabbay
2015-01-21 23:47 ` Dave Airlie [this message]
2015-01-22 9:42 ` Oded Gabbay
-- strict thread matches above, loose matches on Subject: below --
2017-01-16 15:39 Oded Gabbay
2016-09-19 19:49 Oded Gabbay
2016-09-27 6:55 ` Oded Gabbay
2016-07-03 5:14 Oded Gabbay
2016-05-04 6:31 Oded Gabbay
2016-02-27 21:07 Oded Gabbay
2015-07-20 8:01 Oded Gabbay
2015-06-01 5:53 Oded Gabbay
2015-05-18 6:29 Oded Gabbay
2015-05-18 6:31 ` Oded Gabbay
2015-05-19 0:16 ` Dave Airlie
2015-05-19 4:39 ` Oded Gabbay
2015-03-25 12:22 Oded Gabbay
2015-01-09 20:33 Oded Gabbay
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='CAPM=9txhozFS39fXOHq4V5UMXHo1uFUTeAD8aZ7qxcQQWOJRBQ@mail.gmail.com' \
--to=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=oded.gabbay@amd.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.