All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Desaulniers <ndesaulniers@google.com>
To: Arnd Bergmann <arnd@kernel.org>
Cc: "Christian König" <christian.koenig@amd.com>,
	"Alex Deucher" <alexdeucher@gmail.com>,
	"Harry Wentland" <harry.wentland@amd.com>,
	"Leo Li" <sunpeng.li@amd.com>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	"David Airlie" <airlied@linux.ie>,
	"Daniel Vetter" <daniel@ffwll.ch>,
	"Nathan Chancellor" <natechancellor@gmail.com>,
	"Luben Tuikov" <luben.tuikov@amd.com>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Mauro Rossi" <issor.oruam@gmail.com>,
	"Randy Dunlap" <rdunlap@infradead.org>,
	"Roman Li" <Roman.Li@amd.com>,
	"amd-gfx list" <amd-gfx@lists.freedesktop.org>,
	LKML <linux-kernel@vger.kernel.org>,
	clang-built-linux <clang-built-linux@googlegroups.com>,
	"Maling list - DRI developers" <dri-devel@lists.freedesktop.org>,
	"Bhawanpreet Lakha" <Bhawanpreet.Lakha@amd.com>,
	"Daniel Kolesa" <daniel@octaforge.org>,
	"Timothy Pearson" <tpearson@raptorengineering.com>
Subject: Re: [PATCH] drm/amdgpu: make DRM_AMD_DC x86-only again
Date: Mon, 7 Dec 2020 14:28:42 -0800	[thread overview]
Message-ID: <CAKwvOd=+w6vJvvq9Pwnv1EHHzwCx=o_=PbSozXpqryN6P1yxVQ@mail.gmail.com> (raw)
In-Reply-To: <CAK8P3a0gjPWiRX0yg=i6Qxgyo02AtQVVsw+=w-OvF956Tn=jDw@mail.gmail.com>

On Mon, Dec 7, 2020 at 2:17 PM Arnd Bergmann <arnd@kernel.org> wrote:
>
> On Mon, Dec 7, 2020 at 11:08 PM 'Nick Desaulniers' via Clang Built
> Linux <clang-built-linux@googlegroups.com> wrote:
> >
> > On Mon, Dec 7, 2020 at 1:57 PM Arnd Bergmann <arnd@kernel.org> wrote:
>
> > >
> > > Right, looking at my latest randconfig logs, I see the same problem on x86
> > > builds with clang as well, though I'm not entirely sure which other
> > > configuration
> > > options are needed to trigger it.
> > >
> > > So my patch can be disregarded, but I agree this needs a better fix,
> > > either in clang or in the dcn driver.
> >
> > If you could give https://github.com/ClangBuiltLinux/frame-larger-than
> > a spin again, I would appreciate any feedback.
>
> I've already tried it, but the tool doesn't seem to like me, I never
> get the information out of it that I want. This time it failed because
> it could not parse the .o file correctly.

Can you send me a config to reproduce the .o file?
-- 
Thanks,
~Nick Desaulniers

WARNING: multiple messages have this Message-ID (diff)
From: Nick Desaulniers <ndesaulniers@google.com>
To: Arnd Bergmann <arnd@kernel.org>
Cc: "Timothy Pearson" <tpearson@raptorengineering.com>,
	"Arnd Bergmann" <arnd@arndb.de>,
	clang-built-linux <clang-built-linux@googlegroups.com>,
	"Leo Li" <sunpeng.li@amd.com>,
	"Bhawanpreet Lakha" <Bhawanpreet.Lakha@amd.com>,
	"David Airlie" <airlied@linux.ie>,
	"Randy Dunlap" <rdunlap@infradead.org>,
	"Roman Li" <Roman.Li@amd.com>,
	"amd-gfx list" <amd-gfx@lists.freedesktop.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	"Mauro Rossi" <issor.oruam@gmail.com>,
	"Luben Tuikov" <luben.tuikov@amd.com>,
	"Maling list - DRI developers" <dri-devel@lists.freedesktop.org>,
	"Daniel Kolesa" <daniel@octaforge.org>,
	"Nathan Chancellor" <natechancellor@gmail.com>,
	"Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH] drm/amdgpu: make DRM_AMD_DC x86-only again
