mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <demfloro@demfloro.ru>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: Borislav Petkov <bp@alien8.de>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] x86/mm: Flush more aggressively in lazy TLB mode
Date: Fri, 13 Oct 2017 09:07:52 +0000	[thread overview]
Message-ID: <20171013220838.1a85dd55@demfloro.ru> (raw)
In-Reply-To: <20171009170231.fkpraqokz6e4zeco@pd.tnic>

>I'm getting conflicts when trying to apply it ontop of rc4+tip/master but they 
>seem only contextual. Here's what applies:

This patch helped with random kernel freezes during I/O on AMD FX-9590 CPU

  parent reply	other threads:[~2017-10-13  9:15 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-09 16:50 Andy Lutomirski
2017-10-09 17:02 ` Borislav Petkov
2017-10-09 17:36   ` Borislav Petkov
2017-10-09 17:50     ` Andy Lutomirski
2017-10-09 18:08       ` Borislav Petkov
2017-10-09 18:31         ` Andy Lutomirski
2017-10-13  9:07   ` demfloro [this message]
2017-10-14 10:49   ` [tip:x86/urgent] " tip-bot for Andy Lutomirski
2017-10-14 12:34     ` [PATCH] x86/mm: Rip out the TLB benchmarking knob Borislav Petkov
2017-10-14 17:01       ` Andy Lutomirski
2017-10-14 16:34     ` [tip:x86/urgent] x86/mm: Flush more aggressively in lazy TLB mode Andy Lutomirski
2017-10-14 17:00       ` Andy Lutomirski
2017-10-16  2:39   ` [lkp-robot] [x86/mm] c4c3c3c2d0: will-it-scale.per_process_ops -61.0% regression kernel test robot
2017-10-16 10:15     ` Borislav Petkov
2017-10-17  1:06       ` Andy Lutomirski
2017-10-17  4:57         ` Markus Trippelsdorf
2017-10-17  8:00           ` Borislav Petkov
2017-10-17 22:06             ` Andy Lutomirski
2017-10-18 14:26               ` Borislav Petkov
2017-10-18  1:59             ` Ye Xiaolong
2017-10-18  8:11               ` Borislav Petkov
2017-10-17  6:04         ` Ye Xiaolong
2017-10-10  8:22 ` [RFC PATCH] x86/mm: Flush more aggressively in lazy TLB mode Markus Trippelsdorf

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=20171013220838.1a85dd55@demfloro.ru \
    --to=demfloro@demfloro.ru \
    --cc=bp@alien8.de \
    --cc=markus@trippelsdorf.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

all inboxes | Powered by JetHome®