From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753069AbbGNRcR (ORCPT ); Tue, 14 Jul 2015 13:32:17 -0400 Received: from www.linutronix.de ([62.245.132.108]:33337 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751627AbbGNRcQ (ORCPT ); Tue, 14 Jul 2015 13:32:16 -0400 Date: Tue, 14 Jul 2015 19:32:02 +0200 (CEST) From: Thomas Gleixner To: Boris Ostrovsky cc: LKML , Ingo Molnar , Peter Zijlstra , Peter Anvin , xiao jin , Joerg Roedel , Borislav Petkov , Yanmin Zhang , xen-devel Subject: Re: [patch 1/4] hotplug: Prevent alloc/free of irq descriptors during cpu up/down In-Reply-To: <55A532C2.4080306@oracle.com> Message-ID: References: <20150705170530.849428850@linutronix.de> <20150705171102.063519515@linutronix.de> <55A51F10.7010407@oracle.com> <55A532C2.4080306@oracle.com> User-Agent: Alpine 2.11 (DEB 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 14 Jul 2015, Boris Ostrovsky wrote: > On 07/14/2015 11:44 AM, Thomas Gleixner wrote: > > On Tue, 14 Jul 2015, Boris Ostrovsky wrote: > > > > Prevent allocation and freeing of interrupt descriptors accross cpu > > > > hotplug. > > > > > > This breaks Xen guests that allocate interrupt descriptors in .cpu_up(). > > And where exactly does XEN allocate those descriptors? > > xen_cpu_up() > xen_setup_timer() > bind_virq_to_irqhandler() > bind_virq_to_irq() > xen_allocate_irq_dynamic() > xen_allocate_irqs_dynamic() > irq_alloc_descs() > > > There is also a similar pass via xen_cpu_up() -> xen_smp_intr_init() Sigh. > > > > > > Any chance this locking can be moved into arch code? > > No. The issue here is that all architectures need that protection and just Xen does irq allocations in cpu_up. So moving that protection into architecture code is not really an option. > > > Otherwise we will need to have something like arch_post_cpu_up() > > > after the lock is released. I'm not sure, that this will work. You probably want to do this in the cpu prepare stage, i.e. before calling __cpu_up(). I have to walk the dogs now. Will look into it later tonight. > > > (The patch doesn't appear to have any side effects for the down path since > > > Xen > > > guests deallocate descriptors in __cpu_die()). > > Exact place please. > > Whose place? Where descriptors are deallocated? > > __cpu_die() > xen_cpu_die() > xen_teardown_timer() > unbind_from_irqhandler() > unbind_from_irq() > __unbind_from_irq() > xen_free_irq() > irq_free_descs() > free_desc() Right, that's outside the lock held region. Thanks, tglx