From: Paolo Bonzini <pbonzini@redhat.com>
To: "Nutaro, James J." <nutarojj@ornl.gov>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v6] qqq: module for synchronizing with a simulation
Date: Mon, 9 Jan 2017 18:10:20 +0100 [thread overview]
Message-ID: <33a6f57d-4563-ec4a-f77f-1a15ca57c19d@redhat.com> (raw)
In-Reply-To: <283fd6b709734ccdbeb6d217f8b32043@EXCHCS32.ornl.gov>
On 09/01/2017 18:04, Nutaro, James J. wrote:
> Thanks again Paolo. When I change the command line switches, is it best to submit a whole new version of the patch? Or is there another method for managing patch revisions?
Yes, submit a new version, then put
v6->v7: did this and that [Paolo]
at the end of the commit message, where the square brackets mean
"suggested by...".
Thanks,
Paolo
>
> -----Original Message-----
> From: Paolo Bonzini [mailto:pbonzini@redhat.com]
> Sent: Thursday, January 05, 2017 10:27 AM
> To: Nutaro, James J.; qemu-devel@nongnu.org
> Subject: Re: [PATCH v6] qqq: module for synchronizing with a simulation
>
>
>
> On 05/01/2017 16:07, James J. Nutaro wrote:
>> This patch adds an interface for pacing the execution of QEMU to match an external
>> simulation clock. Its aim is to permit QEMU to be used as a module within a
>> larger simulation system.
>>
>> Signed-off-by: James J. Nutaro <nutarojj@ornl.gov>
>
> What's the difference between v5 and v6?
>
>> +(2) Fork QEMU with the appropriate command line arguments.
>> + The -qqq part of the argument will look something like
>> +
>> + -qqq sock=socks[1]
>
> No need for -qqq, just make it "-icount extclock=FD".
>
> Paolo
>
next prev parent reply other threads:[~2017-01-09 17:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 15:07 [Qemu-devel] [PATCH v6] qqq: module for synchronizing with a simulation James J. Nutaro
2017-01-05 15:27 ` Paolo Bonzini
2017-01-05 16:17 ` Nutaro, James J.
2017-01-09 17:04 ` Nutaro, James J.
2017-01-09 17:10 ` Paolo Bonzini [this message]
2017-01-17 22:28 ` Nutaro, James J.
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=33a6f57d-4563-ec4a-f77f-1a15ca57c19d@redhat.com \
--to=pbonzini@redhat.com \
--cc=nutarojj@ornl.gov \
--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).