From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: X86 ML <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Song Liu <songliubraving@fb.com>, Kairui Song <kasong@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>, Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH v3 2/4] objtool: Add support for C jump tables
Date: Wed, 26 Jun 2019 21:38:31 -0700 [thread overview]
Message-ID: <CAADnVQK4B6oaaYnVsUsZ7coL0yw1fJtapazcf=_hDKyzkrmGZw@mail.gmail.com> (raw)
In-Reply-To: <20190627035623.owkbrxa7dx7suv4a@treble>
On Wed, Jun 26, 2019 at 8:56 PM Josh Poimboeuf <jpoimboe@redhat.com> wrote:
>
> The last patch was based weird, this one's based on upstream. Will test
> tomorrow.
Great. Once it passes your tests I'll be happy to test it on my side.
next prev parent reply other threads:[~2019-06-27 4:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 0:33 [PATCH v3 0/4] x86: bpf unwinder fixes Josh Poimboeuf
2019-06-27 0:33 ` [PATCH v3 1/4] perf/x86: Always store regs->ip in perf_callchain_kernel() Josh Poimboeuf
2019-06-27 22:22 ` [tip:x86/urgent] " tip-bot for Song Liu
2019-06-27 0:33 ` [PATCH v3 2/4] objtool: Add support for C jump tables Josh Poimboeuf
2019-06-27 1:42 ` Alexei Starovoitov
2019-06-27 2:47 ` Josh Poimboeuf
2019-06-27 2:54 ` Alexei Starovoitov
2019-06-27 3:44 ` Josh Poimboeuf
2019-06-27 3:56 ` Josh Poimboeuf
2019-06-27 4:38 ` Alexei Starovoitov [this message]
2019-06-27 12:58 ` Steven Rostedt
2019-06-27 0:33 ` [PATCH v3 3/4] bpf: Fix ORC unwinding in non-JIT BPF code Josh Poimboeuf
2019-06-27 0:57 ` Alexei Starovoitov
2019-06-27 1:06 ` Josh Poimboeuf
2019-06-27 1:22 ` Alexei Starovoitov
2019-06-27 1:30 ` Josh Poimboeuf
2019-06-27 0:33 ` [PATCH v3 4/4] x86/unwind/orc: Fall back to using frame pointers for generated code Josh Poimboeuf
2019-06-27 22:22 ` [tip:x86/urgent] " tip-bot for Josh Poimboeuf
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='CAADnVQK4B6oaaYnVsUsZ7coL0yw1fJtapazcf=_hDKyzkrmGZw@mail.gmail.com' \
--to=alexei.starovoitov@gmail.com \
--cc=bp@alien8.de \
--cc=jpoimboe@redhat.com \
--cc=kasong@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=songliubraving@fb.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).