From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Thomas Lendacky <Thomas.Lendacky@amd.com>,
xen-devel@lists.xen.org,
Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>,
Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>,
sherry.hurwitz@amd.com, shurd@broadcom.com
Subject: Re: [PATCH V4] ns16550: Add support for UART present in Broadcom TruManage capable NetXtreme chips
Date: Fri, 22 Nov 2013 13:09:45 +0000 [thread overview]
Message-ID: <528F5799.6010207@citrix.com> (raw)
In-Reply-To: <528F58BE0200007800105CD2@nat28.tlf.novell.com>
On 22/11/13 12:14, Jan Beulich wrote:
>>>> On 22.11.13 at 11:44, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
>> On 21/11/13 22:50, Aravind Gopalakrishnan wrote:
>>> if ( uart->remapped_io_base )
>>> + {
>>> + sfn = paddr_to_pfn((unsigned long) uart->io_base + PAGE_SIZE);
>>> + efn = paddr_to_pfn((unsigned long) uart->io_base + uart->io_size - 1);
>>> + if ( iomem_deny_access(dom0, sfn, efn) != 0 )
>>> + BUG();
>> BUG_ON(!iomem_deny_access(dom0, sfn, efn))
> Actually, we had more or less agreed to avoid side effects in
> ASSERT() and BUG_ON() expressions (to eliminate the ambiguity
> whether such expressions get always evaluated).
ASSERT()s certain, as the non-debug builds will optimise away call.
BUG/WARN_ON()s are different - they will be executed in all cases.
>
>> is slightly more compact, and has the advantage of showing the action
>> which failed in the BUG message.
> Since when does BUG() should any expression?
Hmm - they don't do they. I was getting my BUG()s and ASSERTS()s mixed up.
next prev parent reply other threads:[~2013-11-22 13:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 22:50 [PATCH V4] ns16550: Add support for UART present in Broadcom TruManage capable NetXtreme chips Aravind Gopalakrishnan
2013-11-22 10:44 ` Andrew Cooper
2013-11-22 12:14 ` Jan Beulich
2013-11-22 13:09 ` Andrew Cooper [this message]
2013-11-22 13:12 ` Jan Beulich
2013-11-22 12:29 ` Jan Beulich
2013-11-22 15:01 ` Aravind Gopalakrishnan
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=528F5799.6010207@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Aravind.Gopalakrishnan@amd.com \
--cc=JBeulich@suse.com \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=Thomas.Lendacky@amd.com \
--cc=sherry.hurwitz@amd.com \
--cc=shurd@broadcom.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.