From: kernel test robot <lkp@intel.com>
To: Naman Jain <namjain@linux.microsoft.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Wei Liu <wei.liu@kernel.org>,
Roman Kisel <romank@linux.microsoft.com>,
Saurabh Sengar <ssengar@linux.microsoft.com>,
Alok Tiwari <alok.a.tiwari@oracle.com>,
Nuno Das Neves <nunodasneves@linux.microsoft.com>,
Michael Kelley <mhklinux@outlook.com>
Subject: [linux-next:master 3139/4234] error: <unknown>:0:0: ran out of registers during register allocation in function 'hv_call_get_vp_registers'
Date: Sun, 24 Aug 2025 08:32:48 +0200 [thread overview]
Message-ID: <202508240828.pVaUV45D-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 0f4c93f7eb861acab537dbe94441817a270537bf
commit: 96a1d2495c2f48467a91b8657bd594350b84ea9e [3139/4234] Drivers: hv: Introduce mshv_vtl driver
config: i386-buildonly-randconfig-2003-20250824 (https://download.01.org/0day-ci/archive/20250824/202508240828.pVaUV45D-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250824/202508240828.pVaUV45D-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/202508240828.pVaUV45D-lkp@intel.com/
All errors (new ones prefixed by >>):
>> error: <unknown>:0:0: ran out of registers during register allocation in function 'hv_call_get_vp_registers'
>> error: <unknown>:0:0: ran out of registers during register allocation in function 'hv_call_set_vp_registers'
>> error: <unknown>:0:0: ran out of registers during register allocation in function 'hv_call_get_partition_property'
3 errors generated.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-08-24 6:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-24 6:32 kernel test robot [this message]
2025-08-24 17:43 ` [linux-next:master 3139/4234] error: <unknown>:0:0: ran out of registers during register allocation in function 'hv_call_get_vp_registers' Naman Jain
2025-08-25 17:00 ` Nathan Chancellor
2025-08-26 6:40 ` Naman Jain
2025-08-26 6:50 ` Philip Li
2025-08-25 17:06 ` Michael Kelley
2025-08-25 17:26 ` Nathan Chancellor
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=202508240828.pVaUV45D-lkp@intel.com \
--to=lkp@intel.com \
--cc=alok.a.tiwari@oracle.com \
--cc=llvm@lists.linux.dev \
--cc=mhklinux@outlook.com \
--cc=namjain@linux.microsoft.com \
--cc=nunodasneves@linux.microsoft.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=romank@linux.microsoft.com \
--cc=ssengar@linux.microsoft.com \
--cc=wei.liu@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