From: "Michael S. Tsirkin" <mst@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/6] range: add min/max operations on ranges
Date: Tue, 10 Sep 2013 15:51:10 +0300 [thread overview]
Message-ID: <20130910125110.GA2121@redhat.com> (raw)
In-Reply-To: <20130910113554.7d988986@nial.usersys.redhat.com>
On Tue, Sep 10, 2013 at 11:35:54AM +0200, Igor Mammedov wrote:
> On Wed, 4 Sep 2013 13:48:35 +0300
> "Michael S. Tsirkin" <mst@redhat.com> wrote:
>
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> > ---
> > include/qemu/range.h | 17 +++++++++++++++++
> > 1 file changed, 17 insertions(+)
> >
> > diff --git a/include/qemu/range.h b/include/qemu/range.h
> > index 4a0780d..1c688ca 100644
> > --- a/include/qemu/range.h
> > +++ b/include/qemu/range.h
> > @@ -17,6 +17,23 @@ struct Range {
> > uint64_t end; /* 1 + the last byte. 0 if range empty or ends at ~0x0LL. */
> > };
> >
> > +static inline void range_extend(Range *range, Range *extend_by)
> doc comment what it does pls.
>
> > +{
> > + if (!extend_by->begin && !extend_by->end) {
> > + return;
> > + }
> > + if (!range->begin && !range->end) {
> > + *range = *extend_by;
> > + return;
> > + }
> > + if (range->begin > extend_by->begin) {
> > + range->begin = extend_by->begin;
> > + }
> > + if (range->end - 1 < extend_by->end - 1) {
> (foo)->end could be 0 at this point leading to overflow when subtracted,
> is it intended to be so?
Absolutely - as the comment near this field definition states:
0 means region ends at ~0x0LL.
> > + range->end = extend_by->end;
> > + }
> > +}
> > +
> > /* Get last byte of a range from offset + length.
> > * Undefined for ranges that wrap around 0. */
> > static inline uint64_t range_get_last(uint64_t offset, uint64_t len)
>
next prev parent reply other threads:[~2013-09-10 12:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 10:48 [Qemu-devel] [PATCH 0/6] pci: keep window properties up to date Michael S. Tsirkin
2013-09-04 10:48 ` [Qemu-devel] [PATCH 1/6] q35: make pci window address/size match guest cfg Michael S. Tsirkin
2013-09-10 13:37 ` Igor Mammedov
2013-09-10 13:46 ` Michael S. Tsirkin
2013-09-10 13:46 ` Igor Mammedov
2013-09-10 13:53 ` Michael S. Tsirkin
2013-09-10 14:09 ` Igor Mammedov
2013-09-10 14:16 ` Michael S. Tsirkin
2013-09-10 15:05 ` Igor Mammedov
2013-09-10 15:25 ` Michael S. Tsirkin
2013-09-04 10:48 ` [Qemu-devel] [PATCH 2/6] range: add Range to typedefs Michael S. Tsirkin
2013-09-04 10:48 ` [Qemu-devel] [PATCH 3/6] range: add min/max operations on ranges Michael S. Tsirkin
2013-09-10 9:35 ` Igor Mammedov
2013-09-10 12:51 ` Michael S. Tsirkin [this message]
2013-09-04 10:48 ` [Qemu-devel] [PATCH 4/6] pci: add helper to retrieve the 64-bit range Michael S. Tsirkin
2013-09-10 13:40 ` Igor Mammedov
2013-09-10 13:50 ` Michael S. Tsirkin
2013-09-10 17:05 ` Igor Mammedov
2013-09-10 17:28 ` Michael S. Tsirkin
2013-09-04 10:48 ` [Qemu-devel] [PATCH 5/6] q35: use 64 bit window programmed by guest Michael S. Tsirkin
2013-09-10 14:12 ` Igor Mammedov
2013-09-10 14:19 ` Michael S. Tsirkin
2013-09-04 10:48 ` [Qemu-devel] [PATCH 6/6] piix: " Michael S. Tsirkin
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=20130910125110.GA2121@redhat.com \
--to=mst@redhat.com \
--cc=imammedo@redhat.com \
--cc=qemu-devel@nongnu.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).