From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 1/1] Make qemu_peek_buffer loop until it gets it's data
Date: Mon, 24 Mar 2014 09:52:22 +0000 [thread overview]
Message-ID: <20140324095221.GB3829@work-vm> (raw)
In-Reply-To: <532CA4C7.8060204@redhat.com>
* Eric Blake (eblake@redhat.com) wrote:
> On 03/21/2014 01:30 PM, Dr. David Alan Gilbert (git) wrote:
> > From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> >
> > Make qemu_peek_buffer repatedly call fill_buffer until it gets
> > all the data it requires, or until there is an error.
> >
> > At the moment, qemu_peek_buffer will try one qemu_fill_buffer if there
> > isn't enough data waiting, however the kernel is entitled to return
> > just a few bytes, and still leave qemu_peek_buffer with less bytes
> > than it needed. I've seen this fail in a dev world, and I think it
> > could theoretically fail in the peeking of the subsection headers in
> > the current world.
> >
> > Comment qemu_peek_byte to point out it's not guaranteed to work for
>
> > +/*
> > + * Attempt to fill the buffer from the underlying file
> > + * Returns the number of bytes read, or -ve value for an error.
>
> s/-ve/negative/ - it is not an obvious abbreviation, and I only knew
> what it meant because you have been told to fix it in other patches.
If I need to recut it for another reason I'll change it.
However, it's a perfectly common abbreviation that's widely used
(hundreds of times in the kernel source for example).
Dave
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2014-03-24 9:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 19:30 [Qemu-devel] [PATCH v2 1/1] Make qemu_peek_buffer loop until it gets it's data Dr. David Alan Gilbert (git)
2014-03-21 20:44 ` Eric Blake
2014-03-24 9:52 ` Dr. David Alan Gilbert [this message]
2014-03-24 13:16 ` Eric Blake
2014-03-26 16:48 ` Markus Armbruster
2014-03-26 17:18 ` Dr. David Alan Gilbert
2014-03-27 8:16 ` Markus Armbruster
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=20140324095221.GB3829@work-vm \
--to=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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).