dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sylvain BERTRAND <sylware@legeek.net>
To: "Christian König" <deathsimple@vodafone.de>
Cc: Christian Koenig <christian.koenig@amd.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 08/10] drm/radeon: replace pflip and sw_int counters with atomics
Date: Thu, 24 May 2012 13:59:09 +0200	[thread overview]
Message-ID: <20120524115909.GA14376@freedom> (raw)
In-Reply-To: <1337845754-3718-8-git-send-email-deathsimple@vodafone.de>

> +	atomic_t			ring_int[RADEON_NUM_RINGS];
>  	bool				crtc_vblank_int[RADEON_MAX_CRTCS];
> -	bool				pflip[RADEON_MAX_CRTCS];
> -	int				pflip_refcount[RADEON_MAX_CRTCS];
> +	atomic_t			pflip[RADEON_MAX_CRTCS];

Hi,

Does the linux API mandates atomic_t to be a 32bits word?

Regards,

-- 
Sylvain

  reply	other threads:[~2012-05-24 11:59 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-24  7:49 [PATCH 01/10] drm/radeon: remove radeon_fence_create Christian König
2012-05-24  7:49 ` [PATCH 02/10] drm/radeon: add infrastructure for advanced ring synchronization Christian König
2012-05-24 15:56   ` j.glisse
2012-05-24  7:49 ` [PATCH 03/10] drm/radeon: rework ring syncing code Christian König
2012-05-24 15:57   ` j.glisse
2012-05-24  7:49 ` [PATCH 04/10] drm/radeon: replace vmram_mutex with mclk_lock v2 Christian König
2012-05-24 15:57   ` j.glisse
2012-05-24  7:49 ` [PATCH 05/10] drm/radeon: remove some unneeded structure members Christian König
2012-05-24 15:58   ` j.glisse
2012-05-24  7:49 ` [PATCH 06/10] drm/radeon: fix & improve ih ring handling Christian König
2012-05-24 15:59   ` j.glisse
2012-05-24  7:49 ` [PATCH 07/10] drm/radeon: apply Murphy's law to the kms irq code Christian König
2012-05-24 15:35   ` Alex Deucher
2012-05-24 15:53     ` j.glisse
2012-05-31 18:15     ` Alex Deucher
2012-05-31 18:39       ` Jerome Glisse
2012-05-31 20:15       ` Christian König
2012-05-24  7:49 ` [PATCH 08/10] drm/radeon: replace pflip and sw_int counters with atomics Christian König
2012-05-24 11:59   ` Sylvain BERTRAND [this message]
2012-05-24 12:29     ` Koenig, Christian
2012-05-24 12:46       ` Sylvain BERTRAND
2012-05-24 12:53         ` Dave Airlie
2012-05-24 12:54           ` Dave Airlie
2012-05-24 14:23             ` Sylvain BERTRAND
2012-05-24  7:49 ` [PATCH 09/10] drm/radeon: replace cs_mutex with vm_mutex Christian König
2012-05-24  7:49 ` [PATCH 10/10] drm/radeon: work around bugs in caymans compute rings Christian König
2012-05-24 15:54 ` [PATCH 01/10] drm/radeon: remove radeon_fence_create j.glisse
  -- strict thread matches above, loose matches on Subject: below --
2012-05-31 20:15 Christian König
2012-05-31 20:16 ` [PATCH 08/10] drm/radeon: replace pflip and sw_int counters with atomics Christian König
2012-06-01  6:19   ` Michel Dänzer
2012-06-01  6:30     ` Michel Dänzer
2012-06-01 10:44       ` Christian König
2012-06-01 10:55         ` Michel Dänzer
2012-06-01 11:36 [PATCH 01/10] drm/radeon: remove radeon_fence_create Christian König
2012-06-01 11:36 ` [PATCH 08/10] drm/radeon: replace pflip and sw_int counters with atomics Christian König

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=20120524115909.GA14376@freedom \
    --to=sylware@legeek.net \
    --cc=christian.koenig@amd.com \
    --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