From: Cornelia Huck <cohuck@redhat.com>
To: "Cho, Yu-Chen" <acho@suse.com>,
qemu-devel@nongnu.org, qemu-s390x@nongnu.org
Cc: thuth@redhat.com, david@redhat.com, richard.henderson@linaro.org,
pasic@linux.ibm.com, borntraeger@de.ibm.com, cfontana@suse.de,
pbonzini@redhat.com, acho@suse.com
Subject: Re: [RFC v4 11/14] target/s390x: remove kvm-stub.c
Date: Wed, 02 Jun 2021 12:44:09 +0200 [thread overview]
Message-ID: <87sg20pmva.fsf@redhat.com> (raw)
In-Reply-To: <20210524025256.22252-11-acho@suse.com>
On Mon, May 24 2021, "Cho, Yu-Chen" <acho@suse.com> wrote:
> all function calls are protected by kvm_enabled(),
> so we should not need the stubs.
>
> Signed-off-by: Claudio Fontana <cfontana@suse.de>
> Signed-off-by: Cho, Yu-Chen <acho@suse.com>
> ---
> target/s390x/kvm-stub.c | 126 ---------------------------------------
> target/s390x/meson.build | 2 +-
> 2 files changed, 1 insertion(+), 127 deletions(-)
> delete mode 100644 target/s390x/kvm-stub.c
(...)
> -int kvm_s390_get_gs(void)
> -{
> - return 0;
> -}
Unrelated to this patch: Nobody seems to call kvm_s390_get_gs()
(anymore?); are we missing something, or can that function be removed?
next prev parent reply other threads:[~2021-06-02 10:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 2:52 [RFC v4 01/14] target/s390x: meson: add target_user_arch Cho, Yu-Chen
2021-05-24 2:52 ` [RFC v4 02/14] hw/s390x: rename tod-qemu.c to tod-tcg.c Cho, Yu-Chen
2021-05-24 2:52 ` [RFC v4 03/14] hw/s390x: only build tod-tcg from the CONFIG_TCG build Cho, Yu-Chen
2021-05-24 2:52 ` [RFC v4 04/14] hw/s390x: tod: make explicit checks for accelerators when initializing Cho, Yu-Chen
2021-05-24 2:52 ` [RFC v4 05/14] target/s390x: remove tcg-stub.c Cho, Yu-Chen
2021-05-24 2:52 ` [RFC v4 06/14] target/s390x: start moving TCG-only code to tcg/ Cho, Yu-Chen
2021-06-02 9:48 ` Cornelia Huck
2021-05-24 2:52 ` [RFC v4 07/14] target/s390x: move sysemu-only code out to cpu-sysemu.c Cho, Yu-Chen
2021-06-02 10:05 ` Cornelia Huck
2021-05-24 2:52 ` [RFC v4 08/14] target/s390x: split cpu-dump from helper.c Cho, Yu-Chen
2021-06-02 10:20 ` Cornelia Huck
2021-05-24 2:52 ` [RFC v4 09/14] target/s390x: make helper.c sysemu-only Cho, Yu-Chen
2021-06-02 10:22 ` Cornelia Huck
2021-05-24 2:52 ` [RFC v4 10/14] target/s390x: use kvm_enabled() to wrap call to kvm_s390_get_hpage_1m Cho, Yu-Chen
2021-06-02 10:41 ` Cornelia Huck
2021-05-24 2:52 ` [RFC v4 11/14] target/s390x: remove kvm-stub.c Cho, Yu-Chen
2021-06-02 10:44 ` Cornelia Huck [this message]
2021-06-02 11:23 ` Thomas Huth
2021-05-24 2:52 ` [RFC v4 12/14] target/s390x: move kvm files into kvm/ Cho, Yu-Chen
2021-05-24 2:52 ` [RFC v4 13/14] target/s390x: split sysemu part of cpu models Cho, Yu-Chen
2021-05-24 2:52 ` [RFC v4 14/14] MAINTAINERS: update s390x directories Cho, Yu-Chen
2021-06-02 10:37 ` Philippe Mathieu-Daudé
2021-06-02 10:48 ` Cornelia Huck
2021-06-02 9:44 ` [RFC v4 01/14] target/s390x: meson: add target_user_arch Cornelia Huck
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=87sg20pmva.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=acho@suse.com \
--cc=borntraeger@de.ibm.com \
--cc=cfontana@suse.de \
--cc=david@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.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).