From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: KVM: Save two instructions in __guest_enter()
Date: Thu, 25 Aug 2016 15:31:22 +0200 [thread overview]
Message-ID: <20160825133122.GA8016@lvm> (raw)
In-Reply-To: <1470791736-13949-1-git-send-email-shankerd@codeaurora.org>
Hi Shanker,
On Tue, Aug 09, 2016 at 08:15:36PM -0500, Shanker Donthineni wrote:
> We are doing an unnecessary stack push/pop operation when restoring
> the guest registers x0-x18 in __guest_enter(). This patch saves the
> two instructions by using x18 as a base register. No need to store
> the vcpu context pointer in stack because it is redundant and not
> being used anywhere, the same information is available in tpidr_el2.
Does this have any measureable benefit?
Thanks,
-Christoffer
next prev parent reply other threads:[~2016-08-25 13:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 1:15 [PATCH] arm64: KVM: Save two instructions in __guest_enter() Shanker Donthineni
2016-08-25 13:31 ` Christoffer Dall [this message]
2016-08-29 15:22 ` Shanker Donthineni
2016-08-29 18:15 ` Christoffer Dall
2016-08-29 18:13 ` Christoffer Dall
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=20160825133122.GA8016@lvm \
--to=christoffer.dall@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).