From: "H. Peter Anvin" <hpa@zytor.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: "H. Peter Anvin" <hpa@linux.intel.com>,
mingo@kernel.org, linux-kernel@vger.kernel.org,
masami.hiramatsu.pt@hitachi.com, rostedt@goodmis.org,
tglx@linutronix.de, fengguang.wu@intel.com,
tip-bot for Jiri Kosina <tipbot@zytor.com>,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:perf/core] kprobes/x86: Call out into INT3 handler directly instead of using notifier
Date: Mon, 29 Jul 2013 02:23:19 -0700 [thread overview]
Message-ID: <51F63487.7040003@zytor.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1307291116560.18809@pobox.suse.cz>
On 07/29/2013 02:18 AM, Jiri Kosina wrote:
> On Mon, 29 Jul 2013, H. Peter Anvin wrote:
>
>>>> Please note that putting this patch in perf/core means x86/jumplabel is
>>>> completely nonfunctional by itself.
>>>
>>> I'd like to point out that this is still the case ... TIA,
>>
>> What is?
>
> 17f41571bb2c4a is only in perf/core, x86/jumplabel is missing it. I am not
> sure about the tip workflow, but as it is now, x86/jumplabel is buggy, so
> it should be either fixed (by pulling 17f41571bb2c4a from perf/core) or
> removed, or somehow marked as broken ... ?
>
> Not a big deal for me as long as perf/core is fine, but as you were
> mentioning it ...
>
Yes, we know. In effect, x86/jumplabel not really a working standalone
topic branch at the moment. It is probably not worth fixing it for this
kernel cycle, as the number of patches involved is relatively small, but
it is perhaps a bit unfortunate.
-hpa
prev parent reply other threads:[~2013-07-29 9:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-20 13:12 [x86] Kernel panic - not syncing: Fatal exception in interrupt Fengguang Wu
2013-07-21 0:23 ` H. Peter Anvin
2013-07-21 8:30 ` Jiri Kosina
2013-07-21 16:21 ` Fengguang Wu
2013-07-21 17:21 ` H. Peter Anvin
2013-07-22 11:18 ` Jiri Kosina
2013-07-22 1:07 ` Fengguang Wu
2013-07-22 11:14 ` [PATCH -tip/x86/jumplabel] x86: call out into int3 handler directly instead of using notifier Jiri Kosina
2013-07-22 11:24 ` Masami Hiramatsu
2013-07-22 20:53 ` H. Peter Anvin
2013-07-22 21:00 ` Jiri Kosina
2013-07-23 1:24 ` Masami Hiramatsu
2013-07-23 7:45 ` Ingo Molnar
2013-07-23 8:09 ` Jiri Kosina
2013-07-24 3:55 ` [tip:perf/core] kprobes/x86: Call out into INT3 " tip-bot for Jiri Kosina
2013-07-24 14:33 ` H. Peter Anvin
2013-07-29 9:06 ` Jiri Kosina
2013-07-29 9:14 ` H. Peter Anvin
2013-07-29 9:18 ` Jiri Kosina
2013-07-29 9:23 ` H. Peter Anvin [this message]
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=51F63487.7040003@zytor.com \
--to=hpa@zytor.com \
--cc=fengguang.wu@intel.com \
--cc=hpa@linux.intel.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tipbot@zytor.com \
/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.