drivers/vfio/fsl-mc/vfio_fsl_mc_intr.c
Source file repositories/reference/linux-study-clean/drivers/vfio/fsl-mc/vfio_fsl_mc_intr.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/vfio/fsl-mc/vfio_fsl_mc_intr.c- Extension
.c- Size
- 4187 bytes
- Lines
- 193
- Domain
- Driver Families
- Bucket
- drivers/vfio
- Inferred role
- Driver Families: implementation source
- Status
- source implementation candidate
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
- Touches IRQ or DMA behavior; this matters for the representative real-device path.
- Allocates kernel memory; connect allocation flags and lifetime to context constraints.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/vfio.hlinux/slab.hlinux/types.hlinux/eventfd.hlinux/fsl/mc.hvfio_fsl_mc_private.h
Detected Declarations
function vfio_fsl_mc_irqs_allocatefunction vfio_fsl_mc_irq_handlerfunction vfio_set_triggerfunction vfio_fsl_mc_set_irq_triggerfunction vfio_fsl_mc_set_irqs_ioctlfunction vfio_fsl_mc_irqs_cleanup
Annotated Snippet
// SPDX-License-Identifier: (GPL-2.0+ OR BSD-3-Clause)
/*
* Copyright 2013-2016 Freescale Semiconductor Inc.
* Copyright 2019 NXP
*/
#include <linux/vfio.h>
#include <linux/slab.h>
#include <linux/types.h>
#include <linux/eventfd.h>
#include "linux/fsl/mc.h"
#include "vfio_fsl_mc_private.h"
static int vfio_fsl_mc_irqs_allocate(struct vfio_fsl_mc_device *vdev)
{
struct fsl_mc_device *mc_dev = vdev->mc_dev;
struct vfio_fsl_mc_irq *mc_irq;
int irq_count;
int ret, i;
/* Device does not support any interrupt */
if (mc_dev->obj_desc.irq_count == 0)
return 0;
/* interrupts were already allocated for this device */
if (vdev->mc_irqs)
return 0;
irq_count = mc_dev->obj_desc.irq_count;
mc_irq = kzalloc_objs(*mc_irq, irq_count, GFP_KERNEL_ACCOUNT);
if (!mc_irq)
return -ENOMEM;
/* Allocate IRQs */
ret = fsl_mc_allocate_irqs(mc_dev);
if (ret) {
kfree(mc_irq);
return ret;
}
for (i = 0; i < irq_count; i++) {
mc_irq[i].count = 1;
mc_irq[i].flags = VFIO_IRQ_INFO_EVENTFD;
}
vdev->mc_irqs = mc_irq;
return 0;
}
static irqreturn_t vfio_fsl_mc_irq_handler(int irq_num, void *arg)
{
struct vfio_fsl_mc_irq *mc_irq = (struct vfio_fsl_mc_irq *)arg;
eventfd_signal(mc_irq->trigger);
return IRQ_HANDLED;
}
static int vfio_set_trigger(struct vfio_fsl_mc_device *vdev,
int index, int fd)
{
struct vfio_fsl_mc_irq *irq = &vdev->mc_irqs[index];
struct eventfd_ctx *trigger;
int hwirq;
int ret;
hwirq = vdev->mc_dev->irqs[index]->virq;
if (irq->trigger) {
free_irq(hwirq, irq);
kfree(irq->name);
eventfd_ctx_put(irq->trigger);
irq->trigger = NULL;
}
if (fd < 0) /* Disable only */
return 0;
irq->name = kasprintf(GFP_KERNEL_ACCOUNT, "vfio-irq[%d](%s)",
hwirq, dev_name(&vdev->mc_dev->dev));
if (!irq->name)
return -ENOMEM;
trigger = eventfd_ctx_fdget(fd);
if (IS_ERR(trigger)) {
kfree(irq->name);
return PTR_ERR(trigger);
}
Annotation
- Immediate include surface: `linux/vfio.h`, `linux/slab.h`, `linux/types.h`, `linux/eventfd.h`, `linux/fsl/mc.h`, `vfio_fsl_mc_private.h`.
- Detected declarations: `function vfio_fsl_mc_irqs_allocate`, `function vfio_fsl_mc_irq_handler`, `function vfio_set_trigger`, `function vfio_fsl_mc_set_irq_trigger`, `function vfio_fsl_mc_set_irqs_ioctl`, `function vfio_fsl_mc_irqs_cleanup`.
- Atlas domain: Driver Families / drivers/vfio.
- Implementation status: source implementation candidate.
- Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
- IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.