Andrew Morton wrote:
>> On Fri, 7 Sep 2007 08:28:05 +0100 Andi Kleen <[EMAIL PROTECTED]> wrote:
>> On Friday 07 September 2007 05:09, [EMAIL PROTECTED] wrote:
>>> Since the core kernel routines need to reference cpu_sibling_map,
>>> whether it be a static array or a per_cpu data variable, an
Andi Kleen wrote:
> On Friday 07 September 2007 05:09, [EMAIL PROTECTED] wrote:
>> Since the core kernel routines need to reference cpu_sibling_map,
>> whether it be a static array or a per_cpu data variable, an access
>> function has been defined.
>>
>> In addition, changes have been made to the
> On Fri, 7 Sep 2007 08:28:05 +0100 Andi Kleen <[EMAIL PROTECTED]> wrote:
> On Friday 07 September 2007 05:09, [EMAIL PROTECTED] wrote:
> > Since the core kernel routines need to reference cpu_sibling_map,
> > whether it be a static array or a per_cpu data variable, an access
> > function has been
On Friday 07 September 2007 05:09, [EMAIL PROTECTED] wrote:
> Since the core kernel routines need to reference cpu_sibling_map,
> whether it be a static array or a per_cpu data variable, an access
> function has been defined.
>
> In addition, changes have been made to the ia64 and ppc64 arch's to
On Friday 07 September 2007 05:09, [EMAIL PROTECTED] wrote:
Since the core kernel routines need to reference cpu_sibling_map,
whether it be a static array or a per_cpu data variable, an access
function has been defined.
In addition, changes have been made to the ia64 and ppc64 arch's to
move
On Fri, 7 Sep 2007 08:28:05 +0100 Andi Kleen [EMAIL PROTECTED] wrote:
On Friday 07 September 2007 05:09, [EMAIL PROTECTED] wrote:
Since the core kernel routines need to reference cpu_sibling_map,
whether it be a static array or a per_cpu data variable, an access
function has been defined.
Andrew Morton wrote:
On Fri, 7 Sep 2007 08:28:05 +0100 Andi Kleen [EMAIL PROTECTED] wrote:
On Friday 07 September 2007 05:09, [EMAIL PROTECTED] wrote:
Since the core kernel routines need to reference cpu_sibling_map,
whether it be a static array or a per_cpu data variable, an access
function
Andi Kleen wrote:
On Friday 07 September 2007 05:09, [EMAIL PROTECTED] wrote:
Since the core kernel routines need to reference cpu_sibling_map,
whether it be a static array or a per_cpu data variable, an access
function has been defined.
In addition, changes have been made to the ia64 and
Since the core kernel routines need to reference cpu_sibling_map,
whether it be a static array or a per_cpu data variable, an access
function has been defined.
In addition, changes have been made to the ia64 and ppc64 arch's to
move the cpu_sibling_map from a static cpumask_t array [NR_CPUS] to
Since the core kernel routines need to reference cpu_sibling_map,
whether it be a static array or a per_cpu data variable, an access
function has been defined.
In addition, changes have been made to the ia64 and ppc64 arch's to
move the cpu_sibling_map from a static cpumask_t array [NR_CPUS] to
10 matches
Mail list logo