From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Qian Cai <cai@lca.pw>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
rkrcmar@redhat.com, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, hpa@zytor.com, x86@kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kvm: add proper frame pointer logic for vmx
Date: Tue, 15 Jan 2019 09:48:45 -0800 [thread overview]
Message-ID: <20190115174845.GB21622@linux.intel.com> (raw)
In-Reply-To: <7d6ae0bc-b7c7-63ea-ae94-4437a29a31b1@lca.pw>
On Tue, Jan 15, 2019 at 11:43:20AM -0500, Qian Cai wrote:
>
>
> On 1/15/19 2:13 AM, Paolo Bonzini wrote:
> > Hmm, maybe like this:
> >
> > diff --git a/arch/x86/kvm/vmx/vmenter.S b/arch/x86/kvm/vmx/vmenter.S
> > index bcef2c7e9bc4..33122fa9d4bd 100644
> > --- a/arch/x86/kvm/vmx/vmenter.S
> > +++ b/arch/x86/kvm/vmx/vmenter.S
> > @@ -26,19 +26,17 @@ ENTRY(vmx_vmenter)
> > ret
> >
> > 2: vmlaunch
> > +3:
> > ret
> >
> > -3: cmpb $0, kvm_rebooting
> > - jne 4f
> > - call kvm_spurious_fault
> > -4: ret
> > -
> > .pushsection .fixup, "ax"
> > -5: jmp 3b
> > +4: cmpb $0, kvm_rebooting
> > + jne 3b
> > + jmp kvm_spurious_fault
> > .popsection
> >
> > - _ASM_EXTABLE(1b, 5b)
> > - _ASM_EXTABLE(2b, 5b)
> > + _ASM_EXTABLE(1b, 4b)
> > + _ASM_EXTABLE(2b, 4b)
> >
> > ENDPROC(vmx_vmenter)
>
> No, that will not work. The problem is in vmx.o where I just sent another patch
> for it.
>
> I can see there are five options to solve it.
>
> 1) always inline vmx_vcpu_run()
> 2) always noinline vmx_vcpu_run()
> 3) add -fdiable-ipa-fnsplit option to Makefile for vmx.o
> 4) let STACK_FRAME_NON_STANDARD support part.* syntax.
What is ".part." and where does it come from? Searching for information
is futile, the term is too generic.
> 5) trim-down vmx_vcpu_run() even more to not causing splitting by GCC.
>
> Option 1) and 2) seems give away the decision for user with
> CONFIG_CC_OPTIMIZE_FOR_(PERFORMANCE/SIZE).
>
> Option 3) prevents other functions there for splitting for optimization.
>
> Option 4) and 5) seems tricky to implement.
>
> I am not more leaning to 3) as only other fuction will miss splitting is
> vmx_segment_access_rights().
next prev parent reply other threads:[~2019-01-15 17:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 6:44 Qian Cai
2019-01-15 7:04 ` Qian Cai
2019-01-15 7:13 ` Paolo Bonzini
2019-01-15 16:34 ` Sean Christopherson
2019-01-15 16:54 ` Qian Cai
2019-01-15 16:43 ` Qian Cai
2019-01-15 17:31 ` Qian Cai
2019-01-15 17:48 ` Sean Christopherson [this message]
2019-01-15 17:49 ` Sean Christopherson
2019-01-15 18:29 ` Qian Cai
2019-01-15 19:06 ` Sean Christopherson
2019-01-15 19:08 ` Sean Christopherson
2019-01-15 22:38 ` Josh Poimboeuf
2019-01-16 0:54 ` Sean Christopherson
2019-01-16 14:56 ` Josh Poimboeuf
2019-01-16 16:35 ` Sean Christopherson
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=20190115174845.GB21622@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=bp@alien8.de \
--cc=cai@lca.pw \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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
Powered by JetHome