From: Nicholas Piggin <npiggin@gmail.com> To: linuxppc-dev@lists.ozlabs.org Cc: Nicholas Piggin <npiggin@gmail.com>, Will Deacon <will@kernel.org>, Peter Zijlstra <peterz@infradead.org>, Boqun Feng <boqun.feng@gmail.com>, Michael Ellerman <mpe@ellerman.id.au>, Arnd Bergmann <arnd@arndb.de>, Christophe Leroy <christophe.leroy@c-s.fr>, Alexey Kardashevskiy <aik@ozlabs.ru>, linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org Subject: [PATCH 2/3] powerpc/64s/iommu: don't use atomic_ function on atomic64_t type Date: Wed, 11 Nov 2020 21:07:22 +1000 [thread overview] Message-ID: <20201111110723.3148665-3-npiggin@gmail.com> (raw) In-Reply-To: <20201111110723.3148665-1-npiggin@gmail.com> Signed-off-by: Nicholas Piggin <npiggin@gmail.com> --- arch/powerpc/mm/book3s64/iommu_api.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/powerpc/mm/book3s64/iommu_api.c b/arch/powerpc/mm/book3s64/iommu_api.c index 563faa10bb66..685d7bb3d26f 100644 --- a/arch/powerpc/mm/book3s64/iommu_api.c +++ b/arch/powerpc/mm/book3s64/iommu_api.c @@ -263,7 +263,7 @@ long mm_iommu_put(struct mm_struct *mm, struct mm_iommu_table_group_mem_t *mem) goto unlock_exit; /* Are there still mappings? */ - if (atomic_cmpxchg(&mem->mapped, 1, 0) != 1) { + if (atomic64_cmpxchg(&mem->mapped, 1, 0) != 1) { ++mem->used; ret = -EBUSY; goto unlock_exit; -- 2.23.0
WARNING: multiple messages have this Message-ID (diff)
From: Nicholas Piggin <npiggin@gmail.com> To: linuxppc-dev@lists.ozlabs.org Cc: Christophe Leroy <christophe.leroy@c-s.fr>, linux-arch@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>, Peter Zijlstra <peterz@infradead.org>, Boqun Feng <boqun.feng@gmail.com>, linux-kernel@vger.kernel.org, Nicholas Piggin <npiggin@gmail.com>, Alexey Kardashevskiy <aik@ozlabs.ru>, Will Deacon <will@kernel.org> Subject: [PATCH 2/3] powerpc/64s/iommu: don't use atomic_ function on atomic64_t type Date: Wed, 11 Nov 2020 21:07:22 +1000 [thread overview] Message-ID: <20201111110723.3148665-3-npiggin@gmail.com> (raw) In-Reply-To: <20201111110723.3148665-1-npiggin@gmail.com> Signed-off-by: Nicholas Piggin <npiggin@gmail.com> --- arch/powerpc/mm/book3s64/iommu_api.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/powerpc/mm/book3s64/iommu_api.c b/arch/powerpc/mm/book3s64/iommu_api.c index 563faa10bb66..685d7bb3d26f 100644 --- a/arch/powerpc/mm/book3s64/iommu_api.c +++ b/arch/powerpc/mm/book3s64/iommu_api.c @@ -263,7 +263,7 @@ long mm_iommu_put(struct mm_struct *mm, struct mm_iommu_table_group_mem_t *mem) goto unlock_exit; /* Are there still mappings? */ - if (atomic_cmpxchg(&mem->mapped, 1, 0) != 1) { + if (atomic64_cmpxchg(&mem->mapped, 1, 0) != 1) { ++mem->used; ret = -EBUSY; goto unlock_exit; -- 2.23.0
next prev parent reply other threads:[~2020-11-11 11:07 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-11 11:07 [PATCH 0/3] powerpc: convert to use ARCH_ATOMIC Nicholas Piggin 2020-11-11 11:07 ` Nicholas Piggin 2020-11-11 11:07 ` [PATCH 1/3] asm-generic/atomic64: Add support for ARCH_ATOMIC Nicholas Piggin 2020-11-11 11:07 ` Nicholas Piggin 2020-11-11 13:39 ` Christophe Leroy 2020-11-11 13:39 ` Christophe Leroy 2020-11-11 13:44 ` Peter Zijlstra 2020-11-11 13:44 ` Peter Zijlstra 2020-11-16 1:48 ` Nicholas Piggin 2020-11-16 1:48 ` Nicholas Piggin 2020-11-11 11:07 ` Nicholas Piggin [this message] 2020-11-11 11:07 ` [PATCH 2/3] powerpc/64s/iommu: don't use atomic_ function on atomic64_t type Nicholas Piggin 2020-11-11 11:07 ` [PATCH 3/3] powerpc: rewrite atomics to use ARCH_ATOMIC Nicholas Piggin 2020-11-11 11:07 ` Nicholas Piggin 2020-11-11 19:07 ` kernel test robot 2020-11-11 19:07 ` kernel test robot 2020-11-11 19:07 ` kernel test robot 2020-11-13 5:05 ` kernel test robot 2020-11-13 5:05 ` kernel test robot 2020-11-13 5:05 ` kernel test robot 2020-11-13 15:30 ` Boqun Feng 2020-11-13 15:30 ` Boqun Feng 2020-12-22 3:52 ` Nicholas Piggin 2020-12-22 3:52 ` Nicholas Piggin 2020-12-23 2:45 ` Boqun Feng 2020-12-23 2:45 ` Boqun Feng 2020-12-15 11:01 ` [PATCH 0/3] powerpc: convert " Michael Ellerman 2020-12-15 11:01 ` Michael Ellerman
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=20201111110723.3148665-3-npiggin@gmail.com \ --to=npiggin@gmail.com \ --cc=aik@ozlabs.ru \ --cc=arnd@arndb.de \ --cc=boqun.feng@gmail.com \ --cc=christophe.leroy@c-s.fr \ --cc=linux-arch@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linuxppc-dev@lists.ozlabs.org \ --cc=mpe@ellerman.id.au \ --cc=peterz@infradead.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.