Re: [PATCH] xen/events: don't use chip_data for legacy IRQs

2020-09-30 Thread boris . ostrovsky
On 9/30/20 5:16 AM, Juergen Gross wrote: > Since commit c330fb1ddc0a ("XEN uses irqdesc::irq_data_common::handler_data > to store a per interrupt XEN data pointer which contains XEN specific > information.") > Xen is using the chip_data pointer for storing IRQ specific data. When > running as a

Re: [PATCH] xen/events: don't use chip_data for legacy IRQs

2020-09-30 Thread Stefan Bader
On 30.09.20 11:16, Juergen Gross wrote: > Since commit c330fb1ddc0a ("XEN uses irqdesc::irq_data_common::handler_data > to store a per interrupt XEN data pointer which contains XEN specific > information.") > Xen is using the chip_data pointer for storing IRQ specific data. When > running as a HV

[PATCH] xen/events: don't use chip_data for legacy IRQs

2020-09-30 Thread Juergen Gross
Since commit c330fb1ddc0a ("XEN uses irqdesc::irq_data_common::handler_data to store a per interrupt XEN data pointer which contains XEN specific information.") Xen is using the chip_data pointer for storing IRQ specific data. When running as a HVM domain this can result in problems for legacy IR