From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: hpa@zytor.com
Cc: mingo@kernel.org, linux-kernel@vger.kernel.org,
konrad.wilk@oracle.com, boris.ostrovsky@oracle.com,
jwboyer@redhat.com, tglx@linutronix.de, bp@suse.de
Subject: Re: [tip:x86/urgent] x86, mm: Patch out arch_flush_lazy_mmu_mode() when running on bare metal
Date: Thu, 11 Apr 2013 11:17:12 -0400 [thread overview]
Message-ID: <5166D3F8.2050901@oracle.com> (raw)
In-Reply-To: <tip-511ba86e1d386f671084b5d0e6f110bb30b8eeb2@git.kernel.org>
On 04/10/2013 08:30 PM, tip-bot for Boris Ostrovsky wrote:
> Commit-ID: 511ba86e1d386f671084b5d0e6f110bb30b8eeb2
> Gitweb: http://git.kernel.org/tip/511ba86e1d386f671084b5d0e6f110bb30b8eeb2
> Author: Boris Ostrovsky <boris.ostrovsky@oracle.com>
> AuthorDate: Sat, 23 Mar 2013 09:36:36 -0400
> Committer: H. Peter Anvin <hpa@linux.intel.com>
> CommitDate: Wed, 10 Apr 2013 11:25:10 -0700
>
> x86, mm: Patch out arch_flush_lazy_mmu_mode() when running on bare metal
>
> Invoking arch_flush_lazy_mmu_mode() results in calls to
> preempt_enable()/disable() which may have performance impact.
>
> Since lazy MMU is not used on bare metal we can patch away
> arch_flush_lazy_mmu_mode() so that it is never called in such
> environment.
>
> [ hpa: the previous patch "Fix vmalloc_fault oops during lazy MMU
> updates" may cause a minor performance regression on
> bare metal. This patch resolves that performance regression. It is
> somewhat unclear to me if this is a good -stable candidate. ]
I think this
https://lkml.org/lkml/2013/2/26/420
was also part of lazy mmu set of patches but is missing in the latest
batch of
commits.
-boris
next prev parent reply other threads:[~2013-04-11 15:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 13:53 [PATCH] mm/x86: Patch out arch_flush_lazy_mmu_mode() when running on bare metal Boris Ostrovsky
2013-03-21 0:08 ` Josh Boyer
2013-03-22 20:09 ` Konrad Rzeszutek Wilk
2013-03-22 20:25 ` H. Peter Anvin
2013-03-23 13:36 ` [PATCH 1/2] x86: mm: Fix vmalloc_fault oops during lazy MMU updates Konrad Rzeszutek Wilk
2013-03-23 13:36 ` [PATCH 2/2] mm/x86: Patch out arch_flush_lazy_mmu_mode() when running on bare metal Konrad Rzeszutek Wilk
2013-04-03 13:26 ` Boris Ostrovsky
2013-04-11 0:30 ` [tip:x86/urgent] x86, mm: " tip-bot for Boris Ostrovsky
2013-04-11 15:17 ` Boris Ostrovsky [this message]
2013-04-11 0:29 ` [tip:x86/urgent] x86, mm, paravirt: Fix vmalloc_fault oops during lazy MMU updates tip-bot for Samu Kallio
-- strict thread matches above, loose matches on Subject: below --
2013-04-11 15:42 [tip:x86/urgent] x86, mm: Patch out arch_flush_lazy_mmu_mode() when running on bare metal Konrad Rzeszutek Wilk
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=5166D3F8.2050901@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=jwboyer@redhat.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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