From: Masami Hiramatsu <mhiramat@kernel.org>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
"H . Peter Anvin" <hpa@zytor.com>,
x86@kernel.org
Subject: Re: [PATCH] x86/decoder: Update UD0 to have operands
Date: Tue, 13 Feb 2018 01:34:14 +0900 [thread overview]
Message-ID: <20180213013414.bc8ee339bf7999149acc6636@kernel.org> (raw)
In-Reply-To: <201802110336.UCMZHvli%fengguang.wu@intel.com>
On Sun, 11 Feb 2018 03:26:12 +0800
kbuild test robot <lkp@intel.com> wrote:
> Hi Masami,
>
> I love your patch! Perhaps something to improve:
>
> [auto build test WARNING on tip/auto-latest]
> [also build test WARNING on v4.15 next-20180209]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
>
> url: https://github.com/0day-ci/linux/commits/Masami-Hiramatsu/x86-decoder-Update-UD0-to-have-operands/20180211-013327
> config: x86_64-acpi-redef (attached as .config)
> compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> All warnings (new ones prefixed by >>):
>
> >> drivers/regulator/devres.o: warning: objtool: devm_regulator_unregister_notifier()+0x2e: can't decode instruction
> --
> >> sound/core/info.o: warning: objtool: snd_info_get_line()+0x9: can't find jump dest instruction at .text+0x8b5
> --
> >> sound/core/sound_oss.o: warning: objtool: snd_oss_kernel_minor()+0x5: can't find jump dest instruction at .text+0x36
> --
> >> sound/core/hwdep.o: warning: objtool: snd_hwdep_dsp_load()+0x78: can't find jump dest instruction at .text+0x5fa
> --
> >> sound/core/timer.o: warning: objtool: snd_timer_notify()+0x49: return with modified stack frame
> --
> >> sound/core/hrtimer.o: warning: objtool: snd_hrtimer_callback()+0x62: can't find jump dest instruction at .text+0x108
> --
> >> sound/core/pcm_lib.o: warning: objtool: snd_pcm_playback_silence()+0x17b: can't find jump dest instruction at .text+0x9b9
> --
> >> sound/drivers/opl3/opl3_lib.o: warning: objtool: snd_opl3_create()+0x1f5: can't find jump dest instruction at .text+0x628
> --
> >> sound/drivers/opl3/opl3_midi.o: warning: objtool: snd_opl3_kill_voice()+0x9: can't find jump dest instruction at .text+0x12
> --
> >> drivers/media/dvb-core/dvb_math.o: warning: objtool: intlog2()+0x2: can't find jump dest instruction at .text+0x9
> --
> >> drivers/gpu/drm/ttm/ttm_execbuf_util.o: warning: objtool: ttm_eu_backoff_reservation()+0x64: can't find jump dest instruction at .text+0xb5
> ..
Ugg, OK this is what I worried about :(
This might mean gcc generated UD0 without MODRM binary but the tool check it with MODRM...
I will check it.
Thanks,
--
Masami Hiramatsu <mhiramat@kernel.org>
prev parent reply other threads:[~2018-02-12 16:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 6:15 arch/x86/tools/insn_decoder_test: warning: ffffffff810005de: 0f ff e8 ud0 %eax,%ebp kbuild test robot
2018-02-08 15:17 ` [PATCH] x86/decoder: Update UD0 to have operands Masami Hiramatsu
2018-02-10 19:26 ` kbuild test robot
2018-02-12 16:34 ` Masami Hiramatsu [this message]
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=20180213013414.bc8ee339bf7999149acc6636@kernel.org \
--to=mhiramat@kernel.org \
--cc=hpa@zytor.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@kernel.org \
--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
all inboxes | Powered by JetHome®