On Thu, Apr 24, 2025 at 08:19:39PM +0200, Daniel Wagner wrote: > I've added back the isolcpus io_queue agrument. This avoids any semantic > changes of managed_irq.
IMO, this is correct thing to do. > I don't like it but I haven't found a > better way to deal with it. Ming clearly stated managed_irq should not > change. Precisely, we can't cause io hang and break existing managed_irq applications, especially you know there isn't kernel solution for it, same for v5, v6 or whatever. I will look at v6 this week. Thanks, Ming
