dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <deathsimple@vodafone.de>
To: alexdeucher@gmail.com
Cc: Alex Deucher <alexander.deucher@amd.com>,
	Jerome Glisse <jglisse@redhat.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/radeon: GPU virtual memory support v22
Date: Fri, 06 Jan 2012 13:53:11 +0100	[thread overview]
Message-ID: <4F06EEB7.2070901@vodafone.de> (raw)
In-Reply-To: <1325819467-2216-1-git-send-email-alexdeucher@gmail.com>

On -10.01.-28163 20:59, alexdeucher@gmail.com wrote:
[SNIP]
>   #define RADEON_CHUNK_ID_RELOCS	0x01
>   #define RADEON_CHUNK_ID_IB	0x02
>   #define RADEON_CHUNK_ID_FLAGS	0x03
>
>   /* The first dword of RADEON_CHUNK_ID_FLAGS is a uint32 of these flags: */
>   #define RADEON_CS_KEEP_TILING_FLAGS 0x01
> +#define RADEON_CS_USE_VM            0x02
> +/* The second dword of RADEON_CHUNK_ID_FLAGS is a uint32 that sets the ring type */
> +#define RADEON_CS_RING_GFX          0
> +#define RADEON_CS_RING_COMPUTE      1
> +/* The third dword of RADEON_CHUNK_ID_FLAGS is a sint32 that sets the priority */
> +/* 0 = normal, + = higher priority, - = lower priority */
> +struct drm_radeon_cs_ring_priority {
> +	int32_t			priority;
> +};
Sorry, missed that one before, the "struct drm_radeon_cs_ring_priority" 
is pretty much pointless.

My comment was going more into that direction:
struct drm_radeon_cs_flags {
     uint32_t      flags;
     uint32_t      ring_type;
     int32_t        priority;
};

Anyway, the patch is finally committed, but I think we should fix 
(remove?) that before it goes further upstream.

Christian.

  parent reply	other threads:[~2012-01-06 13:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-06  3:11 [PATCH 1/3] drm/radeon: GPU virtual memory support v22 alexdeucher
2012-01-06  3:11 ` [PATCH 2/3] drm/radeon/kms: Add support for multi-ring sync in CS ioctl (v2) alexdeucher
2012-01-06  3:11 ` [PATCH 3/3] drm/radeon/kms: sync across multiple rings when doing bo moves v3 alexdeucher
2012-01-06 10:09 ` [PATCH 1/3] drm/radeon: GPU virtual memory support v22 Dave Airlie
2012-01-06 14:13   ` Alex Deucher
2012-01-06 12:53 ` Christian König [this message]
2012-01-06 14:12   ` Alex Deucher
2012-01-06 14:46     ` Christian König
2012-01-06 15:00       ` Alex Deucher
2012-01-08 14:05 ` Daniel Vetter
2012-01-08 22:56   ` Jerome Glisse
2012-01-09  8:31     ` Daniel Vetter
2012-01-09 15:44       ` Jerome Glisse
2012-01-09 16:07         ` Alex Deucher
2012-01-09 16:49           ` Daniel Vetter
2012-01-09 16:56             ` Alex Deucher
2012-01-09 20:05               ` Daniel Vetter
2012-01-09 16:42         ` Daniel Vetter

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=4F06EEB7.2070901@vodafone.de \
    --to=deathsimple@vodafone.de \
    --cc=alexander.deucher@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jglisse@redhat.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