From: Ingo Molnar <mingo@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Jürgen Groß" <jgross@suse.com>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
paulmck@kernel.org, mhocko@suse.com,
"Jonathan Corbet" <corbet@lwn.net>
Subject: Re: [PATCH v2 3/3] kernel/smp: add more data to CSD lock debugging
Date: Tue, 2 Mar 2021 08:05:59 +0100 [thread overview]
Message-ID: <20210302070559.GB2809110@gmail.com> (raw)
In-Reply-To: <YD1SJNDeGcNOO00s@hirez.programming.kicks-ass.net>
* Peter Zijlstra <peterz@infradead.org> wrote:
> On Mon, Mar 01, 2021 at 08:16:12PM +0100, Jürgen Groß wrote:
> > > https://lkml.kernel.org/r/20210220231712.2475218-2-namit@vmware.com
> >
> > They are already in tip locking/core (Ingo applied them).
>
> I'm very tempted to undo that :-(
Sorry about that - I'm sorting out the conflicts with the concurrent TLB
flush series.
Thanks,
Ingo
next prev parent reply other threads:[~2021-03-02 8:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 10:13 [PATCH v2 0/3] kernel/smp.c: add more CSD lock debugging Juergen Gross
2021-03-01 10:13 ` [PATCH v2 1/3] kernel/smp: add boot parameter for controlling " Juergen Gross
2021-03-01 14:09 ` [tip: locking/core] locking/csd_lock: Add " tip-bot2 for Juergen Gross
2021-03-06 11:54 ` tip-bot2 for Juergen Gross
2021-03-01 10:13 ` [PATCH v2 2/3] kernel/smp: prepare more " Juergen Gross
2021-03-01 14:09 ` [tip: locking/core] locking/csd_lock: Prepare " tip-bot2 for Juergen Gross
2021-03-06 11:54 ` tip-bot2 for Juergen Gross
2021-03-01 10:13 ` [PATCH v2 3/3] kernel/smp: add more data to " Juergen Gross
2021-03-01 14:09 ` [tip: locking/core] locking/csd_lock: Add " tip-bot2 for Juergen Gross
2021-03-01 17:07 ` [PATCH v2 3/3] kernel/smp: add " Peter Zijlstra
2021-03-01 19:16 ` Jürgen Groß
2021-03-01 20:44 ` Peter Zijlstra
2021-03-02 7:05 ` Ingo Molnar [this message]
2021-03-02 7:14 ` Ingo Molnar
2021-03-02 5:57 ` Jürgen Groß
2021-03-06 11:54 ` [tip: locking/core] locking/csd_lock: Add " tip-bot2 for Juergen Gross
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=20210302070559.GB2809110@gmail.com \
--to=mingo@kernel.org \
--cc=corbet@lwn.net \
--cc=jgross@suse.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.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