From: Ingo Molnar <mingo@kernel.org>
To: Yinghai Lu <yinghai@kernel.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Denys Vlasenko <dvlasenk@redhat.com>,
Wu Fengguang <fengguang.wu@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Borislav Petkov <bp@suse.de>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andy Lutomirski <luto@kernel.org>,
Brian Gerst <brgerst@gmail.com>,
"linux-tip-commits@vger.kernel.org"
<linux-tip-commits@vger.kernel.org>
Subject: Re: [tip:x86/asm] x86/asm: Optimize clear_page()
Date: Tue, 7 Mar 2017 08:30:12 +0100 [thread overview]
Message-ID: <20170307073012.GA15693@gmail.com> (raw)
In-Reply-To: <CAE9FiQU1NozwtPj9YFQjrmJO0CDw2XSqN3HLN4rn2iThFiO7dw@mail.gmail.com>
* Yinghai Lu <yinghai@kernel.org> wrote:
> On Wed, Mar 1, 2017 at 1:47 AM, tip-bot for Borislav Petkov
> <tipbot@zytor.com> wrote:
> > Commit-ID: 49ca7bb328c630dd43be626534b49e19513296fd
> > Gitweb: http://git.kernel.org/tip/49ca7bb328c630dd43be626534b49e19513296fd
> > Author: Borislav Petkov <bp@suse.de>
> > AuthorDate: Thu, 9 Feb 2017 01:34:49 +0100
> > Committer: Ingo Molnar <mingo@kernel.org>
> > CommitDate: Wed, 1 Mar 2017 10:18:32 +0100
> >
> > x86/asm: Optimize clear_page()
> >
> > Currently, we CALL clear_page() which then JMPs to the proper function
> > chosen by the alternatives.
> >
> > What we should do instead is CALL the proper function directly. (This
> > was something Ingo suggested a while ago). So let's do that.
>
> looks like this one broke the kexec.
> after revert it back, kexec work again.
Ok, this should be fixed in the new version I just pushed out:
f25d38475519 x86/asm: Optimize clear_page()
Please let me know if it doesn't.
Thanks,
Ingo
next prev parent reply other threads:[~2017-03-07 15:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 19:51 [PATCH] x86: Optimize clear_page() Borislav Petkov
2017-02-15 11:19 ` [PATCH -v1.1] " Borislav Petkov
2017-02-19 13:41 ` Borislav Petkov
2017-03-01 9:47 ` [tip:x86/asm] x86/asm: " tip-bot for Borislav Petkov
2017-03-07 5:11 ` Yinghai Lu
2017-03-07 7:30 ` Ingo Molnar [this message]
2017-03-07 18:57 ` Yinghai Lu
2017-03-08 10:47 ` Ingo Molnar
2017-03-02 1:09 ` [lkp-robot] [x86] ed3ce2a917: BUG:unable_to_handle_kernel kernel test robot
2017-03-02 1:09 ` kernel test robot
2017-03-02 18:19 ` Borislav Petkov
2017-03-02 18:19 ` Borislav Petkov
2017-03-09 2:13 ` Ye Xiaolong
2017-03-09 2:13 ` Ye Xiaolong
2017-03-09 2:30 ` Fengguang Wu
2017-03-09 2:30 ` Fengguang Wu
2017-03-09 8:17 ` Borislav Petkov
2017-03-09 8:17 ` Borislav Petkov
2017-03-09 8:14 ` Borislav Petkov
2017-03-09 8:14 ` Borislav Petkov
2017-03-10 2:33 ` Ye Xiaolong
2017-03-10 2:33 ` Ye Xiaolong
2017-03-10 8:30 ` Borislav Petkov
2017-03-10 8:30 ` Borislav Petkov
2017-03-07 8:34 ` [tip:x86/asm] x86/asm: Optimize clear_page() tip-bot for Borislav Petkov
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=20170307073012.GA15693@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=brgerst@gmail.com \
--cc=dvlasenk@redhat.com \
--cc=fengguang.wu@intel.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=yinghai@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.