Received: by 2002:a05:6358:e9c4:b0:b2:91dc:71ab with SMTP id hc4csp6560072rwb; Tue, 9 Aug 2022 18:35:46 -0700 (PDT) X-Google-Smtp-Source: AA6agR7/hG+XQbeS+y7bT5bvztcTgrM9Re6QCCJDi2xO1wZgZ5kdoysREYYH+1WAgdi3PN4euSKC X-Received: by 2002:a63:3646:0:b0:41c:f56d:fff6 with SMTP id d67-20020a633646000000b0041cf56dfff6mr19962165pga.475.1660095346604; Tue, 09 Aug 2022 18:35:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1660095346; cv=none; d=google.com; s=arc-20160816; b=DVZgyXov0yFVe2ASalWVewFIVN2EYJHAO4GhTw6lAwhXohEQe9y9As2eKZhNLsEhRp lSkSRZxi5Kdy5KPmhavKClTheApNDzqcU0GDCReAOee9mUtJuj93lAIOHXaiYHcZIfpb /EoQXFztG2cSxqEGr1tMwZyLMV5PXGMK4zEO6Qm2qrTojsoYRqz49Oe6qRB3sZn4dhxJ rewrjJn6nnmu1bq4gR+OuElz2j3X8GzhaKY8ecptMUL7uztCx+apiTScCJ34E6HEKjGN mm/CeINgbe97dHi6FZh3MhijALKHBrMbk6lUE5yDsgMshkRmFXbLwzrIrWVRqefteRDi bh5g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent:message-id:in-reply-to :date:references:subject:cc:to:from:dkim-signature; bh=miP9cihNzcErWJWcmDTEoKnlnDOiFQI22mTMj5CISjw=; b=ZerSaf0z6Rg+oFr45Tw2jx6URmPPD4CPzK5R5YZsiLnpd/d3RQjYTVBFRZIA51xhWr Uq5+sAs6NKwo0RvTU/lU995E/i5yOQrhiukTk5cgmTmWjtKQZvdrPfaG5ARnuxZcEMCA vyWJrlGjrTGUXDCKigzP9uaKTK6L+WldHcFdSuRxcQzEUrhpAvHIprwG8Je7qjawlhNh Ar0jo4P8HRg2axB9UCSPw4CmYZmY72DzN2c256lc3l9MA1ktFjIL5TOsprx4G9fiyXkL jcD41hKJz7DDxzTUDNrGlYtaI6jY6gGy3jVVGDDQmnOOw8KCmwZFvx+69kMUHjLvpHUB shIg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=Dqc5opAp; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id n13-20020a170902e54d00b0016bd79636a5si17602261plf.575.2022.08.09.18.35.32; Tue, 09 Aug 2022 18:35:46 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=Dqc5opAp; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229764AbiHJAyF (ORCPT + 99 others); Tue, 9 Aug 2022 20:54:05 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54468 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229456AbiHJAyD (ORCPT ); Tue, 9 Aug 2022 20:54:03 -0400 Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C68577E802 for ; Tue, 9 Aug 2022 17:54:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1660092842; x=1691628842; h=from:to:cc:subject:references:date:in-reply-to: message-id:mime-version; bh=nItkLIlxJEYz2NOoOOtaYjhZi5bSbXZOnKdSyUbLTIA=; b=Dqc5opApna+ziCix7zfxEA1NyNP6S8gXcSUHHAkz3+xvRpCTpEbDbBEZ JUZPXND66qLYMRzA71NJm4nML5aeFMgBRE8h48Cg4u5z7VJWSUtKiMzy/ dPey/4Y1TCdYXIG2AhINBYL9lxhfEjTq05D49J8rnrJtlipkjrG5seBPD I6z/QuW3txVA41jdxRxdShPf++B/pM3Fh8givQBzNKryQW29DJfInSjD7 CVDENtONZBawN32PIDcNhx2jg5WjX2n8zXe7uCMEi+1HaxxGnMrTUvNZm SsdO8gim6f9ma38T+TxNAnb1Bwax8+ZXDLMx6PBxjDf3vWTtgkXbxQffC w==; X-IronPort-AV: E=McAfee;i="6400,9594,10434"; a="291754526" X-IronPort-AV: E=Sophos;i="5.93,225,1654585200"; d="scan'208";a="291754526" Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Aug 2022 17:54:02 -0700 X-IronPort-AV: E=Sophos;i="5.93,225,1654585200"; d="scan'208";a="581024195" Received: from yhuang6-desk2.sh.intel.com (HELO yhuang6-desk2.ccr.corp.intel.com) ([10.238.208.55]) by orsmga006-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Aug 2022 17:53:58 -0700 From: "Huang, Ying" To: Peter Xu Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, Andrea Arcangeli , David Hildenbrand , Minchan Kim , Andrew Morton , Vlastimil Babka , Nadav Amit , Hugh Dickins , Andi Kleen , "Kirill A . Shutemov" , Christoph Hellwig Subject: Re: [PATCH v2 2/2] mm: Remember young/dirty bit for page migrations References: <20220804203952.53665-1-peterx@redhat.com> <20220804203952.53665-3-peterx@redhat.com> <877d3hhksz.fsf@yhuang6-desk2.ccr.corp.intel.com> Date: Wed, 10 Aug 2022 08:53:49 +0800 In-Reply-To: (Peter Xu's message of "Tue, 9 Aug 2022 13:59:48 -0400") Message-ID: <87wnbggbqa.fsf@yhuang6-desk2.ccr.corp.intel.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=ascii X-Spam-Status: No, score=-5.0 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Peter Xu writes: > On Tue, Aug 09, 2022 at 04:40:12PM +0800, Huang, Ying wrote: [snip] > >> I don't find pte_dirty() is synced to PageDirty() as in >> try_to_migrate_one(). Is it a issue in the original code? > > I think it has? There is: > > /* Set the dirty flag on the folio now the pte is gone. */ > if (pte_dirty(pteval)) > folio_mark_dirty(folio); > Sorry, my original words are confusing. Yes, there's dirty bit syncing in try_to_migrate_one(). But I don't find that in migrate_device.c $ grep dirty mm/migrate_device.c if (pte_soft_dirty(pte)) swp_pte = pte_swp_mksoft_dirty(swp_pte); if (pte_swp_soft_dirty(pte)) swp_pte = pte_swp_mksoft_dirty(swp_pte); entry = pte_mkwrite(pte_mkdirty(entry)); I guess that migrate_device.c is used to migrate between CPU visible page to CPU un-visible page (device visible), so the rule is different? Best Regards, Huang, Ying