From: Cornelia Huck <cohuck@redhat.com>
To: Janosch Frank <frankja@linux.ibm.com>
Cc: thuth@redhat.com, pmorel@linux.ibm.com, david@redhat.com,
qemu-devel@nongnu.org, borntraeger@de.ibm.com,
qemu-s390x@nongnu.org, mihajlov@linux.ibm.com
Subject: Re: [PATCH v3 4/5] s390x: Move clear reset
Date: Mon, 25 Nov 2019 14:37:14 +0100 [thread overview]
Message-ID: <20191125143714.1c7c5937.cohuck@redhat.com> (raw)
In-Reply-To: <20191125090348.27010-5-frankja@linux.ibm.com>
On Mon, 25 Nov 2019 04:03:47 -0500
Janosch Frank <frankja@linux.ibm.com> wrote:
> Let's also move the clear reset function into the reset handler.
>
> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
> ---
> target/s390x/cpu-qom.h | 1 +
> target/s390x/cpu.c | 58 +++++++++++++-----------------------------
> 2 files changed, 18 insertions(+), 41 deletions(-)
>
> @@ -453,6 +424,11 @@ static Property s390x_cpu_properties[] = {
> DEFINE_PROP_END_OF_LIST()
> };
>
> +static void s390_cpu_reset_clear(CPUState *s)
> +{
> + return s390_cpu_reset(s, S390_CPU_RESET_CLEAR);
> +}
> +
> static void s390_cpu_class_init(ObjectClass *oc, void *data)
> {
> S390CPUClass *scc = S390_CPU_CLASS(oc);
> @@ -469,7 +445,7 @@ static void s390_cpu_class_init(ObjectClass *oc, void *data)
> scc->load_normal = s390_cpu_load_normal;
> #endif
> scc->reset = s390_cpu_reset;
> - cc->reset = s390_cpu_full_reset;
> + cc->reset = s390_cpu_reset_clear;
> cc->class_by_name = s390_cpu_class_by_name,
> cc->has_work = s390_cpu_has_work;
> #ifdef CONFIG_TCG
One thing I liked about the previous naming is that it is more obvious
that the clear reset is actually the full reset of a cpu. Not sure if
keeping that is better than matching the function name to the name of
the reset being performed. Opinions?
next prev parent reply other threads:[~2019-11-25 13:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 9:03 [PATCH v3 0/5] s390x: Reset cleanup Janosch Frank
2019-11-25 9:03 ` [PATCH v3 1/5] s390x: Don't do a normal reset on the initial cpu Janosch Frank
2019-11-25 13:11 ` Cornelia Huck
2019-11-25 9:03 ` [PATCH v3 2/5] s390x: Move reset normal to shared reset handler Janosch Frank
2019-11-25 13:19 ` Cornelia Huck
2019-11-27 17:45 ` David Hildenbrand
2019-11-25 9:03 ` [PATCH v3 3/5] s390x: Move initial reset Janosch Frank
2019-11-25 9:03 ` [PATCH v3 4/5] s390x: Move clear reset Janosch Frank
2019-11-25 13:37 ` Cornelia Huck [this message]
2019-11-25 13:49 ` Janosch Frank
2019-11-25 15:42 ` Cornelia Huck
2019-11-25 9:03 ` [PATCH v3 5/5] s390x: Beautify diag308 handling Janosch Frank
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=20191125143714.1c7c5937.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=mihajlov@linux.ibm.com \
--cc=pmorel@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@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).