From: Peter Zijlstra <peterz@infradead.org>
To: Ilia Mirkin <imirkin@alum.mit.edu>
Cc: Ingo Molnar <mingo@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Pekka Paalanen <ppaalanen@gmail.com>, Lyude <lyude@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
Karol Herbst <kherbst@redhat.com>,
Linus Torvalds <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:51:05 +0100 [thread overview]
Message-ID: <20171212145105.6rfbdbty6e5ajron@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CAKb7UvjsNE2Y6TWeBSoZ2dxqJndY-Sq6TYZhg9-jUjfw2A2zWQ@mail.gmail.com>
On Tue, Dec 12, 2017 at 09:47:05AM -0500, Ilia Mirkin wrote:
> > So this 'thing' has huge gaping SMP holes in.
>
> Sure does! Probably why the following happens when mmiotrace is enabled:
>
> void enable_mmiotrace(void)
> {
> mutex_lock(&mmiotrace_mutex);
> if (is_enabled())
> goto out;
>
> if (nommiotrace)
> pr_info("MMIO tracing disabled.\n");
> kmmio_init();
> enter_uniprocessor();
^^^^^
Ah! I completely missed that. OK, that makes it much less broken :-)
If I don't forget, I'll add some comments to this file to clarify that.
Thanks!
> spin_lock_irq(&trace_lock);
> atomic_inc(&mmiotrace_enabled);
> spin_unlock_irq(&trace_lock);
> pr_info("enabled.\n");
> out:
> mutex_unlock(&mmiotrace_mutex);
> }
next prev parent reply other threads:[~2017-12-12 14:51 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
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 [this message]
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=20171212145105.6rfbdbty6e5ajron@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=hpa@zytor.com \
--cc=imirkin@alum.mit.edu \
--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=mingo@kernel.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
all inboxes | Powered by JetHome®