Re: [kbuild-all] Re: [patch 06/12] x86/entry: Convert system vectors to irq stack macro

[Rong Chen]

On 2/5/21 10:13 PM, Peter Zijlstra wrote:
> On Fri, Feb 05, 2021 at 11:52:40AM +0800, kernel test robot wrote:
> > Hi Thomas,
> >
> > I love your patch! Perhaps something to improve:
> >
> > [auto build test WARNING on tip/x86/asm]
> > [also build test WARNING on tip/master linus/master tip/x86/core v5.11-rc6 next-20210125]
> > [If your patch is applied to the wrong git tree, kindly drop us a note.
> > And when submitting patch, we suggest to use '--base' as documented in
> > https://git-scm.com/docs/git-format-patch]
> >
> > url:    https://github.com/0day-ci/linux/commits/Thomas-Gleixner/x86-irq-64-Inline-irq-stack-switching/20210205-091059
> > base:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git 5c99720b28381bb400d4f546734c34ddaf608761
> > config: x86_64-randconfig-r026-20210204 (attached as .config)
> > compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
> > reproduce (this is a W=1 build):
> >          # https://github.com/0day-ci/linux/commit/d91ff58e804175dd59e483c7cf236e1fe66c2187
> >          git remote add linux-review https://github.com/0day-ci/linux
> >          git fetch --no-tags linux-review Thomas-Gleixner/x86-irq-64-Inline-irq-stack-switching/20210205-091059
> >          git checkout d91ff58e804175dd59e483c7cf236e1fe66c2187
> >          # save the attached .config to linux build tree
> >          make W=1 ARCH=x86_64
> >
> > If you fix the issue, kindly add following tag as appropriate
> > Reported-by: kernel test robot <lkp@xxxxxxxxx>
> >
> > All warnings (new ones prefixed by >>):
> >
> > > > arch/x86/hyperv/hv_init.o: warning: objtool: sysvec_hyperv_reenlightenment()+0x7f: undefined stack state
> > --
> > > > arch/x86/kernel/cpu/mshyperv.o: warning: objtool: sysvec_hyperv_callback()+0x7f: undefined stack state
> > > > arch/x86/kernel/cpu/mshyperv.o: warning: objtool: sysvec_hyperv_stimer0()+0x7f: undefined stack state
> It would help if you'd actually applied the patches to a tree that had
> the required objtool patches as described in 0/n. Or better yet, don't
> scrape emails if the 0/n includes a git link which you'll run on anyway.

Hi Peter,

Thanks for the advice, we'll add the check to our cluster,
and sorry for the inconvenience.

Best Regards,
Rong Chen