qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: Peter Lieven <pl@kamp.de>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, famz@redhat.com, benoit@irqsave.net,
	ronniesahlberg@gmail.com, armbru@redhat.com, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCHv5 1/6] util: introduce MIN_NON_ZERO
Date: Mon, 27 Oct 2014 09:24:45 +0100	[thread overview]
Message-ID: <544E014D.5070802@redhat.com> (raw)
In-Reply-To: <1414253919-3044-2-git-send-email-pl@kamp.de>

On 2014-10-25 at 18:18, Peter Lieven wrote:
> at least in block layer we have the case of limits being defined for a
> BlockDriverState. However, in this context often zero (0) has the special
> meanining of undefined which means no limit. If two of those limits are
> combined and the minimum is needed the minimum function should only return
> zero if both parameters are zero.
>
> Signed-off-by: Peter Lieven <pl@kamp.de>
> ---
>   include/qemu/osdep.h |    6 ++++++
>   1 file changed, 6 insertions(+)
>
> diff --git a/include/qemu/osdep.h b/include/qemu/osdep.h
> index 1565404..bcdf088 100644
> --- a/include/qemu/osdep.h
> +++ b/include/qemu/osdep.h
> @@ -68,6 +68,12 @@ typedef signed int              int_fast16_t;
>   #define MAX(a, b) (((a) > (b)) ? (a) : (b))
>   #endif
>   
> +/* Minimum function that returns zero only iff both values are zero.
> + * Intended for use with unsigned values only. */
> +#ifndef MIN_NON_ZERO
> +#define MIN_NON_ZERO(a, b) (((a != 0) && (a) < (b)) ? (a) : (b))

*cough* This should be (((a) != 0 && (a) < (b)) ? (a) : (b)), so the 
parentheses need to enclose the "a", not the "a != 0".

I guess the maintainer could fix that up, though.

And with that fixed, of course,

Reviewed-by: Max Reitz <mreitz@redhat.com>

> +#endif
> +
>   #ifndef ROUND_UP
>   #define ROUND_UP(n,d) (((n) + (d) - 1) & -(d))
>   #endif

  reply	other threads:[~2014-10-27  8:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-25 16:18 [Qemu-devel] [PATCHv5 0/6] introduce max_transfer_length Peter Lieven
2014-10-25 16:18 ` [Qemu-devel] [PATCHv5 1/6] util: introduce MIN_NON_ZERO Peter Lieven
2014-10-27  8:24   ` Max Reitz [this message]
2014-10-25 16:18 ` [Qemu-devel] [PATCHv5 2/6] BlockLimits: introduce max_transfer_length Peter Lieven
2014-10-25 16:18 ` [Qemu-devel] [PATCHv5 3/6] block/iscsi: set max_transfer_length Peter Lieven
2014-10-27  8:28   ` Max Reitz
2014-10-27  8:36     ` Peter Lieven
2014-10-27  8:44       ` Max Reitz
2014-10-27  8:47         ` Peter Lieven
2014-10-27  9:04           ` Max Reitz
2014-10-25 16:18 ` [Qemu-devel] [PATCHv5 4/6] block: avoid creating oversized writes in multiwrite_merge Peter Lieven
2014-10-25 16:18 ` [Qemu-devel] [PATCHv5 5/6] block/iscsi: limit to INT_MAX throughout iscsi_refresh_limits Peter Lieven
2014-10-27  8:32   ` Max Reitz
2014-10-27  8:35     ` Peter Lieven
2014-10-27  8:38       ` Max Reitz
2014-10-25 16:18 ` [Qemu-devel] [PATCHv5 6/6] block/iscsi: check for oversized requests Peter Lieven
2014-10-27  8:35   ` Max Reitz

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=544E014D.5070802@redhat.com \
    --to=mreitz@redhat.com \
    --cc=armbru@redhat.com \
    --cc=benoit@irqsave.net \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pl@kamp.de \
    --cc=qemu-devel@nongnu.org \
    --cc=ronniesahlberg@gmail.com \
    --cc=stefanha@redhat.com \
    /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).