linux-kernel - Re: [RFC PATCH v3 1/4] vfio: Define device specific irq type capability

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: <20190627061942.k5onxbm27dju3iv5@sirius.home.kraxel.org>
Date:   Thu, 27 Jun 2019 08:19:42 +0200
From:   Gerd Hoffmann <kraxel@...hat.com>
To:     Tina Zhang <tina.zhang@...el.com>
Cc:     intel-gvt-dev@...ts.freedesktop.org, kvm@...r.kernel.org,
        linux-kernel@...r.kernel.org, zhenyuw@...ux.intel.com,
        zhiyuan.lv@...el.com, zhi.a.wang@...el.com, kevin.tian@...el.com,
        hang.yuan@...el.com, alex.williamson@...hat.com
Subject: Re: [RFC PATCH v3 1/4] vfio: Define device specific irq type
 capability

  Hi,

> +struct vfio_irq_info_cap_type {
> +	struct vfio_info_cap_header header;
> +	__u32 type;     /* global per bus driver */
> +	__u32 subtype;  /* type specific */

Do we really need both type and subtype?

cheers,
  Gerd