kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
* Calling architecture specific headers files?
@ 2015-05-05 14:00 Abhishek Bist
  0 siblings, 0 replies; only message in thread
From: Abhishek Bist @ 2015-05-05 14:00 UTC (permalink / raw)
  To: kernelnewbies

Hi,
   I am searching the way out that how an architecture specific header's file come into existence.For example the
generic defination of spinlock is supposed to call architecture specific spinlock.

(linux/spinlock_types.h)
	typedef struct raw_spinlock {
          arch_spinlock_t raw_lock;			<<<<
 #ifdef CONFIG_GENERIC_LOCKBREAK
         unsigned int break_lock;
 #endif
 #ifdef CONFIG_DEBUG_SPINLOCK
         unsigned int magic, owner_cpu;
         void *owner;
 #endif
 #ifdef CONFIG_DEBUG_LOCK_ALLOC
         struct lockdep_map dep_map;
 #endif
 } raw_spinlock_t;


(x86/include/asm/spinlock_types.h)
typedef struct arch_spinlock {
        union {
                __ticketpair_t head_tail;
                struct __raw_tickets {
                       __ticket_t head, tail;
                } tickets;
        };
} arch_spinlock_t;

what is there which makes to load the architecture specific spinlock (x86) in my case.

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2015-05-05 14:00 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-05-05 14:00 Calling architecture specific headers files? Abhishek Bist

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).