search for: phys_cpu

...to > do the pinning and call the user function by itself depending on the > environment (pinning supported)? Yeah, uhmm.. not sure on the details; my brain is having a hard time engaging this morning. Maybe just make the vpin thing an option like: smp_call_on_cpu(int (*func)(void *), int phys_cpu); Also; is something like the vpin thing possible on KVM? because if we're going to expose it to generic code like this we had maybe look at wider support.

...to > do the pinning and call the user function by itself depending on the > environment (pinning supported)? Yeah, uhmm.. not sure on the details; my brain is having a hard time engaging this morning. Maybe just make the vpin thing an option like: smp_call_on_cpu(int (*func)(void *), int phys_cpu); Also; is something like the vpin thing possible on KVM? because if we're going to expose it to generic code like this we had maybe look at wider support.

On Fri, Apr 01, 2016 at 11:03:21AM +0200, Juergen Gross wrote: > > Maybe just make the vpin thing an option like: > > > > smp_call_on_cpu(int (*func)(void *), int phys_cpu); > > Also; is something like the vpin thing possible on KVM? because if we're > > going to expose it to generic code like this we had maybe look at wider > > support. > > It is necessary for dom0 under Xen. I don't think there is a need to do > this on KVM as a...

On Fri, Apr 01, 2016 at 11:03:21AM +0200, Juergen Gross wrote: > > Maybe just make the vpin thing an option like: > > > > smp_call_on_cpu(int (*func)(void *), int phys_cpu); > > Also; is something like the vpin thing possible on KVM? because if we're > > going to expose it to generic code like this we had maybe look at wider > > support. > > It is necessary for dom0 under Xen. I don't think there is a need to do > this on KVM as a...

...er function by itself depending on the >> environment (pinning supported)? > > Yeah, uhmm.. not sure on the details; my brain is having a hard time > engaging this morning. > > Maybe just make the vpin thing an option like: > > smp_call_on_cpu(int (*func)(void *), int phys_cpu); Okay. > Also; is something like the vpin thing possible on KVM? because if we're > going to expose it to generic code like this we had maybe look at wider > support. It is necessary for dom0 under Xen. I don't think there is a need to do this on KVM as a guest has no direct ac...

...lt;linux/export.h> > #include <linux/smp.h> > +#include <linux/hypervisor.h> > > int smp_call_function_single(int cpu, void (*func) (void *info), void *info, > int wait) > @@ -85,9 +86,17 @@ EXPORT_SYMBOL(on_each_cpu_cond); > > int smp_call_sync_on_phys_cpu(unsigned int cpu, int (*func)(void *), void *par) > { > + int ret; > + > if (cpu != 0) > return -EINVAL; > > - return func(par); > + preempt_disable(); > + hypervisor_pin_vcpu(0); > + ret = func(par); > + hypervisor_pin_vcpu(-1); > + preempt_enable(); &gt...

...lt;linux/export.h> > #include <linux/smp.h> > +#include <linux/hypervisor.h> > > int smp_call_function_single(int cpu, void (*func) (void *info), void *info, > int wait) > @@ -85,9 +86,17 @@ EXPORT_SYMBOL(on_each_cpu_cond); > > int smp_call_sync_on_phys_cpu(unsigned int cpu, int (*func)(void *), void *par) > { > + int ret; > + > if (cpu != 0) > return -EINVAL; > > - return func(par); > + preempt_disable(); > + hypervisor_pin_vcpu(0); > + ret = func(par); > + hypervisor_pin_vcpu(-1); > + preempt_enable(); &gt...

...ion_table[MAX_MPC_ENTRY] __initdata; - /* Return xen''s logical cpu_id of the new added cpu or <0 if error */ static int __devinit MP_processor_info_x(struct mpc_config_processor *m, - u32 apicidx) + u32 apicidx, bool_t hotplug) { int ver, apicid, cpu = 0; physid_mask_t phys_cpu; @@ -108,55 +93,7 @@ static int __devinit MP_processor_info_x if (!(m->mpc_cpuflag & CPU_ENABLED)) return -EINVAL; - apicid = mpc_apic_id(m, apicidx, translation_table[mpc_record]); - - if (m->mpc_featureflag&(1<<0)) - Dprintk(" Floating point unit present.\n&quo...