In message <[EMAIL PROTECTED]> you write:
> This is not quite right:
>
> @@ -1643,7 +1643,7 @@
> printk(KERN_NOTICE "apm: disabled on user
> request.\n");
> return -ENODEV;
> }
> - if ((smp_num_cpus > 1) && !power_off) {
> + if
Hi!
> I did the infrastructure, Anton did the bugfinding and PPC support,
> aka. the hard stuff. Other architectures need to implement
> __cpu_disable, __cpu_die and __cpu_up for them to work. Volunteers
> appreciated.
>
> This patch allows you to down & up CPUs as follows:
> #
Hi!
I did the infrastructure, Anton did the bugfinding and PPC support,
aka. the hard stuff. Other architectures need to implement
__cpu_disable, __cpu_die and __cpu_up for them to work. Volunteers
appreciated.
This patch allows you to down up CPUs as follows:
# echo 0
In message [EMAIL PROTECTED] you write:
This is not quite right:
@@ -1643,7 +1643,7 @@
printk(KERN_NOTICE "apm: disabled on user
request.\n");
return -ENODEV;
}
- if ((smp_num_cpus 1) !power_off) {
+ if ((num_online_cpus() 1)
> Would any special hardware besides a multi-cpu system be necessarey to
> test this out?
You should be able to run it on any SMP machine assuming you write the
arch specific code (PPC could be used as an example). Of course it isn't
very interesting if the hardware doesn't support hot swap :)
Would any special hardware besides a multi-cpu system be necessarey to
test this out?
You should be able to run it on any SMP machine assuming you write the
arch specific code (PPC could be used as an example). Of course it isn't
very interesting if the hardware doesn't support hot swap :)
Would any special hardware besides a multi-cpu system be necessarey to
test this out?
Matthew Fredrickson
On Mon, Feb 05, 2001 at 03:00:40PM +1100, Rusty Russell wrote:
> Hi all,
>
> I did the infrastructure, Anton did the bugfinding and PPC support,
> aka. the hard stuff. Other
Would any special hardware besides a multi-cpu system be necessarey to
test this out?
Matthew Fredrickson
On Mon, Feb 05, 2001 at 03:00:40PM +1100, Rusty Russell wrote:
Hi all,
I did the infrastructure, Anton did the bugfinding and PPC support,
aka. the hard stuff. Other architectures
In message <[EMAIL PROTECTED]> you write
:
> Hello,
>Which archs still need to implement it? I briefly looked over the patch an
d noticed that it had i386, ppc, mips64, and s390 already there.
PPC is there (kinda hackish, but proof of concept). For the rest, I
don't consider:
> Rusty, what would be needed to "hot-add" CPUs ?
The PPC version at the moment simply locks a cpu in the idle loop
with __cli(); while(1); for cpu down and jumps out of it for cpu up.
Good for testing but not very useful. After talking to paulus we
will use the RTAS cpu stop and cpu start.
On 2001-02-05T15:00:40,
Rusty Russell <[EMAIL PROTECTED]> said:
> I did the infrastructure, Anton did the bugfinding and PPC support,
> aka. the hard stuff. Other architectures need to implement
> __cpu_disable, __cpu_die and __cpu_up for them to work. Volunteers
> appreciated.
Rusty, what
Hello,
Which archs still need to implement it? I briefly looked over the patch and noticed
that it had i386, ppc, mips64, and s390 already there.
Regards,
Frank
>Hi all,
>
>I did the infrastructure, Anton did the bugfinding and PPC >support,
>aka. the hard stuff. Other architectures need to
Hi all,
I did the infrastructure, Anton did the bugfinding and PPC support,
aka. the hard stuff. Other architectures need to implement
__cpu_disable, __cpu_die and __cpu_up for them to work. Volunteers
appreciated.
This patch allows you to down & up CPUs as follows:
# echo 0 >
Hi all,
I did the infrastructure, Anton did the bugfinding and PPC support,
aka. the hard stuff. Other architectures need to implement
__cpu_disable, __cpu_die and __cpu_up for them to work. Volunteers
appreciated.
This patch allows you to down up CPUs as follows:
# echo 0
Hello,
Which archs still need to implement it? I briefly looked over the patch and noticed
that it had i386, ppc, mips64, and s390 already there.
Regards,
Frank
Hi all,
I did the infrastructure, Anton did the bugfinding and PPC support,
aka. the hard stuff. Other architectures need to
Rusty, what would be needed to "hot-add" CPUs ?
The PPC version at the moment simply locks a cpu in the idle loop
with __cli(); while(1); for cpu down and jumps out of it for cpu up.
Good for testing but not very useful. After talking to paulus we
will use the RTAS cpu stop and cpu start.
In
In message [EMAIL PROTECTED] you write
:
Hello,
Which archs still need to implement it? I briefly looked over the patch an
d noticed that it had i386, ppc, mips64, and s390 already there.
PPC is there (kinda hackish, but proof of concept). For the rest, I
don't consider:
return
17 matches
Mail list logo
