From: Peter Maydell <peter.maydell@linaro.org>
To: Stefan Weil <weil@mail.berlios.de>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH] Remove unneeded function parameter from gen_pc_load
Date: Sun, 17 Apr 2011 22:34:47 +0100 [thread overview]
Message-ID: <BANLkTi=_VJ6HSx5ubObZWijE-i8o898-OQ@mail.gmail.com> (raw)
In-Reply-To: <4DAB569A.2020604@mail.berlios.de>
On 17 April 2011 22:07, Stefan Weil <weil@mail.berlios.de> wrote:
> Am 17.04.2011 20:27, schrieb Aurelien Jarno:
>>
>> On Thu, Apr 14, 2011 at 08:50:00PM +0200, Stefan Weil wrote:
>>>
>>> Am 13.04.2011 23:05, schrieb Peter Maydell:
>>>>
>>>> On 13 April 2011 21:38, Stefan Weil <weil@mail.berlios.de> wrote:
>>>>>
>>>>> gen_pc_load was introduced in commit
>>>>> d2856f1ad4c259e5766847c49acbb4e390731bd4.
>>>>> The only reason for parameter searched_pc was
>>>>> a debug statement in target-i386/translate.c.
>>>>>
>>>>> Remove searched_pc from the debug statement
>>>>> and from the parameter list of gen_pc_load.
>>>>
>>>> No issues with the meat of the patch, but if we're going to
>>>> change all the callers and implementations of this anyway,
>>>> is there any appetite for giving it a more appropriate name?
>>>> It doesn't generate any code, it affects more than just the
>>>> pc, and it doesn't do a load...
>>>>
>>>> restore_state_to_opc() ? set_env_for_opc() ?
>>>>
>>>> -- PMM
>>>
>>>
>>> What about cpu_restore_pc()? That's not always the whole truth,
>>> but it's always the main action done in function n.n. which currently
>>> is called gen_pc_load.
>>>
>>> Or cpu_restore_helper()? Helper is very generic - it always fits.
>>>
>>> Aurelien, please feel free to choose a name which suits bests.
>>> I don't mind if you simply patch my patch, create a new one
>>> or tell me which name should go into a new version of the patch
>>> so I can send it.
>>>
>>
>> As Peter said, the function is doing more than simply restoring the
>> pc. I am fine with the name he proposed, I think restore_state_to_opc()
>> is a bit better.
>
> Ok, so I'll send a new patch which also replaces gen_pc_load
> by restore_state_to_op.
That's _to_opc, not _to_op : I was trying to be consistent with
the naming of the gen_opc_* arrays.
-- PMM
next prev parent reply other threads:[~2011-04-17 21:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 20:38 [Qemu-devel] [PATCH] Remove unneeded function parameter from gen_pc_load Stefan Weil
2011-04-13 21:05 ` Peter Maydell
2011-04-14 18:50 ` Stefan Weil
2011-04-17 18:27 ` Aurelien Jarno
2011-04-17 21:07 ` Stefan Weil
2011-04-17 21:34 ` Peter Maydell [this message]
2011-04-17 21:43 ` Aurelien Jarno
2011-04-18 16:35 ` Stefan Weil
2011-04-18 16:39 ` [Qemu-devel] [PATCH 1/2] Remove unused function parameters from gen_pc_load and rename the function Stefan Weil
2011-04-18 17:15 ` Peter Maydell
2011-04-20 9:03 ` [Qemu-devel] [PULL] Remove unused function parameters Stefan Weil
2011-04-20 10:53 ` Aurelien Jarno
2011-04-20 10:57 ` Peter Maydell
2011-04-18 16:39 ` [Qemu-devel] [PATCH 2/2] Remove unused function parameter from cpu_restore_state Stefan Weil
2011-04-18 17:28 ` Peter Maydell
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='BANLkTi=_VJ6HSx5ubObZWijE-i8o898-OQ@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
--cc=weil@mail.berlios.de \
/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).