Re: [RFC, patch] i386: vgetcpu(), take 2

Chuck Ebbert <[email protected]> writes:

> Use a GDT entry's limit field to store per-cpu data for fast access
> from userspace, and provide a vsyscall to access the current CPU
> number stored there.

Just the CPU alone is useless - you want at least the node too in many
cases. Best you use the prototype I proposed earlier for x86-64.

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [RFC, patch] i386: vgetcpu(), take 2
    • From: Rohit Seth <[email protected]>
  • Re: [RFC, patch] i386: vgetcpu(), take 2
    • From: Ingo Molnar <[email protected]>

• References:
  • [RFC, patch] i386: vgetcpu(), take 2
    • From: Chuck Ebbert <[email protected]>

• Prev by Date: Re: [patch] i386: halt the CPU on serious errors
• Next by Date: Re: [Lse-tech] [PATCH 00/11] Task watchers: Introduction
• Previous by thread: Re: [RFC, patch] i386: vgetcpu(), take 2
• Next by thread: Re: [RFC, patch] i386: vgetcpu(), take 2
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]