[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1608091117250.5388@nanos>
Date: Tue, 9 Aug 2016 11:19:18 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Eric Auger <eric.auger@...hat.com>
cc: eric.auger.pro@...il.com, christoffer.dall@...aro.org,
marc.zyngier@....com, robin.murphy@....com,
alex.williamson@...hat.com, will.deacon@....com, joro@...tes.org,
jason@...edaemon.net, linux-arm-kernel@...ts.infradead.org,
kvm@...r.kernel.org, drjones@...hat.com,
linux-kernel@...r.kernel.org, Bharat.Bhushan@...escale.com,
pranav.sawargaonkar@...il.com, p.fedin@...sung.com,
iommu@...ts.linux-foundation.org, Jean-Philippe.Brucker@....com,
yehuday@...vell.com, Manish.Jaggi@...iumnetworks.com,
robert.richter@...iumnetworks.com, dennis.chen@....com
Subject: Re: [PATCH v12 02/11] genirq/msi: msi_compose wrapper
On Tue, 2 Aug 2016, Eric Auger wrote:
> Currently the MSI message is composed by directly calling
> irq_chip_compose_msi_msg and erased by setting the memory to zero.
>
> On some platforms, we will need to complexify this composition to
> properly handle MSI emission through IOMMU. Also we will need to track
> when the MSI message is erased.
I just can't find how you do that. After applying the series the
> + if (erase)
> + memset(msg, 0, sizeof(*msg));
branch is still just a memset(). The wrapper is fine for the compose side, but
having the extra argument just to wrap the memset() for no gain is silly.
Thanks,
tglx
Powered by blists - more mailing lists