[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1366909184.3142.0.camel@zakaz.uk.xensource.com>
Date: Thu, 25 Apr 2013 17:59:44 +0100
From: Ian Campbell <Ian.Campbell@...rix.com>
To: Stefano Stabellini <stefano.stabellini@...citrix.com>
CC: "xen-devel@...ts.xensource.com" <xen-devel@...ts.xensource.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"konrad.wilk@...cle.com" <konrad.wilk@...cle.com>
Subject: Re: [PATCH v4 2/7] xen/arm: SMP support
> > > @@ -216,6 +245,8 @@ static int __init xen_guest_init(void)
> > > * is required to use VCPUOP_register_vcpu_info to place vcpu info
> > > * for secondary CPUs as they are brought up. */
> > > per_cpu(xen_vcpu, 0) = &HYPERVISOR_shared_info->vcpu_info[0];
> > > + for_each_online_cpu(i)
> > > + xen_secondary_init(i);
> > >
> > > gnttab_init();
> > > if (!xen_initial_domain())
> > [...]
> > > @@ -244,7 +280,7 @@ static int __init xen_init_events(void)
> > > return -EINVAL;
> > > }
> > >
> > > - enable_percpu_irq(xen_events_irq, 0);
> > > + on_each_cpu(xen_percpu_enable_events, NULL, 0);
> >
> > It feels like there ought to be some sort of per-cpu bringup callback
> > which takes care of these dynamically. Maybe that doesn't matter until
> > we get vcpu hotplug going?
>
> I suspect there isn't one, considering that on_each_cpu is also used by
> kvm_vgic_hyp_init, kvm_timer_hyp_init and others.
Could we use cpu_notifiers for this?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists