All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
	Julien Grall <julien.grall@arm.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Stefano Stabellini <sstabellini@kernel.org>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: find_next{,_zero}_bit() inconsistencies
Date: Tue, 30 Aug 2016 10:26:15 +0100	[thread overview]
Message-ID: <57C55137.7040707@citrix.com> (raw)
In-Reply-To: <57C43FA50200007800109C22@prv-mh.provo.novell.com>

On 29/08/16 12:59, Jan Beulich wrote:
> Hello,
> 
> in the context of
> https://lists.xenproject.org/archives/html/xen-devel/2016-08/msg03068.html
> I once again came across the different behavior our various
> implementations of the $subject functions, in particular their varying
> handling of the offset argument being greater / greater-or-equal
> the size argument. Shouldn't we settle on a single, uniform model,
> which might be
> 1) offset >= size is valid, returns size,
> 2) offset == size is valid, returns size, offset > size is invalid,
> 3) offset >= size is invalid.

What does the linux implementation do?

David

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  parent reply	other threads:[~2016-08-30  9:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-29 11:59 find_next{,_zero}_bit() inconsistencies Jan Beulich
2016-08-29 12:03 ` Andrew Cooper
2016-08-29 12:38   ` Jan Beulich
2016-08-30  9:26 ` David Vrabel [this message]
2016-08-30 10:08   ` Jan Beulich
2016-08-30 12:32     ` 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=57C55137.7040707@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=julien.grall@arm.com \
    --cc=sstabellini@kernel.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.