From: "levi.yun" <yeoreum.yun@arm.com>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Catalin Marinas <Catalin.Marinas@arm.com>,
Mark Rutland <Mark.Rutland@arm.com>,
Will Deacon <will@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Aaron Lu <aaron.lu@intel.com>
Subject: Re: [RFC PATCH] sched: Add missing memory barrier in switch_mm_cid
Date: Wed, 13 Mar 2024 08:37:52 +0000 [thread overview]
Message-ID: <8cd9b873-d9f8-49cb-89e0-e59f61dc5c8c@arm.com> (raw)
In-Reply-To: <b7660de7-03ad-4d6c-b135-998d2cc0c80e@efficios.com>
index 35389b2af88e..0d5e54201eb2 100644
>>> --- a/arch/x86/include/asm/barrier.h
>>> +++ b/arch/x86/include/asm/barrier.h
>>> @@ -79,6 +79,9 @@ do { \
>>> #define __smp_mb__before_atomic() do { } while (0)
>>> #define __smp_mb__after_atomic() do { } while (0)
>>
>>> +/* Writing to CR3 provides a full memory barrier in switch_mm(). */
>>> +#define smp_mb__after_switch_mm() do { } while (0)
>>> +
>>> #include <asm-generic/barrier.h>
>>
>> IIUC, ppc already does smp_mb() in switch_mm.
>>
>> Would it better to add the same macro which do nothing to pcc?\\
>
> Does it ?
>
Sorry. I made a mistake.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
prev parent reply other threads:[~2024-03-13 8:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 15:24 Mathieu Desnoyers
2024-03-11 8:45 ` Yeo Reum Yun
2024-03-12 18:07 ` Mathieu Desnoyers
2024-03-13 8:37 ` levi.yun [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=8cd9b873-d9f8-49cb-89e0-e59f61dc5c8c@arm.com \
--to=yeoreum.yun@arm.com \
--cc=Catalin.Marinas@arm.com \
--cc=Mark.Rutland@arm.com \
--cc=aaron.lu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.org \
--cc=will@kernel.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
all inboxes | Powered by JetHome®