From: kernel test robot <lkp@intel.com>
To: Sean Christopherson <seanjc@google.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [sean-jc:x86/unfudge_irq_bypass 69/72] arch/x86/include/../../../drivers/iommu/amd/amd_iommu_types.h:895:3: error: unknown type name 'u128'
Date: Sat, 12 Apr 2025 23:52:12 +0800 [thread overview]
Message-ID: <202504122327.ML6cln49-lkp@intel.com> (raw)
tree: https://github.com/sean-jc/linux x86/unfudge_irq_bypass
head: eb313cd2befb6b7fdcab08d5c7d41ad3cb8f3ec2
commit: 90742a7369ff07f4d093b61b7205c5d4f77b81a1 [69/72] *** DO NOT MERGE *** iommu/amd: Hack to fake IRQ posting support
config: i386-buildonly-randconfig-003-20250412 (https://download.01.org/0day-ci/archive/20250412/202504122327.ML6cln49-lkp@intel.com/config)
compiler: clang version 20.1.2 (https://github.com/llvm/llvm-project 58df0ef89dd64126512e4ee27b4ac3fd8ddf6247)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250412/202504122327.ML6cln49-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/202504122327.ML6cln49-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from arch/x86/kvm/svm/avic.c:31:
>> arch/x86/include/../../../drivers/iommu/amd/amd_iommu_types.h:895:3: error: unknown type name 'u128'
895 | u128 data128[2];
| ^
arch/x86/include/../../../drivers/iommu/amd/amd_iommu_types.h:1053:3: error: unknown type name 'u128'
1053 | u128 irte;
| ^
2 errors generated.
vim +/u128 +895 arch/x86/include/../../../drivers/iommu/amd/amd_iommu_types.h
8d283c35a293e6 include/asm-x86/amd_iommu_types.h Joerg Roedel 2008-06-26 888
5694703f14b1f6 include/asm-x86/amd_iommu_types.h Joerg Roedel 2008-07-11 889 /*
5694703f14b1f6 include/asm-x86/amd_iommu_types.h Joerg Roedel 2008-07-11 890 * Structure defining one entry in the device table
5694703f14b1f6 include/asm-x86/amd_iommu_types.h Joerg Roedel 2008-07-11 891 */
8d283c35a293e6 include/asm-x86/amd_iommu_types.h Joerg Roedel 2008-06-26 892 struct dev_table_entry {
8b3f78733814b1 drivers/iommu/amd/amd_iommu_types.h Suravee Suthikulpanit 2024-11-18 893 union {
ee6c28684585a6 drivers/iommu/amd_iommu_types.h Joerg Roedel 2011-11-09 894 u64 data[4];
8b3f78733814b1 drivers/iommu/amd/amd_iommu_types.h Suravee Suthikulpanit 2024-11-18 @895 u128 data128[2];
8b3f78733814b1 drivers/iommu/amd/amd_iommu_types.h Suravee Suthikulpanit 2024-11-18 896 };
8d283c35a293e6 include/asm-x86/amd_iommu_types.h Joerg Roedel 2008-06-26 897 };
8d283c35a293e6 include/asm-x86/amd_iommu_types.h Joerg Roedel 2008-06-26 898
:::::: The code at line 895 was first introduced by commit
:::::: 8b3f78733814b180089a400743b6f19d118aec62 iommu/amd: Introduce helper function to update 256-bit DTE
:::::: TO: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
:::::: CC: Joerg Roedel <jroedel@suse.de>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-04-12 15:52 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=202504122327.ML6cln49-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=seanjc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).