From: Christoffer Dall <christoffer.dall@linaro.org>
To: kvm-ia64@vger.kernel.org
Subject: Re: [PATCH 1/2] KVM: static inline empty kvm_arch functions
Date: Mon, 01 Sep 2014 09:21:49 +0000 [thread overview]
Message-ID: <20140901092149.GD19836@cbox> (raw)
On Thu, Aug 28, 2014 at 03:13:02PM +0200, Radim Krčmář wrote:
> Using static inline is going to save few bytes and cycles.
> For example on powerpc, the difference is 700 B after stripping.
> (5 kB before)
>
> This patch also deals with two overlooked empty functions:
> kvm_arch_flush_shadow was not removed from arch/mips/kvm/mips.c
> 2df72e9bc KVM: split kvm_arch_flush_shadow
> and kvm_arch_sched_in never made it into arch/ia64/kvm/kvm-ia64.c.
> e790d9ef6 KVM: add kvm_arch_sched_in
>
> Signed-off-by: Radim Krčmář <rkrcmar@redhat.com>
For the arm/arm64 part:
Acked-by: Christoffer Dall <christoffer.dall@linaro.org>
next reply other threads:[~2014-09-01 9:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 9:21 Christoffer Dall [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-08-28 13:13 [PATCH 1/2] KVM: static inline empty kvm_arch functions Radim Krčmář
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=20140901092149.GD19836@cbox \
--to=christoffer.dall@linaro.org \
--cc=kvm-ia64@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