From: Andi Kleen <ak@linux.intel.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH 3/8] L1TFv3 1
Date: Mon, 7 May 2018 11:21:40 -0700 [thread overview]
Message-ID: <20180507182140.GD4050@tassilo.jf.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1805071701060.1667@nanos.tec.linutronix.de>
> IOW, you know it's a mess and because you can't be bothered to clean it up,
> you add open coded crap to it, so others have more work to clean it up later.
It's not about being bothered, it's about keeping a clean and simple
and self contained and straight forward patchkit that only does one thing
and can be easily understood without diving into all kinds of unrelated stuff.
If I add a numa balancing dependency the cognitive load for every reviewer
and later applier will go up by at least an order of magnitude,
with very little benefit.
I know doing patchkits like this is out of fashion, but I'm old school
in that regard.
It's only two users that could be replaced with pte_protnone() anyways,
you're being overly dramatic.
The third user is custom and couldn't be expressed with pte_protnone().
-Andi
next prev parent reply other threads:[~2018-05-07 18:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 3:23 [MODERATED] [PATCH 0/8] L1TFv3 4 Andi Kleen
2018-05-04 3:23 ` [MODERATED] [PATCH 1/8] L1TFv3 8 Andi Kleen
2018-05-04 13:42 ` [MODERATED] " Michal Hocko
2018-05-04 14:07 ` Andi Kleen
2018-05-04 3:23 ` [MODERATED] [PATCH 2/8] L1TFv3 7 Andi Kleen
2018-05-07 11:45 ` [MODERATED] " Vlastimil Babka
2018-05-04 3:23 ` [MODERATED] [PATCH 3/8] L1TFv3 1 Andi Kleen
2018-05-04 3:55 ` [MODERATED] " Linus Torvalds
2018-05-04 13:42 ` Michal Hocko
2018-05-07 12:38 ` Vlastimil Babka
2018-05-07 13:41 ` Andi Kleen
2018-05-07 18:01 ` Thomas Gleixner
2018-05-07 18:21 ` Andi Kleen [this message]
2018-05-07 20:03 ` Thomas Gleixner
2018-05-04 3:23 ` [MODERATED] [PATCH 4/8] L1TFv3 6 Andi Kleen
2018-05-04 3:23 ` [MODERATED] [PATCH 5/8] L1TFv3 2 Andi Kleen
2018-05-04 3:23 ` [MODERATED] [PATCH 6/8] L1TFv3 0 Andi Kleen
2018-05-04 3:23 ` [MODERATED] [PATCH 7/8] L1TFv3 5 Andi Kleen
2018-05-04 13:43 ` [MODERATED] " Michal Hocko
2018-05-04 14:11 ` Andi Kleen
2018-05-04 14:21 ` Michal Hocko
2018-05-04 3:23 ` [MODERATED] [PATCH 8/8] L1TFv3 3 Andi Kleen
2018-05-04 14:19 ` [MODERATED] " Andi Kleen
2018-05-04 14:34 ` Michal Hocko
2018-05-04 15:53 ` Andi Kleen
2018-05-04 16:26 ` Michal Hocko
2018-05-04 22:15 ` Dave Hansen
2018-05-05 3:55 ` Andi Kleen
2018-05-04 3:54 ` [MODERATED] Re: [PATCH 0/8] L1TFv3 4 Andi Kleen
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=20180507182140.GD4050@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=speck@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 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.