From: Philip Li <philip.li@intel.com>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: kbuild-all@lists.01.org, intel-gfx@lists.freedesktop.org,
clang-built-linux <clang-built-linux@googlegroups.com>
Subject: Re: [Intel-gfx] [PATCH 02/23] perf/core: Only copy-to-user after completely unlocking all locks.
Date: Thu, 2 Apr 2020 07:04:43 +0800 [thread overview]
Message-ID: <20200401230443.GA3836@intel.com> (raw)
In-Reply-To: <CAKwvOdniUVifJ9b1y9bhHPkdGkLasf=mkx7XwAK_ZTEk2Q+BKg@mail.gmail.com>
On Wed, Apr 01, 2020 at 11:55:28AM -0700, Nick Desaulniers wrote:
> On Tue, Mar 31, 2020 at 11:50 PM kbuild test robot <lkp@intel.com> wrote:
> >
> > Hi Maarten,
> >
> > I love your patch! Perhaps something to improve:
> >
> > [auto build test WARNING on drm-tip/drm-tip]
> > [also build test WARNING on next-20200331]
> > [cannot apply to drm-intel/for-linux-next tip/perf/core v5.6]
> > [if your patch is applied to the wrong git tree, please drop us a note to help
> > improve the system. BTW, we also suggest to use '--base' option to specify the
> > base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
> >
> > url: https://github.com/0day-ci/linux/commits/Maarten-Lankhorst/Revert-drm-i915-gem-Drop-relocation-slowpath/20200401-005710
> > base: git://anongit.freedesktop.org/drm/drm-tip drm-tip
> > config: x86_64-randconfig-d003-20200331 (attached as .config)
> > compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 5227fa0c72ce55927cf4849160acb00442489937)
> > reproduce:
> > wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> > chmod +x ~/bin/make.cross
> > # save the attached .config to linux build tree
> > COMPILER=clang make.cross ARCH=x86_64
> >
> > If you fix the issue, kindly add following tag
> > Reported-by: kbuild test robot <lkp@intel.com>
> >
> > All warnings (new ones prefixed by >>):
> >
> > >> kernel/events/core.o: warning: objtool: perf_read()+0x306: stack state mismatch: reg1[3]=-2-56 reg2[3]=-1+0
>
> Apologies Maarten, this objtool warning looks like maybe a compiler
> bug for us to fix.
>
> Philip, I tried to reproduce by cloning
> git://anongit.freedesktop.org/drm/drm-tip, but I don't understand the
> URL in the report. Were Maarten's patches on top of drm-tip? Is
Hi Nick, this is report for patch we receive from the mailing list, so the patch series
is applied on "git://anongit.freedesktop.org/drm/drm-tip drm-tip", and form a branch
at "https://github.com/0day-ci/linux/commits/Maarten-Lankhorst/Revert-drm-i915-gem-Drop-relocation-slowpath/20200401-005710".
The url is the real code to be checked out that can be used to reproduce.
Thanks
> there a tree you found them from (rather than me fetching the 0day
> branch on github)? (Or maybe this is what a report looks like for a
> series posted to the list?) Apologies for the naivete, but I plan to
> triage as many of these reports on the Clang side as I can in my free
> time, so I want to make sure I understand precisely what failure is
> occurring where and how.
> --
> Thanks,
> ~Nick Desaulniers
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Philip Li <philip.li@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [Intel-gfx] [PATCH 02/23] perf/core: Only copy-to-user after completely unlocking all locks.
Date: Thu, 02 Apr 2020 07:04:43 +0800 [thread overview]
Message-ID: <20200401230443.GA3836@intel.com> (raw)
In-Reply-To: <CAKwvOdniUVifJ9b1y9bhHPkdGkLasf=mkx7XwAK_ZTEk2Q+BKg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2690 bytes --]
On Wed, Apr 01, 2020 at 11:55:28AM -0700, Nick Desaulniers wrote:
> On Tue, Mar 31, 2020 at 11:50 PM kbuild test robot <lkp@intel.com> wrote:
> >
> > Hi Maarten,
> >
> > I love your patch! Perhaps something to improve:
> >
> > [auto build test WARNING on drm-tip/drm-tip]
> > [also build test WARNING on next-20200331]
> > [cannot apply to drm-intel/for-linux-next tip/perf/core v5.6]
> > [if your patch is applied to the wrong git tree, please drop us a note to help
> > improve the system. BTW, we also suggest to use '--base' option to specify the
> > base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
> >
> > url: https://github.com/0day-ci/linux/commits/Maarten-Lankhorst/Revert-drm-i915-gem-Drop-relocation-slowpath/20200401-005710
> > base: git://anongit.freedesktop.org/drm/drm-tip drm-tip
> > config: x86_64-randconfig-d003-20200331 (attached as .config)
> > compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 5227fa0c72ce55927cf4849160acb00442489937)
> > reproduce:
> > wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> > chmod +x ~/bin/make.cross
> > # save the attached .config to linux build tree
> > COMPILER=clang make.cross ARCH=x86_64
> >
> > If you fix the issue, kindly add following tag
> > Reported-by: kbuild test robot <lkp@intel.com>
> >
> > All warnings (new ones prefixed by >>):
> >
> > >> kernel/events/core.o: warning: objtool: perf_read()+0x306: stack state mismatch: reg1[3]=-2-56 reg2[3]=-1+0
>
> Apologies Maarten, this objtool warning looks like maybe a compiler
> bug for us to fix.
>
> Philip, I tried to reproduce by cloning
> git://anongit.freedesktop.org/drm/drm-tip, but I don't understand the
> URL in the report. Were Maarten's patches on top of drm-tip? Is
Hi Nick, this is report for patch we receive from the mailing list, so the patch series
is applied on "git://anongit.freedesktop.org/drm/drm-tip drm-tip", and form a branch
at "https://github.com/0day-ci/linux/commits/Maarten-Lankhorst/Revert-drm-i915-gem-Drop-relocation-slowpath/20200401-005710".
The url is the real code to be checked out that can be used to reproduce.
Thanks
> there a tree you found them from (rather than me fetching the 0day
> branch on github)? (Or maybe this is what a report looks like for a
> series posted to the list?) Apologies for the naivete, but I plan to
> triage as many of these reports on the Clang side as I can in my free
> time, so I want to make sure I understand precisely what failure is
> occurring where and how.
> --
> Thanks,
> ~Nick Desaulniers
next prev parent reply other threads:[~2020-04-01 23:05 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 10:41 [Intel-gfx] [PATCH 01/23] Revert "drm/i915/gem: Drop relocation slowpath" Maarten Lankhorst
2020-03-31 10:41 ` [Intel-gfx] [PATCH 02/23] perf/core: Only copy-to-user after completely unlocking all locks Maarten Lankhorst
2020-04-01 6:50 ` kbuild test robot
2020-04-01 6:50 ` kbuild test robot
2020-04-01 18:55 ` Nick Desaulniers
2020-04-01 18:55 ` Nick Desaulniers
2020-04-01 23:04 ` Philip Li [this message]
2020-04-01 23:04 ` Philip Li
2020-03-31 10:41 ` [Intel-gfx] [PATCH 03/23] drm/i915: Add an implementation for i915_gem_ww_ctx locking, v2 Maarten Lankhorst
2020-03-31 10:41 ` [Intel-gfx] [PATCH 04/23] drm/i915: Remove locking from i915_gem_object_prepare_read/write Maarten Lankhorst
2020-03-31 10:41 ` [Intel-gfx] [PATCH 05/23] drm/i915: Parse command buffer earlier in eb_relocate(slow) Maarten Lankhorst
2020-03-31 10:41 ` [Intel-gfx] [PATCH 06/23] Revert "drm/i915/gem: Split eb_vma into its own allocation" Maarten Lankhorst
2020-03-31 10:41 ` [Intel-gfx] [PATCH 07/23] drm/i915: Use per object locking in execbuf, v7 Maarten Lankhorst
2020-03-31 10:41 ` [Intel-gfx] [PATCH 08/23] drm/i915: Use ww locking in intel_renderstate Maarten Lankhorst
2020-03-31 10:41 ` [Intel-gfx] [PATCH 09/23] drm/i915: Add ww context handling to context_barrier_task Maarten Lankhorst
2020-03-31 10:41 ` [Intel-gfx] [PATCH 10/23] drm/i915: Nuke arguments to eb_pin_engine Maarten Lankhorst
2020-03-31 10:41 ` [Intel-gfx] [PATCH 11/23] drm/i915: Pin engine before pinning all objects, v3 Maarten Lankhorst
2020-03-31 10:41 ` [Intel-gfx] [PATCH 12/23] drm/i915: Rework intel_context pinning to do everything outside of pin_mutex Maarten Lankhorst
2020-03-31 10:41 ` [Intel-gfx] [PATCH 13/23] drm/i915: Make sure execbuffer always passes ww state to i915_vma_pin Maarten Lankhorst
2020-03-31 10:42 ` [Intel-gfx] [PATCH 14/23] drm/i915: Convert i915_gem_object/client_blt.c to use ww locking as well, v2 Maarten Lankhorst
2020-03-31 10:42 ` [Intel-gfx] [PATCH 15/23] drm/i915: Kill last user of intel_context_create_request outside of selftests Maarten Lankhorst
2020-03-31 10:42 ` [Intel-gfx] [PATCH 16/23] drm/i915: Convert i915_perf to ww locking as well Maarten Lankhorst
2020-03-31 10:42 ` [Intel-gfx] [PATCH 17/23] drm/i915: Dirty hack to fix selftests locking inversion Maarten Lankhorst
2020-03-31 10:42 ` [Intel-gfx] [PATCH 18/23] drm/i915/selftests: Fix locking inversion in lrc selftest Maarten Lankhorst
2020-03-31 10:42 ` [Intel-gfx] [PATCH 19/23] drm/i915: Use ww pinning for intel_context_create_request() Maarten Lankhorst
2020-03-31 10:42 ` [Intel-gfx] [PATCH 20/23] drm/i915: Move i915_vma_lock in the selftests to avoid lock inversion, v2 Maarten Lankhorst
2020-03-31 10:42 ` [Intel-gfx] [PATCH 21/23] drm/i915: Add ww locking to vm_fault_gtt Maarten Lankhorst
2020-03-31 10:42 ` [Intel-gfx] [PATCH 22/23] drm/i915: Add ww locking to pin_to_display_plane Maarten Lankhorst
2020-03-31 10:42 ` [Intel-gfx] [PATCH 23/23] drm/i915: Ensure we hold the pin mutex Maarten Lankhorst
2020-03-31 19:43 ` kbuild test robot
2020-03-31 17:49 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/23] Revert "drm/i915/gem: Drop relocation slowpath" Patchwork
2020-03-31 18:13 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2020-04-01 18:56 ` [Intel-gfx] ✗ Fi.CI.IGT: " Patchwork
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=20200401230443.GA3836@intel.com \
--to=philip.li@intel.com \
--cc=clang-built-linux@googlegroups.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kbuild-all@lists.01.org \
--cc=ndesaulniers@google.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.