From: Julien Grall <julien.grall@linaro.org>
To: Sameer Goel <sameer.goel@linaro.org>,
xen-devel@lists.xenproject.org, julien.grall@arm.com,
mjaggi@caviumnetworks.com
Cc: sstabellini@kernel.org, wei.liu2@citrix.com,
george.dunlap@eu.citrix.com, Andrew.Cooper3@citrix.com,
andre.przywara@linaro.org, jbeulich@suse.com,
Ian.Jackson@citrix.com, nd@arm.com, shankerd@codeaurora.org
Subject: Re: [RFC v4 1/8] Port WARN_ON_ONCE() from Linux
Date: Tue, 23 Jan 2018 11:33:51 +0000 [thread overview]
Message-ID: <3eaf2c0e-94e4-8161-985b-3704fbfd4c96@linaro.org> (raw)
In-Reply-To: <20171219031703.23420-2-sameer.goel@linaro.org>
Hi Sameer,
On 19/12/17 03:16, Sameer Goel wrote:
> Port WARN_ON_ONCE macro from Linux.
>
> Signed-off-by: Sameer Goel <sameer.goel@linaro.org>
> ---
> xen/include/xen/lib.h | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/xen/include/xen/lib.h b/xen/include/xen/lib.h
> index ed00ae1379..83206c0848 100644
> --- a/xen/include/xen/lib.h
> +++ b/xen/include/xen/lib.h
> @@ -11,6 +11,17 @@
> #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); \
> + \
> + if (unlikely(__ret_warn_once && !__warned)) { \
I realise BUG_ON/WARN_ON above is not using Xen coding style. However,
can you make this code follow Xen coding style?
FWIW with the coding style change:
Acked-by: Julien Grall <julien.grall@linaro.org>
This will also require an ack from "THE REST" maintainers as this is
common code.
Cheers,
> + __warned = true; \
> + WARN_ON(1); \
> + } \
> + unlikely(__ret_warn_once); \
> +})
> +
> #if __GNUC__ > 4 || (__GNUC__ == 4 && __GNUC_MINOR__ >= 6)
> /* Force a compilation error if condition is true */
> #define BUILD_BUG_ON(cond) ({ _Static_assert(!(cond), "!(" #cond ")"); })
>
--
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-01-23 11:33 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 3:16 [RFC v4 0/8] SMMUv3 driver Sameer Goel
2017-12-19 3:16 ` [RFC v4 1/8] Port WARN_ON_ONCE() from Linux Sameer Goel
2018-01-23 11:33 ` Julien Grall [this message]
2018-01-23 16:13 ` Wei Liu
2018-01-26 1:45 ` Sameer Goel
2017-12-19 3:16 ` [RFC v4 2/8] xen/bitops: Rename LOG_2 to ilog2 Sameer Goel
2018-01-23 11:36 ` Julien Grall
2018-01-23 11:39 ` Roger Pau Monné
2018-01-23 11:44 ` Julien Grall
2018-01-23 12:10 ` Roger Pau Monné
2018-01-23 12:17 ` Julien Grall
2017-12-19 3:16 ` [RFC v4 3/8] xen/linux_compat: Add a Linux compat header Sameer Goel
2018-01-23 16:28 ` Wei Liu
2018-01-23 16:51 ` Roger Pau Monné
2018-02-09 17:54 ` Sameer Goel
2017-12-19 3:16 ` [RFC v4 4/8] passthrough/arm: Modify SMMU driver to use generic device definition Sameer Goel
2018-01-23 11:41 ` Julien Grall
2017-12-19 3:17 ` [RFC v4 5/8] Add verbatim copy of arm-smmu-v3.c from Linux Sameer Goel
2017-12-19 3:17 ` [RFC v4 6/8] xen/iommu: smmu-v3: Add Xen specific code to enable the ported driver Sameer Goel
2018-01-03 5:47 ` Manish Jaggi
2018-01-15 20:34 ` Julien Grall
2018-01-16 12:37 ` Manish Jaggi
2018-01-16 13:13 ` Julien Grall
2018-01-23 15:18 ` Julien Grall
2018-02-09 17:56 ` Sameer Goel
2018-02-09 18:11 ` Julien Grall
2017-12-19 3:17 ` [RFC v4 7/8] xen/smmu: Add a new config define for legacy SMMU Sameer Goel
2018-01-23 15:26 ` Julien Grall
2017-12-19 3:17 ` [RFC v4 8/8] drivers/passthrough/arm: Refactor code for arm smmu drivers Sameer Goel
2018-01-03 5:34 ` Manish Jaggi
2018-01-15 20:41 ` Julien Grall
2018-01-16 12:40 ` Manish Jaggi
2018-01-16 13:14 ` Julien Grall
2018-01-16 13:27 ` Manish Jaggi
2018-01-16 13:40 ` Julien Grall
2018-01-17 6:37 ` Manish Jaggi
2018-01-23 15:38 ` Julien Grall
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=3eaf2c0e-94e4-8161-985b-3704fbfd4c96@linaro.org \
--to=julien.grall@linaro.org \
--cc=Andrew.Cooper3@citrix.com \
--cc=Ian.Jackson@citrix.com \
--cc=andre.przywara@linaro.org \
--cc=george.dunlap@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=julien.grall@arm.com \
--cc=mjaggi@caviumnetworks.com \
--cc=nd@arm.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).