linux-kernel - Re: [PATCH 3/5] dt-bindings: Add Bao I/O dispatcher driver binding

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20251225-modest-faithful-mouflon-1c7d63@quoll>
Date: Thu, 25 Dec 2025 09:58:48 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: joaopeixoto@...x.tech
Cc: linux-kernel@...r.kernel.org, ajd@...ux.ibm.com, alex@...ti.fr, 
	aou@...s.berkeley.edu, bagasdotme@...il.com, catalin.marinas@....com, 
	conor+dt@...nel.org, corbet@....net, dan.j.williams@...el.com, 
	davidmcerdeira@...x.tech, devicetree@...r.kernel.org, dev@...l-k.io, 
	gregkh@...uxfoundation.org, haren@...ux.ibm.com, heiko@...ech.de, jose@...x.tech, 
	kever.yang@...k-chips.com, krzk+dt@...nel.org, linux-arm-kernel@...ts.infradead.org, 
	linux@...linux.org.uk, linux-doc@...r.kernel.org, linux-riscv@...ts.infradead.org, 
	maddy@...ux.ibm.com, mani@...nel.org, nathan@...nel.org, neil.armstrong@...aro.org, 
	palmer@...belt.com, pjw@...nel.org, prabhakar.mahadev-lad.rj@...renesas.com, 
	robh@...nel.org, will@...nel.org
Subject: Re: [PATCH 3/5] dt-bindings: Add Bao I/O dispatcher driver binding

On Wed, Dec 24, 2025 at 01:52:15PM +0000, joaopeixoto@...x.tech wrote:
> From: João Peixoto <joaopeixoto@...x.tech>
> 
> This patch adds a Device Tree binding for the Bao I/O Dispatcher kernel
> module, which can be loaded into backend VMs. The I/O Dispatcher
> provides the bridge between the Bao hypervisor Remote I/O system and the
> frontend device model in userspace, offering a unified API to support
> various VirtIO backends.
> 
> The dispatcher handles hypercalls to the Bao hypervisor, IRQ/eventfd
> forwarding, and provides a character device interface for frontend
> devices, enabling efficient communication between the hypervisor and
> userspace device models.
> 
> The binding documents the following properties:
>   - compatible: "bao,io-dispatcher"
>   - reg: Memory regions for the dispatcher (multiple VirtIO devices)
>   - interrupts: Interrupts used by the devices
>   - interrupt-parent: Parent interrupt controller
> 
> This enables kernel drivers to correctly instantiate and configure Bao
> I/O Dispatcher modules based on the DT description.
> 
> Signed-off-by: João Peixoto <joaopeixoto@...x.tech>
> ---
>  .../bindings/bao/io-dispatcher.yaml           | 67 +++++++++++++++++++
>  1 file changed, 67 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/bao/io-dispatcher.yaml
> 
> diff --git a/Documentation/devicetree/bindings/bao/io-dispatcher.yaml b/Documentation/devicetree/bindings/bao/io-dispatcher.yaml
> new file mode 100644
> index 000000000000..7795f55d3ff9
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/bao/io-dispatcher.yaml
> @@ -0,0 +1,67 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: "http://devicetree.org/schemas/bao/io-dispatcher.yaml#"

You did not even bother to test it.

> +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
> +
> +title: Bao I/O Dispatcher Device
> +
> +maintainers:
> +  - João Peixoto <joaopeixoto@...x.tech>
> +  - José Martins <jose@...x.tech>
> +  - David Cerdeira <davidmcerdeira@...x.tech>
> +
> +description: |
> +  I/O Dispatcher device for Bao hypervisor guests. Handles multiple VirtIO
> +  backend devices and their interrupts.
> +
> +properties:
> +  compatible:
> +    const: "bao,io-dispatcher"
> +    description: Device compatible string.
> +
> +  reg:
> +    description: |
> +      Memory regions for each VirtIO backend device.
> +    maxItems: 20
> +    type: array
> +    items:
> +      type: integer

Don't send us LLM junk. You cannot come with such syntax, it does
not exist. Sending such LLM output is disregard to our time.

NAK


Best regards,
Krzysztof