linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] FCSE: pid life cycle.
Date: Sun, 4 Oct 2009 21:02:23 +0200	[thread overview]
Message-ID: <20091004190223.GH1378@ucw.cz> (raw)
In-Reply-To: <1254432860-11511-2-git-send-email-gilles.chanteperdrix@xenomai.org>

On Thu 2009-10-01 23:34:11, Gilles Chanteperdrix wrote:
> Add a pid member to the mm_context_t structure, allocate this pid in
> the init_new_context, free it in the destroy_context, switch it in
> switch_mm.
> 
> A bitfield is maintained to know what pids are currently in use.
> 
> Signed-off-by: Richard Cochran <richard.cochran@omicron.at>
> Signed-off-by: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
...
> --- /dev/null
> +++ b/arch/arm/include/asm/fcse.h
> @@ -0,0 +1,44 @@
> +/*
> + * Filename:    arch/arm/include/asm/fcse.h
> + * Description: ARM Process ID (PID) includes for Fast Address Space Switching
> + *              (FASS) in ARM Linux.
> + * Created:     14/10/2001
> + * Changes:     19/02/2002 - Macros added.
> + *              03/08/2007 - Adapted to kernel 2.6.21 (ssm)
> + *              Feb 2008   - Simplified a bit (rco)

We normally avoid changelogs in sources.

> +/* Sets the CPU's PID Register */
> +static inline void fcse_pid_set(unsigned long pid)
> +{
> +	__asm__ __volatile__ ("mcr p15, 0, %0, c13, c0, 0"
> +			      : /* */: "r" (pid) : "memory");
> +}

Calling this 'pid' is extremely confusing. PID already means process
id...



-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  parent reply	other threads:[~2009-10-04 19:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-01 21:34 [PATCH] FCSE Gilles Chanteperdrix
2009-10-01 21:34 ` [PATCH] FCSE: pid life cycle Gilles Chanteperdrix
2009-10-01 21:34   ` [PATCH] FCSE: Conversions between VA and MVA Gilles Chanteperdrix
2009-10-01 21:34     ` [PATCH] FCSE: Address-space limits Gilles Chanteperdrix
2009-10-01 21:34       ` [PATCH] FCSE: differentiate cpu_tlb_mask from cpu_vm_mask Gilles Chanteperdrix
2009-10-01 21:34         ` [PATCH] FCSE: Make the shared mappings uncacheable Gilles Chanteperdrix
2009-10-01 21:34           ` [PATCH] "Best-effort" FCSE: choose whether to flush cache at run-time Gilles Chanteperdrix
2009-10-01 21:34             ` [PATCH] "Best-effort" FCSE: Allow PID re-use Gilles Chanteperdrix
2009-10-01 21:34               ` [PATCH] "Best-effort" FCSE: Handle shared mappings Gilles Chanteperdrix
2009-10-01 21:34                 ` [PATCH] "Best-effort" FCSE: Handle mappings above 32 MB Gilles Chanteperdrix
2009-10-01 21:34                   ` [PATCH] FCSE: add Makefile and compilation option Gilles Chanteperdrix
2009-10-04 19:02   ` Pavel Machek [this message]
2009-10-04 19:25     ` [PATCH] FCSE: pid life cycle Gilles Chanteperdrix

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=20091004190223.GH1378@ucw.cz \
    --to=pavel@ucw.cz \
    --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 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).