kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: William Tambe <tambewilliam@gmail.com>
Cc: CVS <cvs268@gmail.com>, Kernel Newbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Regarding Linux kernel SMP and task switching CPU
Date: Mon, 13 Jul 2020 00:20:54 -0400	[thread overview]
Message-ID: <354833.1594614054@turing-police> (raw)
In-Reply-To: <CAF8i9mNeJoF0WwU0MYJZYcDUuxxFHqAq4HS-24BEPK35XZWHkw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 679 bytes --]

On Sun, 12 Jul 2020 12:24:46 -0400, William Tambe said:
> On Sun, Jul 12, 2020 at 7:00 AM CVS <cvs268@gmail.com> wrote:
> >
> > > are there platform specific functions that are called to detect change ?
> > What is it that you wish to do with this?
>
> I am doing porting work; I would like to be able to update
> mm_struct->context when a task migrates to another CPU.

That shouldn't be a big issue - there should already be architecture
independent code that calls a function to do this sort of thing on task
migration, and all you have to do is provide a "Here's how the actual update is
done on the Wombat architecture" function in the appropriate place in the arch/
tree.


[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

      parent reply	other threads:[~2020-07-13  4:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-09 11:01 Regarding Linux kernel SMP and task switching CPU William Tambe
2020-07-12 11:00 ` CVS
2020-07-12 16:24   ` William Tambe
2020-07-12 17:00     ` CVS
2020-07-13  4:20     ` Valdis Klētnieks [this message]

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=354833.1594614054@turing-police \
    --to=valdis.kletnieks@vt.edu \
    --cc=cvs268@gmail.com \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=tambewilliam@gmail.com \
    /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).