Messages in this thread | | | Date | Tue, 21 Aug 2012 10:42:57 -0400 | From | Konrad Rzeszutek Wilk <> | Subject | Re: [PATCH 17/19] x86, msi: Introduce x86_msi.compose_msi_msg call-back |
| |
On Tue, Aug 21, 2012 at 10:40:07AM +0200, Joerg Roedel wrote: > On Mon, Aug 20, 2012 at 10:08:44AM -0400, Konrad Rzeszutek Wilk wrote: > > On Mon, Aug 20, 2012 at 03:56:03PM +0200, Joerg Roedel wrote: > > > This call-back points to the right function for initializing > > > the msi_msg structure. > > > > What is the 'hpet_id' purpose in this? > > The VT-d implementation uses it. This function is used to create the MSI > message for PCI devices and the HPET. When it is called for the HPET the > pdev parameter is NULL and hpet_id is valid.
Perhaps then a more generic term? 'void *platform_priv' ?
| |