linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
Cc: benh@kernel.crashing.org, cbe-oss-dev@ozlabs.org,
	linux-kernel@vger.kernel.org,
	linux-fbdev-devel@lists.sourceforge.net,
	Geert.Uytterhoeven@sonycom.com, jim@jtan.com
Subject: Re: [PATCH 04/15] ps3vram: Replace mutex by spinlock + list
Date: Fri, 8 May 2009 16:05:44 -0700	[thread overview]
Message-ID: <20090508160544.28189203.akpm@linux-foundation.org> (raw)
In-Reply-To: <1241791284-11490-5-git-send-email-Geert.Uytterhoeven@sonycom.com>

On Fri,  8 May 2009 16:01:13 +0200
Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com> wrote:

> +static int ps3vram_make_request(struct request_queue *q, struct bio *bio)
> +{
> +	struct ps3_system_bus_device *dev = q->queuedata;
> +	struct ps3vram_priv *priv = dev->core.driver_data;
> +
> +	dev_dbg(&dev->core, "%s\n", __func__);
> +
> +	spin_lock_irq(&priv->lock);
> +	if (priv->tail) {
> +		priv->tail->bi_next = bio;
> +		priv->tail = bio;
> +		spin_unlock_irq(&priv->lock);
> +		return 0;
> +	}
> +
> +	priv->tail = bio;
> +	spin_unlock_irq(&priv->lock);
> +
> +	do {
> +		bio = ps3vram_do_bio(dev, bio);
> +	} while (bio);

Is there something which prevents two threads of control from walking
the same list at the same time?

> +
>  	return 0;
>  }

  parent reply	other threads:[~2009-05-08 23:05 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-08 14:01 [PATCH 0/15] ps3{fb,vram,disk} patches for 2.6.31 Geert Uytterhoeven
2009-05-08 14:01 ` [PATCH 01/15] ps3vram: Fix error path (return -EIO) for short read/write Geert Uytterhoeven
2009-05-08 14:01   ` [PATCH 02/15] ps3vram: Use proc_create_data() instead of proc_create() Geert Uytterhoeven
2009-05-08 14:01     ` [PATCH 03/15] ps3vram: Correct exchanged gotos in ps3vram_probe() error path Geert Uytterhoeven
2009-05-08 14:01       ` [PATCH 04/15] ps3vram: Replace mutex by spinlock + list Geert Uytterhoeven
2009-05-08 14:01         ` [PATCH 05/15] ps3fb: Remove useless debug checks in ps3fb_shutdown() Geert Uytterhoeven
2009-05-08 14:01           ` [PATCH 06/15] ps3fb: Inline functions in ps3fb_probe(), to ease cleanup in the error path Geert Uytterhoeven
2009-05-08 14:01             ` [PATCH 07/15] ps3fb: Correct handling of device opening in ps3fb_probe() Geert Uytterhoeven
2009-05-08 14:01               ` [PATCH 08/15] powerpc/cell: Extract duplicated IOPTE_* to <asm/iommu.h> Geert Uytterhoeven
2009-05-08 14:01                 ` [PATCH 09/15] ps3fb: GPU memory mapping cleanup Geert Uytterhoeven
2009-05-08 14:01                   ` [PATCH 10/15] ps3vram: " Geert Uytterhoeven
2009-05-08 14:01                     ` [PATCH 11/15] ps3fb/vram: Extract common GPU stuff into <asm/ps3gpu.h> Geert Uytterhoeven
2009-05-08 14:01                       ` [PATCH 12/15] ps3fb: Tear down FB setup during cleanup Geert Uytterhoeven
2009-05-08 14:01                         ` [PATCH 13/15] ps3vram: Remove no longer used ps3vram_priv.ddr_base Geert Uytterhoeven
2009-05-08 14:01                           ` [PATCH 14/15] ps3vram: Make ps3vram_priv.reports a void * Geert Uytterhoeven
2009-05-08 14:01                             ` [PATCH 15/15] block/ps3: remove driver_data direct access of struct device Geert Uytterhoeven
2009-05-10 19:08                 ` [PATCH 08/15] powerpc/cell: Extract duplicated IOPTE_* to <asm/iommu.h> Christoph Hellwig
2009-05-11  7:24                   ` Geert Uytterhoeven
2009-05-08 23:05         ` Andrew Morton [this message]
2009-05-11  6:38           ` [PATCH 04/15] ps3vram: Replace mutex by spinlock + list Geert Uytterhoeven
2009-05-10 19:05         ` [Cbe-oss-dev] " Christoph Hellwig
2009-05-11 14:20           ` Geert Uytterhoeven

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=20090508160544.28189203.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=Geert.Uytterhoeven@sonycom.com \
    --cc=benh@kernel.crashing.org \
    --cc=cbe-oss-dev@ozlabs.org \
    --cc=jim@jtan.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).