linux-kernel - Re: [v2 04/11] soc/fsl: Introduce drivers for the DPAA QMan

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150912011005.GA8796@home.buserror.net>
Date:	Fri, 11 Sep 2015 20:10:05 -0500
From:	Scott Wood <scottwood@...escale.com>
To:	Roy Pledge <Roy.Pledge@...escale.com>
CC:	<linuxppc-dev@...ts.ozlabs.org>, <netdev@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [v2 04/11] soc/fsl: Introduce drivers for the DPAA QMan

On Wed, Aug 12, 2015 at 04:14:50PM -0400, Roy Pledge wrote:
> +/* Lock/unlock frame queues, subject to the "LOCKED" flag. This is about
> + * inter-processor locking only. Note, FQLOCK() is always called either under a
> + * local_irq_save() or from interrupt context - hence there's no need for irq
> + * protection (and indeed, attempting to nest irq-protection doesn't work, as
> + * the "irq en/disable" machinery isn't recursive...). */
> +#define FQLOCK(fq) \
> +	do { \
> +		struct qman_fq *__fq478 = (fq); \
> +		if (fq_isset(__fq478, QMAN_FQ_FLAG_LOCKED)) \
> +			spin_lock(&__fq478->fqlock); \
> +	} while (0)
> +#define FQUNLOCK(fq) \
> +	do { \
> +		struct qman_fq *__fq478 = (fq); \
> +		if (fq_isset(__fq478, QMAN_FQ_FLAG_LOCKED)) \
> +			spin_unlock(&__fq478->fqlock); \
> +	} while (0)
> +

I don't see QMAN_FQ_FLAG_LOCKED set anywhere.  What is the use case?

-Scott
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/