linux-kernel - RE: [patch V2 03/33] genirq/msi: Provide data structs for per device domains

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: <875yf5gb8j.ffs@tglx>
Date:   Wed, 23 Nov 2022 12:29:32 +0100
From:   Thomas Gleixner <tglx@...utronix.de>
To:     "Tian, Kevin" <kevin.tian@...el.com>,
        LKML <linux-kernel@...r.kernel.org>
Cc:     "x86@...nel.org" <x86@...nel.org>, Joerg Roedel <joro@...tes.org>,
        Will Deacon <will@...nel.org>,
        "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
        Bjorn Helgaas <bhelgaas@...gle.com>,
        Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
        Marc Zyngier <maz@...nel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Jason Gunthorpe <jgg@...lanox.com>,
        "Jiang, Dave" <dave.jiang@...el.com>,
        Alex Williamson <alex.williamson@...hat.com>,
        "Williams, Dan J" <dan.j.williams@...el.com>,
        Logan Gunthorpe <logang@...tatee.com>,
        "Raj, Ashok" <ashok.raj@...el.com>, Jon Mason <jdmason@...zu.us>,
        Allen Hubbe <allenbh@...il.com>
Subject: RE: [patch V2 03/33] genirq/msi: Provide data structs for per
 device domains

On Wed, Nov 23 2022 at 07:57, Kevin Tian wrote:
>> From: Thomas Gleixner <tglx@...utronix.de>
>> Sent: Monday, November 21, 2022 10:38 PM
>> 
>> Provide struct msi_domain_template which contains a bundle of struct
>> irq_chip, struct msi_domain_ops and struct msi_domain_info and a name
>> field.
>> 
>> This template is used by MSI device domain implementations to provide the
>> domain specific functionality, feature bits etc.
>> 
>> When a MSI domain is created the template is duplicated in the core code
>> so that it can be modified per instance. That means templates can be
>> marked const at the MSI device domain code.
>> 
>> The template is a bundle to avoid several allocations and duplications
>> of the involved structures.
>> 
>> The name field is used to construct the final domain and chip name via:
>> 
>>     $PREFIX-$NAME-$DEVNAME
>
> $PREFIX$NAME-$DEVNAME

Indeed.