All of lore.kernel.org
 help / color / mirror / Atom feed
From: mathew.li100@gmail.com (Mathew Li)
To: linux-arm-kernel@lists.infradead.org
Subject: Some SMP related questions
Date: Mon, 9 Jun 2014 11:44:29 -0700	[thread overview]
Message-ID: <CALU2kfkrpoSSpRB-XGeKS5DOGRCKapRT_qhZW+u4MOsviOx3QQ@mail.gmail.com> (raw)

Hi,

Just trying to understand SMP arm Linux. I have following questions:

1. On any ARM board, all the devices raise SPIs. Is that correct?
2. On an SMP system, how does Linux configure SPIs? I mean the routing
of the interrupts. For example, when a device raises an interrupt,
does it get seen by all the cpus or is it seen only by the boot cpu,
who handles the interrupt eventually if it is seen by all the cpus?
Could you also please point me to the code?
3. On an SMP system, how does Linux do scheduling? What is used for
scheduling, I believe it is the timer interrupt. Right? Is timer
device and its interrupt private to the cpu or is it also global? If
global then which cpu gets to serve the timer interrupt?
4. In an SMP system, is it possible to run a process on a given cpu
and never schedule it out until the process itself makes some blocking
call, leading to a call into schedule() in kernel? Essentially I am
saying to assign infinite time quantum to the process and only
schedule it out when it does a blocking call.
5. Is it possible to configure and build linux in an ASMP way? For
example, so that whole kernel logic runs on boot cpu and remaining
cpus would be used only and only for processes?

Thanks a lot in advance!
Mathew

             reply	other threads:[~2014-06-09 18:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-09 18:44 Mathew Li [this message]
2014-06-09 19:39 ` Some SMP related questions Russell King - ARM Linux

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=CALU2kfkrpoSSpRB-XGeKS5DOGRCKapRT_qhZW+u4MOsviOx3QQ@mail.gmail.com \
    --to=mathew.li100@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.