Date: Mon, 7 Dec 2020 14:28:42 -0800	[thread overview]
Message-ID: <CAKwvOd=+w6vJvvq9Pwnv1EHHzwCx=o_=PbSozXpqryN6P1yxVQ@mail.gmail.com> (raw)
In-Reply-To: <CAK8P3a0gjPWiRX0yg=i6Qxgyo02AtQVVsw+=w-OvF956Tn=jDw@mail.gmail.com>

On Mon, Dec 7, 2020 at 2:17 PM Arnd Bergmann <arnd@kernel.org> wrote:
>
> On Mon, Dec 7, 2020 at 11:08 PM 'Nick Desaulniers' via Clang Built
> Linux <clang-built-linux@googlegroups.com> wrote:
> >
> > On Mon, Dec 7, 2020 at 1:57 PM Arnd Bergmann <arnd@kernel.org> wrote:
>
> > >
> > > Right, looking at my latest randconfig logs, I see the same problem on x86
> > > builds with clang as well, though I'm not entirely sure which other
> > > configuration
> > > options are needed to trigger it.
> > >
> > > So my patch can be disregarded, but I agree this needs a better fix,
> > > either in clang or in the dcn driver.
> >
> > If you could give https://github.com/ClangBuiltLinux/frame-larger-than
> > a spin again, I would appreciate any feedback.
>
> I've already tried it, but the tool doesn't seem to like me, I never
> get the information out of it that I want. This time it failed because
> it could not parse the .o file correctly.

Can you send me a config to reproduce the .o file?
-- 
Thanks,
~Nick Desaulniers
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: Nick Desaulniers <ndesaulniers@google.com>
To: Arnd Bergmann <arnd@kernel.org>
Cc: "Timothy Pearson" <tpearson@raptorengineering.com>,
	"Arnd Bergmann" <arnd@arndb.de>,
	clang-built-linux <clang-built-linux@googlegroups.com>,
	"Leo Li" <sunpeng.li@amd.com>,
	"Bhawanpreet Lakha" <Bhawanpreet.Lakha@amd.com>,
	"David Airlie" <airlied@linux.ie>,
	"Randy Dunlap" <rdunlap@infradead.org>,
	"Roman Li" <Roman.Li@amd.com>,
	"amd-gfx list" <amd-gfx@lists.freedesktop.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	"Mauro Rossi" <issor.oruam@gmail.com>,
	"Luben Tuikov" <luben.tuikov@amd.com>,
	"Maling list - DRI developers" <dri-devel@lists.freedesktop.org>,
	"Daniel Vetter" <daniel@ffwll.ch>,
	"Daniel Kolesa" <daniel@octaforge.org>,
	"Alex Deucher" <alexdeucher@gmail.com>,
	"Nathan Chancellor" <natechancellor@gmail.com>,
	"Harry Wentland" <harry.wentland@amd.com>,
	"Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH] drm/amdgpu: make DRM_AMD_DC x86-only again
Date: Mon, 7 Dec 2020 14:28:42 -0800	[thread overview]
Message-ID: <CAKwvOd=+w6vJvvq9Pwnv1EHHzwCx=o_=PbSozXpqryN6P1yxVQ@mail.gmail.com> (raw)
In-Reply-To: <CAK8P3a0gjPWiRX0yg=i6Qxgyo02AtQVVsw+=w-OvF956Tn=jDw@mail.gmail.com>

