From: "Lluís Vilanova" <vilanova@ac.upc.edu>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/3] Add "qemu_reset_vcpu"
Date: Fri, 16 Sep 2011 20:43:52 +0200 [thread overview]
Message-ID: <87aaa45nvb.fsf@ginnungagap.bsc.es> (raw)
In-Reply-To: <4E738263.3090307@siemens.com> (Jan Kiszka's message of "Fri, 16 Sep 2011 19:07:47 +0200")
Jan Kiszka writes:
> On 2011-09-16 19:01, Lluís Vilanova wrote:
>> Mimics the already-existing "qemu_init_vcpu".
> Bad name as it implies something important happens inside. Call it
> trace_reset_vcpu because that is what it will do.
I just thought it is much cleaner to call a generic "qemu_reset_vcpu"
function that _might_ do something related to resetting the vCPU state,
regardless of whether there is a tracing event for it or not.
Otherwise if someone wants to add some generic vCPU-resetting code in
the future, the tracing function might end up in the target-specific
code instead of the generic qemu code.
If you still think this is a bad idea I'll resend a patch with both
events renamed into trace_vcpu_init/trace_vcpu_reset.
Thanks,
Lluis
--
"And it's much the same thing with knowledge, for whenever you learn
something new, the whole world becomes that much richer."
-- The Princess of Pure Reason, as told by Norton Juster in The Phantom
Tollbooth
prev parent reply other threads:[~2011-09-16 18:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 17:01 [Qemu-devel] [PATCH 1/3] Add "qemu_reset_vcpu" Lluís Vilanova
2011-09-16 17:01 ` [Qemu-devel] [PATCH 2/3] trace: Add "qemu_init_vcpu" event Lluís Vilanova
2011-09-16 17:01 ` [Qemu-devel] [PATCH 3/3] trace: Add "qemu_reset_vcpu" event Lluís Vilanova
2011-09-16 17:07 ` [Qemu-devel] [PATCH 1/3] Add "qemu_reset_vcpu" Jan Kiszka
2011-09-16 18:43 ` Lluís Vilanova [this message]
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=87aaa45nvb.fsf@ginnungagap.bsc.es \
--to=vilanova@ac.upc.edu \
--cc=jan.kiszka@siemens.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 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.