From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@suse.de>
Cc: Andy Lutomirski <luto@kernel.org>, X86 ML <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 1/2] x86/mm: Reinitialize TLB state on hotplug and resume
Date: Thu, 7 Sep 2017 11:59:32 +0200 [thread overview]
Message-ID: <20170907095931.gnekqsgeelutofb4@gmail.com> (raw)
In-Reply-To: <20170907095437.fs53v7w4smhsbd6m@pd.tnic>
* Borislav Petkov <bp@suse.de> wrote:
> > + */
> > +void initialize_tlbstate_and_flush(void)
>
> I think we should prefix all those visible, TLB-handling functions with
> "tlb_". So you'd have tlb_init_state_and_flush().
Agreed absolutely, but note that this affects more functions as well - for example
enter_lazy_tlb() should probably be tlb_lazy_enter() - or at least
lazy_tlb_enter() or such?
Thanks,
Ingo
next prev parent reply other threads:[~2017-09-07 9:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 2:54 [PATCH 0/2] Fix resume failure due to PCID Andy Lutomirski
2017-09-07 2:54 ` [PATCH 1/2] x86/mm: Reinitialize TLB state on hotplug and resume Andy Lutomirski
2017-09-07 7:01 ` [PATCH] mm/debug: Change BUG_ON() crashes to survivable WARN_ON() warnings Ingo Molnar
2017-09-07 20:50 ` Linus Torvalds
2017-09-07 7:31 ` [PATCH 1/2] x86/mm: Reinitialize TLB state on hotplug and resume Jiri Kosina
2017-09-07 7:48 ` Ingo Molnar
2017-09-07 19:55 ` Jiri Kosina
2017-09-08 1:23 ` Andy Lutomirski
2017-09-07 9:54 ` Borislav Petkov
2017-09-07 9:59 ` Ingo Molnar [this message]
2017-09-07 10:10 ` Borislav Petkov
2017-09-07 2:54 ` [PATCH 2/2] x86/mm: Document how CR4.PCIDE restore works Andy Lutomirski
2017-09-07 3:25 ` [PATCH 0/2] Fix resume failure due to PCID Linus Torvalds
2017-09-07 4:15 ` Andy Lutomirski
2017-09-15 6:59 ` x60: warnings on boot and resume, arch/x86/mm/tlb.c:257 initialize_ ... was " Pavel Machek
2017-09-15 8:39 ` Ingo Molnar
2017-09-15 9:16 ` Pavel Machek
2017-09-15 9:35 ` Ingo Molnar
2017-09-15 10:22 ` [4.14-rc0 regression] " Pavel Machek
2017-09-15 18:47 ` Linus Torvalds
2017-09-15 19:29 ` Andy Lutomirski
2017-09-15 21:06 ` Andy Lutomirski
2017-09-07 8:59 ` Borislav Petkov
2017-09-15 11:01 ` Pavel Machek
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=20170907095931.gnekqsgeelutofb4@gmail.com \
--to=mingo@kernel.org \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).