On Mon, Dec 7, 2020 at 2:17 PM Arnd Bergmann <arnd@kernel.org> wrote:
>
> On Mon, Dec 7, 2020 at 11:08 PM 'Nick Desaulniers' via Clang Built
> Linux <clang-built-linux@googlegroups.com> wrote:
> >
> > On Mon, Dec 7, 2020 at 1:57 PM Arnd Bergmann <arnd@kernel.org> wrote:
>
> > >
> > > Right, looking at my latest randconfig logs, I see the same problem on x86
> > > builds with clang as well, though I'm not entirely sure which other
> > > configuration
> > > options are needed to trigger it.
> > >
> > > So my patch can be disregarded, but I agree this needs a better fix,
> > > either in clang or in the dcn driver.
> >
> > If you could give https://github.com/ClangBuiltLinux/frame-larger-than
> > a spin again, I would appreciate any feedback.
>
> I've already tried it, but the tool doesn't seem to like me, I never
> get the information out of it that I want. This time it failed because
> it could not parse the .o file correctly.

Can you send me a config to reproduce the .o file?
-- 
Thanks,
~Nick Desaulniers
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

  reply	other threads:[~2020-12-07 22:29 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-04  8:13 [PATCH] drm/amdgpu: make DRM_AMD_DC x86-only again Arnd Bergmann
2020-12-04  8:13 ` Arnd Bergmann
2020-12-04  8:13 ` Arnd Bergmann
2020-12-07 20:47 ` Alex Deucher
2020-12-07 20:47   ` Alex Deucher
2020-12-07 20:47   ` Alex Deucher
2020-12-07 20:50   ` Christian König
2020-12-07 20:50     ` Christian König
2020-12-07 20:50     ` Christian König
2020-12-07 21:57     ` Arnd Bergmann
2020-12-07 21:57       ` Arnd Bergmann
2020-12-07 21:57       ` Arnd Bergmann
2020-12-07 22:07       ` Nick Desaulniers
2020-12-07 22:07         ` Nick Desaulniers
2020-12-07 22:07         ` Nick Desaulniers
2020-12-07 22:16         ` Arnd Bergmann
2020-12-07 22:16           ` Arnd Bergmann
2020-12-07 22:16           ` Arnd Bergmann
2020-12-07 22:28           ` Nick Desaulniers [this message]
2020-12-07 22:28             ` Nick Desaulniers
2020-12-07 22:28             ` Nick Desaulniers
2020-12-08 14:26             ` Arnd Bergmann
2020-12-08 14:26               ` Arnd Bergmann
2020-12-08 14:26               ` Arnd Bergmann
2020-12-08 18:21               ` Nick Desaulniers
2020-12-08 18:21                 ` Nick Desaulniers
2020-12-08 18:21                 ` Nick Desaulniers
2020-12-08 22:18                 ` Arnd Bergmann
2020-12-08 22:18                   ` Arnd Bergmann
2020-12-08 22:18                   ` Arnd Bergmann
2020-12-10 22:52                   ` Nick Desaulniers
2020-12-10 22:52                     ` Nick Desaulniers
2020-12-10 22:52                     ` Nick Desaulniers

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='CAKwvOd=+w6vJvvq9Pwnv1EHHzwCx=o_=PbSozXpqryN6P1yxVQ@mail.gmail.com' \
    --to=ndesaulniers@google.com \
    --cc=Bhawanpreet.Lakha@amd.com \
    --cc=Roman.Li@amd.com \
    --cc=airlied@linux.ie \
    --cc=alexander.deucher@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=christian.koenig@amd.com \
    --cc=clang-built-linux@googlegroups.com \
    --cc=daniel@ffwll.ch \
    --cc=daniel@octaforge.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=harry.wentland@amd.com \
    --cc=issor.oruam@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luben.tuikov@amd.com \
    --cc=natechancellor@gmail.com \
    --cc=rdunlap@infradead.org \
    --cc=sunpeng.li@amd.com \
    --cc=tpearson@raptorengineering.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.