> -----Original Message----- > From: Thomas Gleixner [mailto:tglx@xxxxxxxxxxxxx] > Sent: Tuesday, December 12, 2017 10:37 PM > To: Anand, Jerome <jerome.anand@xxxxxxxxx> > Cc: Ville Syrjälä <ville.syrjala@xxxxxxxxxxxxxxx>; Chen, Augustine > <augustine.chen@xxxxxxxxx>; intel-gfx@xxxxxxxxxxxxxxxxxxxxx; alsa-devel@alsa- > project.org; Bossart, Pierre-louis <pierre-louis.bossart@xxxxxxxxx>; > tiwai@xxxxxxx; Ingo Molnar <mingo@xxxxxxxxxx>; H. Peter Anvin > <hpa@xxxxxxxxx>; Jiang Liu <jiang.liu@xxxxxxxxxxxxxxx>; Juergen Gross > <jgross@xxxxxxxx>; Dou Liyang <douly.fnst@xxxxxxxxxxxxxx>; linux- > kernel@xxxxxxxxxxxxxxx > Subject: RE: [PATCH] drm/i915: Remove unused IRQ chip data of > HDMI LPE audio > > On Mon, 11 Dec 2017, Anand, Jerome wrote: > > > On Fri, 8 Dec 2017, Ville Syrjälä wrote: > > > > > > > On Fri, Dec 08, 2017 at 05:33:23PM +0800, Augustine.Chen wrote: > > > > > The chip data of HDMI LPE audio is set to drm_i915_private which > > > > > is not consistent with the expectation by x86 APIC driver. > > > > > > > > Hmm. Why is the apic code looking at data for an irq chip it > > > > hasn't created? > > > > > > > > apic code expects an irq domain to be place as generic approach. > > APIC code does not even see that interrupt at all. It's completely disconnected. > That's the problem - APIC just converts the chip data to its internal format and fails. > > > > > In the case of not enabling CONFIG_CPUMASK_OFFSTACK, this would > > > > > cause kernel panic while doing CPU hotplug. > > > > > > And why so? Surely not because you set irq_chip_data. That's really > > > no explanation at all. > > > > > > > Ideally, I feel there needs to be an irq domain for mapping the irq > > numbers with hwirq. It is not created as part of the hdmi lpe audio > > bridge. Since the logic to mask/unmask lpe audio interrupts is > > removed, there is no need of the Chip data or creation of the domain now. > > That still does not explain why this is broken with > CONFIG_CPUMASK_OFFSTACK=n and cpu hotplug. > If the config option is enabled, the address accessed by APIC is valid as shown below else it tries to access locations which might or might not be valid based on the chip data set. This is the reason why some drivers work and some don't. I feel this needs to be fixed in APIC - not sure though ! #ifdef CONFIG_CPUMASK_OFFSTACK typedef struct cpumask *cpumask_var_t; ... #else typedef struct cpumask cpumask_var_t[1]; ... #endif > Thanks, > > tglx _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
