[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190913144051.GA5310@mellanox.com>
Date: Fri, 13 Sep 2019 14:40:56 +0000
From: Jason Gunthorpe <jgg@...lanox.com>
To: Megha Dey <megha.dey@...ux.intel.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"x86@...nel.org" <x86@...nel.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"maz@...nel.org" <maz@...nel.org>,
"bhelgaas@...gle.com" <bhelgaas@...gle.com>,
"rafael@...nel.org" <rafael@...nel.org>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"hpa@...or.com" <hpa@...or.com>,
"alex.williamson@...hat.com" <alex.williamson@...hat.com>,
"ashok.raj@...el.com" <ashok.raj@...el.com>,
"megha.dey@...el.com" <megha.dey@...el.com>,
"jacob.jun.pan@...el.com" <jacob.jun.pan@...el.com>
Subject: Re: [RFC V1 1/7] genirq/msi: Differentiate between various MSI based
interrupts
On Thu, Sep 12, 2019 at 06:32:02PM -0700, Megha Dey wrote:
> Since a device can support both MSI-X and IMS interrupts simultaneously,
> do away with is_msix and introduce a new enum msi_desc_tag to
> differentiate between the various types of msi_descs.
It would be clearer if this commit message explaind that this is a
cleanup creating a normal tagged union:
struct msi_desc {
[..]
union {
Where the tag says which of the elements in the union is filled in
> +enum msi_desc_tags {
> + IRQ_MSI_TAG_MSI,
> + IRQ_MSI_TAG_MSIX,
> + IRQ_MSI_TAG_IMS,
And don't add IMS to the enum until you add a IMS member to the union.
Jason
Powered by blists - more mailing lists