From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>, Tim Deegan <tim@xen.org>
Cc: xen-devel <xen-devel@lists.xenproject.org>, Keir Fraser <keir@xen.org>
Subject: Re: [PATCH v2 1/3] x86: also allow REP STOS emulation acceleration
Date: Fri, 9 Jan 2015 12:46:45 +0000 [thread overview]
Message-ID: <54AFCDB5.5010105@citrix.com> (raw)
In-Reply-To: <54AFD355020000780005321C@mail.emea.novell.com>
On 09/01/15 12:10, Jan Beulich wrote:
>>>> On 09.01.15 at 12:45, <tim@xen.org> wrote:
>> At 11:24 +0000 on 09 Jan (1420799087), Jan Beulich wrote:
>>>>>> On 09.01.15 at 12:18, <tim@xen.org> wrote:
>>>>>> + default:
>>>>>> + xfree(buf);
>>>>>> + ASSERT(!buf);
>>>> looks dodgy...
>>> In which way? The "default" is supposed to be unreachable, and sits
>>> in the else branch to an if(!buf), i.e. in a release build we'll correctly
>>> free the buffer, while in a debug build the ASSERT() will trigger.
>> Oh I see. Can you please use ASSERT(0) for that?
> I sincerely dislike ASSERT(0), but if that's the only way to get
> the patch accepted...
>
> Jan
>
Perhaps introducing ASSERT_UNREACHABLE() as an alternative which is more
obvious in nature than both ASSERT(!buf) and ASSERT(0) ?
~Andrew
next prev parent reply other threads:[~2015-01-09 12:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 15:47 [PATCH 0/3] x86: XSA-112 follow-ups Jan Beulich
2015-01-08 15:50 ` [PATCH 1/3] x86: also allow REP STOS emulation acceleration Jan Beulich
2015-01-08 16:16 ` Tim Deegan
2015-01-08 16:29 ` Jan Beulich
2015-01-08 16:56 ` Tim Deegan
2015-01-08 17:05 ` Jan Beulich
2015-01-08 18:15 ` Tim Deegan
2015-01-08 19:29 ` Andrew Cooper
2015-01-09 8:42 ` Jan Beulich
2015-01-09 10:27 ` [PATCH v2 " Jan Beulich
2015-01-09 10:56 ` Andrew Cooper
2015-01-09 11:10 ` Jan Beulich
2015-01-09 11:18 ` Tim Deegan
2015-01-09 11:24 ` Jan Beulich
2015-01-09 11:45 ` Tim Deegan
2015-01-09 12:10 ` Jan Beulich
2015-01-09 12:46 ` Andrew Cooper [this message]
2015-01-09 15:20 ` Tim Deegan
2015-01-12 14:54 ` George Dunlap
2015-01-12 15:27 ` Jan Beulich
2015-01-08 15:51 ` [PATCH 2/3] x86/HVM: drop pointless parameters from vIOAPIC internal routines Jan Beulich
2015-01-08 16:13 ` Tim Deegan
2015-01-08 15:52 ` [PATCH 3/3] x86/HVM: vMSI simplification Jan Beulich
2015-01-08 16:14 ` Tim Deegan
2015-01-08 16:30 ` Jan Beulich
2015-01-08 16:33 ` Tim Deegan
2015-01-09 10:23 ` Andrew Cooper
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=54AFCDB5.5010105@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=tim@xen.org \
--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 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.