From: Nadav Amit <namit@vmware.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Song Liu <songliubraving@fb.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>,
"kernel-team@fb.com" <kernel-team@fb.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Dave Hansen <dave.hansen@intel.com>,
Andy Lutomirski <luto@amacapital.net>,
Daniel Bristot de Oliveira <bristot@redhat.com>
Subject: Re: [PATCH] x86/mm: Do not split_large_page() for set_kernel_text_rw()
Date: Mon, 26 Aug 2019 16:09:55 +0000 [thread overview]
Message-ID: <36BC6E27-A6EB-4B25-82C0-311AA0652179@vmware.com> (raw)
In-Reply-To: <20190826115651.43c9bde3@gandalf.local.home>
> On Aug 26, 2019, at 8:56 AM, Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Mon, 26 Aug 2019 15:41:24 +0000
> Nadav Amit <namit@vmware.com> wrote:
>
>>> Anyway, I believe Nadav has some patches that converts ftrace to use
>>> the shadow page modification trick somewhere.
>>
>> For the record - here is my previous patch:
>> https://lkml.org/lkml/2018/12/5/211
>
> FYI, when referencing older patches, please use lkml.kernel.org or
> lore.kernel.org, lkml.org is slow and obsolete.
>
> ie. http://lkml.kernel.org/r/20181205013408.47725-9-namit@vmware.com
Will do so next time.
prev parent reply other threads:[~2019-08-26 16:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 5:23 [PATCH] x86/mm: Do not split_large_page() for set_kernel_text_rw() Song Liu
2019-08-23 9:36 ` Peter Zijlstra
2019-08-26 4:40 ` Song Liu
2019-08-26 9:23 ` Peter Zijlstra
2019-08-26 15:08 ` Song Liu
2019-08-26 20:50 ` Song Liu
2019-08-26 11:33 ` Steven Rostedt
2019-08-26 12:44 ` Peter Zijlstra
2019-08-26 15:41 ` Nadav Amit
2019-08-26 15:56 ` Peter Zijlstra
2019-08-26 15:56 ` Steven Rostedt
2019-08-26 16:09 ` Nadav Amit [this message]
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=36BC6E27-A6EB-4B25-82C0-311AA0652179@vmware.com \
--to=namit@vmware.com \
--cc=bristot@redhat.com \
--cc=dave.hansen@intel.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@amacapital.net \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=songliubraving@fb.com \
--cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).