From: Julien Grall <julien.grall@arm.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>,
"Sameer Goel" <sameer.goel@linaro.org>
Cc: sstabellini@kernel.org, wei.liu2@citrix.com,
mjaggi@caviumnetworks.com, george.dunlap@eu.citrix.com,
Andrew.Cooper3@citrix.com, jbeulich@suse.com,
Ian.Jackson@citrix.com, xen-devel@lists.xenproject.org,
nd@arm.com, shankerd@codeaurora.org
Subject: Re: [PATCH 1/7] Port WARN_ON_ONCE() from Linux
Date: Fri, 9 Feb 2018 10:45:25 +0000 [thread overview]
Message-ID: <6c94284e-f559-273d-021e-05ea35b9ec2e@arm.com> (raw)
In-Reply-To: <20180209102947.6dwuchlgkibx4okr@MacBook-Pro-de-Roger.local>
Hi,
On 02/09/2018 10:29 AM, Roger Pau Monné wrote:
> On Thu, Feb 08, 2018 at 08:10:49PM -0700, Sameer Goel wrote:
>> diff --git a/xen/include/xen/lib.h b/xen/include/xen/lib.h
>> index 1d9771340c..697212a061 100644
>> --- a/xen/include/xen/lib.h
>> +++ b/xen/include/xen/lib.h
>> @@ -11,6 +11,19 @@
>> #define BUG_ON(p) do { if (unlikely(p)) BUG(); } while (0)
>> #define WARN_ON(p) do { if (unlikely(p)) WARN(); } while (0)
>>
>> +#define WARN_ON_ONCE(p) \
>> +({ \
>> + static bool __section(".data.unlikely") __warned; \
>> + int __ret_warn_once = !!(p); \
> ^ bool
>
>> + \
>> + if ( unlikely(__ret_warn_once && !__warned) ) \
>> + { \
>> + __warned = true; \
>> + WARN(); \
>> + } \
>> + unlikely(__ret_warn_once); \
>
> Does this macro really need to return something? It seems weird to me
> to allow usages like: if ( WARN_ON_ONCE...
This construct is used in Linux (included in the driver ported):
if (WARN_ON_ONCE(fwspec->iommu_priv)) {
master = fwspec->iommu_priv;
smmu = master->smmu;
} else {
....
}
IHMO the makes the code nicer to read over:
WARN_ON_ONCE(...)
if ( ... ) {
} else {
}
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-02-09 10:45 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 3:10 [PATCH 0/7] SMMUv3 driver Sameer Goel
2018-02-09 3:10 ` [PATCH 1/7] Port WARN_ON_ONCE() from Linux Sameer Goel
2018-02-09 10:29 ` Roger Pau Monné
2018-02-09 10:45 ` Julien Grall [this message]
2018-02-09 10:47 ` Roger Pau Monné
2018-02-13 9:46 ` Jan Beulich
2018-05-18 22:46 ` Sameer Goel
2018-02-12 14:49 ` Wei Liu
2018-02-13 9:48 ` Jan Beulich
2018-02-09 3:10 ` [PATCH 2/7] xen/bitops: Rename LOG_2 to ilog2 Sameer Goel
2018-02-12 14:46 ` Wei Liu
2018-02-09 3:10 ` [PATCH 3/7] passthrough/arm: Modify SMMU driver to use generic device definition Sameer Goel
2018-02-09 3:10 ` [PATCH 4/7] Add verbatim copy of arm-smmu-v3.c from Linux Sameer Goel
2018-02-09 3:10 ` [PATCH 5/7] xen/iommu: smmu-v3: Add Xen specific code to enable the ported driver Sameer Goel
2018-03-01 14:07 ` Julien Grall
2018-03-01 14:21 ` Jan Beulich
2018-03-01 14:33 ` Julien Grall
2018-03-01 15:38 ` Jan Beulich
2018-03-10 17:53 ` Manish Jaggi
2018-03-12 3:36 ` Manish Jaggi
2018-04-19 10:54 ` Manish Jaggi
2018-05-09 8:30 ` Manish Jaggi
2018-05-09 8:58 ` Julien Grall
2018-05-11 20:54 ` Sameer Goel
2018-05-18 22:38 ` Sameer Goel
2018-02-09 3:10 ` [PATCH 6/7] drivers/passthrough/arm: Refactor code for arm smmu drivers Sameer Goel
2018-02-09 10:43 ` Roger Pau Monné
2018-02-09 10:51 ` Julien Grall
2018-02-09 11:02 ` Roger Pau Monné
2018-02-09 11:12 ` Julien Grall
2018-05-18 23:00 ` Sameer Goel
2018-02-09 17:54 ` Sameer Goel
2018-03-01 14:24 ` Julien Grall
2018-02-09 3:10 ` [PATCH 7/7] xen/smmu: Add a new config define for legacy SMMU Sameer Goel
2018-03-01 14:35 ` [PATCH 0/7] SMMUv3 driver Julien Grall
2018-03-04 14:52 ` Manish Jaggi
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=6c94284e-f559-273d-021e-05ea35b9ec2e@arm.com \
--to=julien.grall@arm.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=Ian.Jackson@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=mjaggi@caviumnetworks.com \
--cc=nd@arm.com \
--cc=roger.pau@citrix.com \
--cc=sameer.goel@linaro.org \
--cc=shankerd@codeaurora.org \
--cc=sstabellini@kernel.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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).