From: Nadav Amit <namit@vmware.com>
To: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Andy Lutomirski <luto@kernel.org>
Cc: Borislav Petkov <bp@alien8.de>,
linux-kernel@vger.kernel.org, Nadav Amit <namit@vmware.com>,
"David S. Miller" <davem@davemloft.net>
Subject: [RFC PATCH 2/6] cpumask: Purify cpumask_next()
Date: Sat, 25 May 2019 01:21:59 -0700 [thread overview]
Message-ID: <20190525082203.6531-3-namit@vmware.com> (raw)
In-Reply-To: <20190525082203.6531-1-namit@vmware.com>
cpumask_next() has no side-effects. Mark it as pure.
Cc: "David S. Miller" <davem@davemloft.net>
Signed-off-by: Nadav Amit <namit@vmware.com>
---
include/linux/cpumask.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/cpumask.h b/include/linux/cpumask.h
index 147bdec42215..20df46705f9c 100644
--- a/include/linux/cpumask.h
+++ b/include/linux/cpumask.h
@@ -209,7 +209,7 @@ static inline unsigned int cpumask_last(const struct cpumask *srcp)
return find_last_bit(cpumask_bits(srcp), nr_cpumask_bits);
}
-unsigned int cpumask_next(int n, const struct cpumask *srcp);
+unsigned int __pure cpumask_next(int n, const struct cpumask *srcp);
/**
* cpumask_next_zero - get the next unset cpu in a cpumask
--
2.20.1
next prev parent reply other threads:[~2019-05-25 8:22 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-25 8:21 [RFC PATCH 0/6] x86/mm: Flush remote and local TLBs concurrently Nadav Amit
2019-05-25 8:21 ` [RFC PATCH 1/6] smp: Remove smp_call_function() and on_each_cpu() return values Nadav Amit
2019-05-25 8:21 ` Nadav Amit [this message]
2019-05-25 8:32 ` [RFC PATCH 2/6] cpumask: Purify cpumask_next() Ingo Molnar
2019-05-27 8:30 ` Peter Zijlstra
2019-05-27 17:34 ` Nadav Amit
2019-05-25 8:22 ` [RFC PATCH 3/6] smp: Run functions concurrently in smp_call_function_many() Nadav Amit
2019-05-27 9:15 ` Peter Zijlstra
2019-05-27 17:39 ` Nadav Amit
2019-05-25 8:22 ` [RFC PATCH 4/6] x86/mm/tlb: Refactor common code into flush_tlb_on_cpus() Nadav Amit
2019-05-27 9:24 ` Peter Zijlstra
2019-05-27 18:59 ` Nadav Amit
2019-05-27 19:14 ` Peter Zijlstra
2019-05-25 8:22 ` [RFC PATCH 5/6] x86/mm/tlb: Flush remote and local TLBs concurrently Nadav Amit
2019-05-25 8:22 ` Nadav Amit
2019-05-25 8:22 ` [Xen-devel] " Nadav Amit
2019-05-25 8:22 ` Nadav Amit via Virtualization
2019-05-25 8:38 ` Nadav Amit
2019-05-25 8:38 ` [Xen-devel] " Nadav Amit
2019-05-25 8:38 ` Nadav Amit via Virtualization
2019-05-25 8:38 ` Nadav Amit
2019-05-25 8:54 ` Juergen Gross
2019-05-25 8:54 ` [Xen-devel] " Juergen Gross
2019-05-27 9:47 ` Peter Zijlstra
2019-05-27 9:47 ` Peter Zijlstra
2019-05-27 9:47 ` Peter Zijlstra
2019-05-27 9:47 ` [Xen-devel] " Peter Zijlstra
2019-05-27 10:21 ` Paolo Bonzini
2019-05-27 10:21 ` [Xen-devel] " Paolo Bonzini
2019-05-27 12:32 ` Peter Zijlstra
2019-05-27 12:32 ` [Xen-devel] " Peter Zijlstra
2019-05-27 12:32 ` Peter Zijlstra
2019-05-27 12:45 ` Paolo Bonzini
2019-05-27 12:45 ` Paolo Bonzini
2019-05-27 12:45 ` [Xen-devel] " Paolo Bonzini
2019-05-27 12:45 ` Paolo Bonzini
2019-05-27 12:32 ` Peter Zijlstra
2019-05-27 10:21 ` Paolo Bonzini
2019-05-27 10:21 ` Paolo Bonzini
2019-05-27 17:49 ` Nadav Amit via Virtualization
2019-05-27 17:49 ` Nadav Amit
2019-05-27 17:49 ` Nadav Amit
2019-05-27 17:49 ` [Xen-devel] " Nadav Amit
2019-05-25 8:54 ` Juergen Gross
2019-05-25 8:54 ` Juergen Gross
2019-05-25 8:22 ` [RFC PATCH 6/6] x86/mm/tlb: Optimize local TLB flushes Nadav Amit
2019-05-27 8:28 ` [RFC PATCH 0/6] x86/mm: Flush remote and local TLBs concurrently Peter Zijlstra
2019-05-27 9:59 ` Peter Zijlstra
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=20190525082203.6531-3-namit@vmware.com \
--to=namit@vmware.com \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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 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.