From: Ingo Molnar <mingo@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, ppaalanen@gmail.com,
lyude@redhat.com, rostedt@goodmis.org, tglx@linutronix.de,
kherbst@redhat.com, torvalds@linux-foundation.org, hpa@zytor.com,
linux-tip-commits@vger.kernel.org,
Karol Herbst <karolherbst@gmail.com>
Subject: Re: [tip:x86/urgent] x86/mm/kmmio: Fix mmiotrace for page unaligned addresses
Date: Tue, 12 Dec 2017 15:04:18 +0100 [thread overview]
Message-ID: <20171212140418.56xld2lxja5rywp7@gmail.com> (raw)
In-Reply-To: <20171212134952.2hok6754245qshv3@hirez.programming.kicks-ass.net>
* Peter Zijlstra <peterz@infradead.org> wrote:
> On Tue, Dec 12, 2017 at 02:55:30AM -0800, tip-bot for Karol Herbst wrote:
> > Commit-ID: 6d60ce384d1d5ca32b595244db4077a419acc687
> > Gitweb: https://git.kernel.org/tip/6d60ce384d1d5ca32b595244db4077a419acc687
> > Author: Karol Herbst <kherbst@redhat.com>
> > AuthorDate: Mon, 27 Nov 2017 08:51:39 +0100
> > Committer: Ingo Molnar <mingo@kernel.org>
> > CommitDate: Mon, 11 Dec 2017 15:35:18 +0100
> >
> > x86/mm/kmmio: Fix mmiotrace for page unaligned addresses
>
> OK, let me hijack this thread since apparently people use and care about
> mmiotrace.
>
> I was recently auditing the x86 tlb flushing and ran across this
> 'thing'. Can someone please explain to me how this is supposed to work
> and how its not completely broken?
(I have Cc:-ed other gents as well.)
Thanks,
Ingo
next prev parent reply other threads:[~2017-12-12 14:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 7:51 [PATCH] " Karol Herbst
2017-12-12 10:55 ` [tip:x86/urgent] " tip-bot for Karol Herbst
2017-12-12 13:49 ` Peter Zijlstra
2017-12-12 14:04 ` Ingo Molnar [this message]
2017-12-12 14:21 ` Ilia Mirkin
2017-12-12 14:43 ` Peter Zijlstra
2017-12-12 14:47 ` Ilia Mirkin
2017-12-12 14:51 ` Peter Zijlstra
2017-12-13 16:31 ` Steven Rostedt
2017-12-12 14:32 ` Karol Herbst
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=20171212140418.56xld2lxja5rywp7@gmail.com \
--to=mingo@kernel.org \
--cc=hpa@zytor.com \
--cc=karolherbst@gmail.com \
--cc=kherbst@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=peterz@infradead.org \
--cc=ppaalanen@gmail.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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
Powered by JetHome