All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [jpoimboe:asm-call-constraint-fix 4/5] arch/x86/include/asm/mshyperv.h:145:57: error: expected ':' or ')' before string constant
Date: Fri, 28 Feb 2025 21:07:13 +0800	[thread overview]
Message-ID: <202502282113.TMGQZuLi-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/jpoimboe/linux.git asm-call-constraint-fix
head:   a882d0410fb655d41b5c5158dcd1a720275cf505
commit: 8f0a744bb81e98286456e1f433565240cd66e440 [4/5] x86: Convert ASM_CALL_CONSTRAINT to input constraint
config: x86_64-buildonly-randconfig-003-20250228 (https://download.01.org/0day-ci/archive/20250228/202502282113.TMGQZuLi-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250228/202502282113.TMGQZuLi-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202502282113.TMGQZuLi-lkp@intel.com/

All errors (new ones prefixed by >>):

   In file included from arch/x86/hyperv/hv_apic.c:29:
   arch/x86/include/asm/mshyperv.h: In function '_hv_do_fast_hypercall8':
>> arch/x86/include/asm/mshyperv.h:145:57: error: expected ':' or ')' before string constant
     145 |                                      : "=a" (hv_status) "+c" (control),
         |                                                         ^~~~


vim +145 arch/x86/include/asm/mshyperv.h

   126	
   127	/* Fast hypercall with 8 bytes of input and no output */
   128	static inline u64 _hv_do_fast_hypercall8(u64 control, u64 input1)
   129	{
   130		u64 hv_status;
   131	
   132	#ifdef CONFIG_X86_64
   133		if (hv_isolation_type_tdx() && !hyperv_paravisor_present)
   134			return hv_tdx_hypercall(control, input1, 0);
   135	
   136		if (hv_isolation_type_snp() && !hyperv_paravisor_present) {
   137			__asm__ __volatile__(
   138					"vmmcall"
   139					: "=a" (hv_status), "+c" (control),
   140					  "+d" (input1)
   141					: ASM_CALL_CONSTRAINT
   142					: "cc", "r8", "r9", "r10", "r11");
   143		} else {
   144			__asm__ __volatile__(CALL_NOSPEC
 > 145					     : "=a" (hv_status) "+c" (control),
   146					       "+d" (input1)
   147					     : THUNK_TARGET(hv_hypercall_pg)
   148					       COMMA(ASM_CALL_CONSTRAINT)
   149					     : "cc", "r8", "r9", "r10", "r11");
   150		}
   151	#else
   152		{
   153			u32 input1_hi = upper_32_bits(input1);
   154			u32 input1_lo = lower_32_bits(input1);
   155	
   156			__asm__ __volatile__ (CALL_NOSPEC
   157					      : "=A"(hv_status), "+c"(input1_lo)
   158					      :	"A" (control), "b" (input1_hi),
   159						THUNK_TARGET(hv_hypercall_pg)
   160						COMMA(ASM_CALL_CONSTRAINT)
   161					      : "cc", "edi", "esi");
   162		}
   163	#endif
   164			return hv_status;
   165	}
   166	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2025-02-28 13:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202502282113.TMGQZuLi-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=jpoimboe@kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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.