From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 56CBEC433E1 for ; Sun, 12 Jul 2020 16:25:58 +0000 (UTC) Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 04A69206F4 for ; Sun, 12 Jul 2020 16:25:57 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="WdYj7TIr" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 04A69206F4 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kernelnewbies-bounces@kernelnewbies.org Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.94) (envelope-from ) id 1juemm-0002sM-H0; Sun, 12 Jul 2020 12:25:04 -0400 Received: from mail-lf1-x129.google.com ([2a00:1450:4864:20::129]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94) (envelope-from ) id 1juemj-0002rn-HT for kernelnewbies@kernelnewbies.org; Sun, 12 Jul 2020 12:25:01 -0400 Received: by mail-lf1-x129.google.com with SMTP id t74so6017981lff.2 for ; Sun, 12 Jul 2020 09:25:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=XBTqQlfNpY2veT/ot9/xraH2pixyjyujDvHrQkfPbgk=; b=WdYj7TIrmp81vE4lLJF+K++DU4+VpbB6dhSH5YfogOspdSzOqiuoequsQ4rQnWWuMV eqgtuKRrtqUEMhi0txKSzRxor++NXWaVOkFfdAcHCOj6NZwheKDNhi97swd/+cl7C1hZ 3kK1pgdqpq2jlFJ6eXLlVlZnPxdlMVGMcp/mn+BjyG+klzY7lDC3eFm2hHd5nmZtP5QE xTVUzmfJrV3CdSw4BPSCdq4sWAgzFrwxuglMK2SLoR2NoE4e6ErnfLnBYTtAcVDq8uWE jhWP99T9e4h5DP12WFhzX4I9nbJteELAIh0vML5AoNqKGPQ5bC0a3gjRkZOmxmApOoa3 ZLVQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=XBTqQlfNpY2veT/ot9/xraH2pixyjyujDvHrQkfPbgk=; b=c2v57JRwkSc7HZXPdzqrfhcLPXfT6CH8eW+6vO/JI2kChkAfcfLLirs6ADjMp+qDE7 C5yeMQYDT+JhV7zH2/H/oYu3f8pYwPAfpOXHCkqWmF3gGRhkwQhGQ3gfV8/IAz2h31YY HdOZN5t/XV+OaQeczWoX8PoGzutlAbpwjR8IEfJDbChHBkdGHTZXhLEzZtA0VLv36ozi bxvUIpirONYHdak3CR/CnUEkIQGA9SopRkdV2NSt3Uk8rBsrqykcdJ33NeZ6P/4UC6mk cC7qcfmURfSVSqPiCeiA0kZIrMA6aO5JYQkI5f8b+gHLmpcAoCERdDL+jac5lkVvd5/9 VuZw== X-Gm-Message-State: AOAM532M9AXkVIeAYZ+cN7s3R4YBIINsB6GHBK4hzhkCdbmEeZD/+i+5 KU9Nwr5itU+QloI/eSxxXRq7Yazh/lxQDMw5L10= X-Google-Smtp-Source: ABdhPJyeuCFRNB8FwrHCRoDrQu8ztQX+Vjcvt6LLRR8dvE7J5x1DBy9rZAXxZ/nY0dAr6KZ0SDVBqx2/0CnGCkNNsHk= X-Received: by 2002:a05:6512:2154:: with SMTP id s20mr18475208lfr.139.1594571098304; Sun, 12 Jul 2020 09:24:58 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: William Tambe Date: Sun, 12 Jul 2020 12:24:46 -0400 Message-ID: Subject: Re: Regarding Linux kernel SMP and task switching CPU To: CVS Cc: Kernel Newbies X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kernelnewbies-bounces@kernelnewbies.org On Sun, Jul 12, 2020 at 7:00 AM CVS 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. Another related question to this topic is: can the same mm_struct be used by two tasks running each on a different CPU ? if yes, I would probably need to make mm_struct->context an array so that it can hold information for each CPU. > > - Are you thinking of modifying the thread migration logic before a > thread is migrated? > - Are you looking to trace such thread migrations across CPUs after they happen? > - Something else?... > > regards > CVS _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies