From: Cornelia Huck <cohuck@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Janosch Frank <frankja@linux.vnet.ibm.com>,
KVM <kvm@vger.kernel.org>,
linux-s390 <linux-s390@vger.kernel.org>,
David Hildenbrand <david@redhat.com>
Subject: Re: [PATCH v2 2/2] KVM: s390: use switch vs jump table in intercept.c
Date: Tue, 6 Feb 2018 13:51:25 +0100 [thread overview]
Message-ID: <20180206135125.52d9d168.cohuck@redhat.com> (raw)
In-Reply-To: <20180206124700.19177-1-borntraeger@de.ibm.com>
On Tue, 6 Feb 2018 12:47:00 +0000
Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> Instead of having huge jump tables for function selection,
> let's use normal switch/case statements for the instruction
> handlers in intercept.c We can now also get rid of
> intercept_handler_t.
>
> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
> Reviewed-by: David Hildenbrand <david@redhat.com>
> ---
> arch/s390/kvm/intercept.c | 51 +++++++++++++++++++++++++++--------------------
> arch/s390/kvm/kvm-s390.h | 2 --
> 2 files changed, 29 insertions(+), 24 deletions(-)
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
next prev parent reply other threads:[~2018-02-06 12:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 11:21 [PATCH 0/2] KVM: s390: avoid jump tables Christian Borntraeger
2018-02-06 11:21 ` [PATCH 1/2] KVM: s390: use switch vs jump table in priv.c Christian Borntraeger
2018-02-06 12:02 ` Cornelia Huck
2018-02-06 12:32 ` David Hildenbrand
2018-02-08 8:01 ` Heiko Carstens
2018-02-08 9:16 ` Janosch Frank
2018-02-06 11:21 ` [PATCH 2/2] KVM: s390: use switch vs jump table in intercept.c Christian Borntraeger
2018-02-06 12:04 ` Cornelia Huck
2018-02-06 12:05 ` Christian Borntraeger
2018-02-06 12:34 ` David Hildenbrand
2018-02-06 12:47 ` [PATCH v2 " Christian Borntraeger
2018-02-06 12:51 ` Cornelia Huck [this message]
2018-02-08 8:30 ` Janosch Frank
2018-02-06 12:30 ` [PATCH 0/2] KVM: s390: avoid jump tables David Hildenbrand
2018-02-06 12:36 ` Christian Borntraeger
2018-02-06 12:42 ` David Hildenbrand
2018-02-08 8:58 ` Heiko Carstens
2018-02-08 9:07 ` Christian Borntraeger
2018-02-08 9:18 ` Christian Borntraeger
2018-02-08 10:09 ` Christian Borntraeger
2018-02-08 10:18 ` 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=20180206135125.52d9d168.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.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).