[llvmlinux] [PATCH v2 for-3.10] tracing: x86: Mark TRACING_SUPPORT as BROKEN

Sedat Dilek sedat.dilek at gmail.com
Fri Jul 26 11:45:52 UTC 2013

On Fri, Jul 26, 2013 at 1:38 PM, Jan-Simon Möller <dl9pf at gmx.de> wrote:
> Hi Sedat,
> On Friday 26 July 2013 13:27:29 Sedat Dilek wrote:
>> On Fri, Jul 26, 2013 at 1:21 PM, Sedat Dilek <sedat.dilek at gmail.com> wrote:
>> > On Fri, Jul 26, 2013 at 1:18 PM, Jan-Simon Möller <dl9pf at gmx.de> wrote:
>> >> Considering it as local workaround.
>> >
>> > So, you can build w/ tracing-support enabled?
>> > Can you do some real tracing?
>> > Can you provide some logs and kernel-configs, please?
>> > What about other arches supported by llvmlinux?
>> > I am really interested in that!
> Seems like you misinterpreted my reply. Let me clarify:
> I'm considering to add your patch to the series. But as it is a workaround and
> in no way material for upstream, we can just use it to prevent a broken config.

OK, yeah it's for llvmlinux not upstream.
Might be good to add a "llvmlinux-3.10" to my patch-subject next time.

As said in my previous emails, sth. like a KNOWN-ISSUES file would be great.

I have here some more logs with BROKEN kernel-configs.

As Linus Torvalds says... do things userfriendly. It's not the user to
care about working configs.
Known BROKEN configs have to be marked properly.

I would also suggest a TODO file, where such things can be placed.
The TODO file I had in mind as Behan answered me the idea of using a
"pre-built toolchain" was not new.
So, you do not forget about your ideas.

Added systemd's TODO as an EXAMPLE.

- Sedat -

[1] http://cgit.freedesktop.org/systemd/systemd/tree/TODO

> --
> JS

More information about the LLVMLinux mailing list