From: kernel test robot <lkp@intel.com>
To: Sean Christopherson <seanjc@google.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Kevin Tian <kevin.tian@intel.com>
Subject: [sean-jc:sink 54/177] drivers/vhost/vdpa.c:219:32: error: no member named 'token' in 'struct irq_bypass_producer'
Date: Tue, 6 May 2025 12:06:25 +0800 [thread overview]
Message-ID: <202505061105.pA1KZRCK-lkp@intel.com> (raw)
tree: https://github.com/sean-jc/linux sink
head: b64923e38c20d35f52d3e78fe87993306d912851
commit: 55503e04dc3db68bfba5486acee4a8baa0ef8765 [54/177] irqbypass: Take ownership of producer/consumer token tracking
config: hexagon-allyesconfig (https://download.01.org/0day-ci/archive/20250506/202505061105.pA1KZRCK-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project f819f46284f2a79790038e1f6649172789734ae8)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250506/202505061105.pA1KZRCK-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/202505061105.pA1KZRCK-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/vhost/vdpa.c:219:32: error: no member named 'token' in 'struct irq_bypass_producer'
219 | qid, vq->call_ctx.producer.token, ret);
| ~~~~~~~~~~~~~~~~~~~~~ ^
include/linux/dev_printk.h:160:67: note: expanded from macro 'dev_info'
160 | dev_printk_index_wrap(_dev_info, KERN_INFO, dev, dev_fmt(fmt), ##__VA_ARGS__)
| ^~~~~~~~~~~
include/linux/dev_printk.h:110:23: note: expanded from macro 'dev_printk_index_wrap'
110 | _p_func(dev, fmt, ##__VA_ARGS__); \
| ^~~~~~~~~~~
1 error generated.
vim +219 drivers/vhost/vdpa.c
776f395004d829 Zhu Lingshan 2020-06-05 197
2cf1ba9a4d15cb Zhu Lingshan 2020-07-31 198 static void vhost_vdpa_setup_vq_irq(struct vhost_vdpa *v, u16 qid)
2cf1ba9a4d15cb Zhu Lingshan 2020-07-31 199 {
2cf1ba9a4d15cb Zhu Lingshan 2020-07-31 200 struct vhost_virtqueue *vq = &v->vqs[qid];
2cf1ba9a4d15cb Zhu Lingshan 2020-07-31 201 const struct vdpa_config_ops *ops = v->vdpa->config;
2cf1ba9a4d15cb Zhu Lingshan 2020-07-31 202 struct vdpa_device *vdpa = v->vdpa;
2cf1ba9a4d15cb Zhu Lingshan 2020-07-31 203 int ret, irq;
2cf1ba9a4d15cb Zhu Lingshan 2020-07-31 204
2cf1ba9a4d15cb Zhu Lingshan 2020-07-31 205 if (!ops->get_vq_irq)
2cf1ba9a4d15cb Zhu Lingshan 2020-07-31 206 return;
2cf1ba9a4d15cb Zhu Lingshan 2020-07-31 207
2cf1ba9a4d15cb Zhu Lingshan 2020-07-31 208 irq = ops->get_vq_irq(vdpa, qid);
cce0ab2b2a3907 Zhu Lingshan 2022-02-22 209 if (irq < 0)
cce0ab2b2a3907 Zhu Lingshan 2022-02-22 210 return;
cce0ab2b2a3907 Zhu Lingshan 2022-02-22 211
cce0ab2b2a3907 Zhu Lingshan 2022-02-22 212 if (!vq->call_ctx.ctx)
2cf1ba9a4d15cb Zhu Lingshan 2020-07-31 213 return;
2cf1ba9a4d15cb Zhu Lingshan 2020-07-31 214
2cf1ba9a4d15cb Zhu Lingshan 2020-07-31 215 vq->call_ctx.producer.irq = irq;
55503e04dc3db6 Sean Christopherson 2025-04-04 216 ret = irq_bypass_register_producer(&vq->call_ctx.producer, vq->call_ctx.ctx);
e01afe36df1a9e Zhu Lingshan 2020-10-23 217 if (unlikely(ret))
e01afe36df1a9e Zhu Lingshan 2020-10-23 218 dev_info(&v->dev, "vq %u, irq bypass producer (token %p) registration fails, ret = %d\n",
e01afe36df1a9e Zhu Lingshan 2020-10-23 @219 qid, vq->call_ctx.producer.token, ret);
2cf1ba9a4d15cb Zhu Lingshan 2020-07-31 220 }
2cf1ba9a4d15cb Zhu Lingshan 2020-07-31 221
:::::: The code at line 219 was first introduced by commit
:::::: e01afe36df1a9e42cacdb9c5b99512ec69a6f14b vdpa: handle irq bypass register failure case
:::::: TO: Zhu Lingshan <lingshan.zhu@intel.com>
:::::: CC: Michael S. Tsirkin <mst@redhat.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-05-06 4:06 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=202505061105.pA1KZRCK-lkp@intel.com \
--to=lkp@intel.com \
--cc=kevin.tian@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