qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Varad Gautam <varadgautam@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] First Patch, Requesting Comments‏
Date: Mon, 18 Nov 2013 19:19:47 +0530	[thread overview]
Message-ID: <1384782589-9333-1-git-send-email-varadgautam@gmail.com> (raw)


Hi! I'm new here, and am working on my first bug. I have posted a patch
for Bug#603872 [1]. It's incomplete right now, but please have a look and
tell me if I'm headed in the right direction. (I don't know if I can send
incomplete patches to the mailing list for suggestions or if I run into
some problems.)
 
Usecase: `qemu-img convert` with -p now shows the write speed.
 
I have a few doubts relating to the patch.
 
1. I'm calculating the speed using the time taken to run the for(;;)
at qemu-img.c:1477. I figured that every time this loop runs, n1
sectors are converted, and so I calculate the write_speed
accordingly. Is this correct?
 
2. I have changed qemu-progress.c:qemu_progress_print() to take in a
speed parameter, thinking that it would be the best option. Should I
do it some other way instead (maybe write another function to print
just speed)?
 
Also, what does IO_BUF_SIZE in the same file relate to?
 
Thanks.
Varad
 
[1] https://bugs.launchpad.net/qemu/+bug/603872

             reply	other threads:[~2013-11-18 13:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-18 13:49 Varad Gautam [this message]
2013-11-18 15:45 ` [Qemu-devel] First Patch, Requesting Comments‏ Max Filippov
2013-11-18 15:59   ` [Qemu-devel] First Patch, Requesting Comments Varad Gautam
2013-11-18 16:45     ` Andreas Färber
2013-11-18 17:01       ` Eric Blake
2013-11-18 18:41         ` Varad Gautam
2013-11-18 19:01           ` Eric Blake

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=1384782589-9333-1-git-send-email-varadgautam@gmail.com \
    --to=varadgautam@gmail.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).