From: "Michel Dänzer" <michel@daenzer.net>
To: "Christian König" <deathsimple@vodafone.de>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 15/15] drm/radeon: implement ring saving on reset v2
Date: Tue, 10 Jul 2012 16:50:01 +0200 [thread overview]
Message-ID: <1341931801.12576.413.camel@thor.local> (raw)
In-Reply-To: <1341924684-563-15-git-send-email-deathsimple@vodafone.de>
On Die, 2012-07-10 at 14:51 +0200, Christian König wrote:
> Try to save whatever is on the rings when
> we encounter an lockup.
>
> v2: Fix spelling error. Free saved ring data if reset fails.
> Add documentation for the new functions.
>
> Signed-off-by: Christian König <deathsimple@vodafone.de>
Just some more spelling nits, otherwise this patch and patch 13 are
Reviewed-by: Michel Dänzer <michel.daenzer@amd.com>
> +/**
> + * radeon_ring_backup - Backup the content of a ring
> + *
> + * @rdev: radeon_device pointer
> + * @ring: the ring we want to backup
'back up', in both cases.
> + * Saves all unprocessed commits to a ring, returns the number of dwords saved.
> + */
'unprocessed commands from'?
> +/**
> + * radeon_ring_restore - append saved commands to the ring again
> + *
> + * @rdev: radeon_device pointer
> + * @ring: ring to append commands to
> + * @size: number of dwords we want to write
> + * @data: saved commands
> + *
> + * Allocates space on the ring and restore the previusly saved commands.
'previously'
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Debian, X and DRI developer
prev parent reply other threads:[~2012-07-10 14:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 12:51 [PATCH 01/15] drm/radeon: add error handling to fence_wait_empty_locked Christian König
2012-07-10 12:51 ` [PATCH 02/15] drm/radeon: add error handling to radeon_vm_unbind_locked Christian König
2012-07-10 12:51 ` [PATCH 03/15] drm/radeon: fix fence related segfault in CS Christian König
2012-07-10 12:51 ` [PATCH 04/15] drm/radeon: add an exclusive lock for GPU reset v2 Christian König
2012-07-10 12:51 ` [PATCH 05/15] drm/radeon: fix ring commit padding Christian König
2012-07-10 12:51 ` [PATCH 06/15] drm/radeon: fix fence value access Christian König
2012-07-10 12:51 ` [PATCH 07/15] drm/radeon: fix fence init after resume Christian König
2012-07-10 12:51 ` [PATCH 08/15] drm/radeon: remove FIXME comment from chipset suspend Christian König
2012-07-10 12:51 ` [PATCH 09/15] drm/radeon: make cp init on cayman more robust Christian König
2012-07-10 12:51 ` [PATCH 10/15] drm/radeon: remove ip_pool start/suspend Christian König
2012-07-10 12:51 ` [PATCH 11/15] drm/radeon: remove r600_blit_suspend Christian König
2012-07-10 12:51 ` [PATCH 12/15] drm/radeon: remove vm_manager start/suspend Christian König
2012-07-10 12:51 ` [PATCH 13/15] drm/radeon: move radeon_ib_ring_tests out of chipset code Christian König
2012-07-10 12:51 ` [PATCH 14/15] drm/radeon: record what is next valid wptr for each ring v2 Christian König
2012-07-10 16:56 ` Jerome Glisse
2012-07-11 8:08 ` Christian König
2012-07-10 12:51 ` [PATCH 15/15] drm/radeon: implement ring saving on reset v2 Christian König
2012-07-10 14:50 ` Michel Dänzer [this message]
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=1341931801.12576.413.camel@thor.local \
--to=michel@daenzer.net \
--cc=deathsimple@vodafone.de \
--cc=dri-devel@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