From: Paolo Bonzini <pbonzini@redhat.com>
To: Qian Cai <cai@lca.pw>, Jim Mattson <jmattson@google.com>
Cc: Sean Christopherson <sean.j.christopherson@intel.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Joerg Roedel <joro@8bytes.org>, kvm list <kvm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kvm/emulate: fix a -Werror=cast-function-type
Date: Mon, 17 Feb 2020 17:32:02 +0100 [thread overview]
Message-ID: <030ced86-5ef0-0a2e-7c66-dbfb1416b8b5@redhat.com> (raw)
In-Reply-To: <1581950844.7365.82.camel@lca.pw>
On 17/02/20 15:47, Qian Cai wrote:
> On Fri, 2020-02-14 at 20:33 +0100, Paolo Bonzini wrote:
>> On 14/02/20 20:14, Qian Cai wrote:
>>>> It seems misguided to define a local variable just to get an implicit
>>>> cast from (void *) to (fastop_t). Sean's first suggestion gives you
>>>> the same implicit cast without the local variable. The second
>>>> suggestion makes both casts explicit.
>>>
>>> OK, I'll do a v2 using the first suggestion which looks simpler once it passed
>>> compilations.
>>>
>>
>> Another interesting possibility is to use an unnamed union of a
>> (*execute) function pointer and a (*fastop) function pointer.
>>
>
> This?
Yes, perfect. Can you send it with Signed-off-by and all that?
Thanks,
Paolo
> diff --git a/arch/x86/include/asm/kvm_emulate.h
> b/arch/x86/include/asm/kvm_emulate.h
> index 03946eb3e2b9..2a8f2bd2e5cf 100644
> --- a/arch/x86/include/asm/kvm_emulate.h
> +++ b/arch/x86/include/asm/kvm_emulate.h
> @@ -292,6 +292,14 @@ enum x86emul_mode {
> #define X86EMUL_SMM_MASK (1 << 6)
> #define X86EMUL_SMM_INSIDE_NMI_MASK (1 << 7)
>
> +/*
> + * fastop functions are declared as taking a never-defined fastop parameter,
> + * so they can't be called from C directly.
> + */
> +struct fastop;
> +
> +typedef void (*fastop_t)(struct fastop *);
> +
> struct x86_emulate_ctxt {
> const struct x86_emulate_ops *ops;
>
> @@ -324,7 +332,10 @@ struct x86_emulate_ctxt {
> struct operand src;
> struct operand src2;
> struct operand dst;
> - int (*execute)(struct x86_emulate_ctxt *ctxt);
> + union {
> + int (*execute)(struct x86_emulate_ctxt *ctxt);
> + fastop_t fop;
> + };
> int (*check_perm)(struct x86_emulate_ctxt *ctxt);
> /*
> * The following six fields are cleared together,
> diff --git a/arch/x86/kvm/emulate.c b/arch/x86/kvm/emulate.c
> index ddbc61984227..dd19fb3539e0 100644
> --- a/arch/x86/kvm/emulate.c
> +++ b/arch/x86/kvm/emulate.c
> @@ -191,25 +191,6 @@
> #define NR_FASTOP (ilog2(sizeof(ulong)) + 1)
> #define FASTOP_SIZE 8
>
> -/*
> - * fastop functions have a special calling convention:
> - *
> - * dst: rax (in/out)
> - * src: rdx (in/out)
> - * src2: rcx (in)
> - * flags: rflags (in/out)
> - * ex: rsi (in:fastop pointer, out:zero if exception)
> - *
> - * Moreover, they are all exactly FASTOP_SIZE bytes long, so functions for
> - * different operand sizes can be reached by calculation, rather than a jump
> - * table (which would be bigger than the code).
> - *
> - * fastop functions are declared as taking a never-defined fastop parameter,
> - * so they can't be called from C directly.
> - */
> -
> -struct fastop;
> -
> struct opcode {
> u64 flags : 56;
> u64 intercept : 8;
> @@ -311,8 +292,19 @@ static void invalidate_registers(struct x86_emulate_ctxt
> *ctxt)
> #define ON64(x)
> #endif
>
> -typedef void (*fastop_t)(struct fastop *);
> -
> +/*
> + * fastop functions have a special calling convention:
> + *
> + * dst: rax (in/out)
> + * src: rdx (in/out)
> + * src2: rcx (in)
> + * flags: rflags (in/out)
> + * ex: rsi (in:fastop pointer, out:zero if exception)
> + *
> + * Moreover, they are all exactly FASTOP_SIZE bytes long, so functions for
> + * different operand sizes can be reached by calculation, rather than a jump
> + * table (which would be bigger than the code).
> + */
> static int fastop(struct x86_emulate_ctxt *ctxt, fastop_t fop);
>
> #define __FOP_FUNC(name) \
> @@ -5683,7 +5675,7 @@ int x86_emulate_insn(struct x86_emulate_ctxt *ctxt)
>
> if (ctxt->execute) {
> if (ctxt->d & Fastop)
> - rc = fastop(ctxt, (fastop_t)ctxt->execute);
> + rc = fastop(ctxt, ctxt->fop);
> else
> rc = ctxt->execute(ctxt);
> if (rc != X86EMUL_CONTINUE)
>
prev parent reply other threads:[~2020-02-17 16:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 15:56 Qian Cai
2020-02-14 16:59 ` Sean Christopherson
2020-02-14 17:08 ` Qian Cai
2020-02-14 17:40 ` Jim Mattson
2020-02-14 19:14 ` Qian Cai
2020-02-14 19:33 ` Paolo Bonzini
2020-02-14 19:54 ` Sean Christopherson
2020-02-17 14:47 ` Qian Cai
2020-02-17 16:32 ` Paolo Bonzini [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=030ced86-5ef0-0a2e-7c66-dbfb1416b8b5@redhat.com \
--to=pbonzini@redhat.com \
--cc=cai@lca.pw \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sean.j.christopherson@intel.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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
all inboxes | Powered by JetHome®