On Wed, Feb 06, 2008 at 09:13:33AM -0600, Russ Anderson wrote:
> On Tue, Feb 05, 2008 at 04:00:09PM -0800, Luck, Tony wrote:
> > > Given that ia64_mca_cpu_init() does not get called in
> > > the hot-plug path
> >
> > Surely it must be ...
>
> That's what I thought, until testing showed otherwise.
> Any reason the various ptrace bits are not included in this pull?
The ptrace bits depend upon some generic changes to add arch_ptrace_stop()
... I think Andrew included them as part 89/260 of today's early
morning mail patch bomb.
-Tony
-
To unsubscribe from this list: send the line "unsubscri
On Tuesday 05 February 2008 07:03:23 pm Carlos Corbacho wrote:
> On Wednesday 06 February 2008 00:35:54 Bjorn Helgaas wrote:
> > > Ok. The only other vendors I really have in mind are HP and Fujitsu,
> > > since both those vendors use WMI on their laptops, so they would be my
> > > most likely cand
On Tue, Feb 05, 2008 at 04:00:09PM -0800, Luck, Tony wrote:
> > Given that ia64_mca_cpu_init() does not get called in
> > the hot-plug path
>
> Surely it must be ...
That's what I thought, until testing showed otherwise.
The two code paths are setup_arch->cpu_init->ia64_mca_cpu_init
for the boot
On Wed, Feb 06, 2008 at 09:39:42PM +0900, Hidetoshi Seto wrote:
> Robin Holt wrote:
> Which other stuff in the cpu_init path would cause a panic on hot-added
> CPU?
I had not looked. I was going off what Tony Luck had said earlier.
Thanks,
Robin
-
To unsubscribe from this list: send the line "u
Hello Tony,
Thank you for review.
Luck, Tony wrote:
> +/* Insert a long branch code */
> +static void __kprobes set_brl_inst(void *from, void *to)
> +{
> + s64 rel = ((s64) to - (s64) from) >> 4;
> + bundle_t *brl;
> + brl = (bundle_t *) ((u64) from & ~0xf);
> + brl->quad0.template
Robin Holt wrote:
On Wed, Feb 06, 2008 at 12:50:11PM +0900, Hidetoshi Seto wrote:
Hidetoshi Seto wrote:
Then, I suppose we need a CPU_UP_PREPARE callback to allocate memory
before hot-added CPU enters cpu_init().
Ah, we cannot allocate bootmem later, so it would be better to make
the callback
On Wed, Feb 06, 2008 at 12:50:11PM +0900, Hidetoshi Seto wrote:
> Hidetoshi Seto wrote:
>> Then, I suppose we need a CPU_UP_PREPARE callback to allocate memory
>> before hot-added CPU enters cpu_init().
>
> Ah, we cannot allocate bootmem later, so it would be better to make
> the callback to return
