kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: ishubist@gmail.com (Abhishek Bist)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Calling architecture specific headers files?
Date: Tue, 5 May 2015 19:30:11 +0530	[thread overview]
Message-ID: <20150505140011.GA17361@localhost.localdomain> (raw)

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.

                 reply	other threads:[~2015-05-05 14:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150505140011.GA17361@localhost.localdomain \
    --to=ishubist@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).