From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: linuxppc-dev@lists.ozlabs.org
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>, Alexander Graf <agraf@suse.de>,
kvm@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, kvm-ppc@vger.kernel.org
Subject: [PATCH 01/10] hashtable: add hash_for_each_possible_rcu_notrace()
Date: Thu, 1 Aug 2013 14:44:23 +1000 [thread overview]
Message-ID: <1375332272-22176-2-git-send-email-aik@ozlabs.ru> (raw)
In-Reply-To: <1375332272-22176-1-git-send-email-aik@ozlabs.ru>
This adds hash_for_each_possible_rcu_notrace() which is basically
a notrace clone of hash_for_each_possible_rcu() which cannot be
used in real mode due to its tracing/debugging capability.
Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
---
include/linux/hashtable.h | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/include/linux/hashtable.h b/include/linux/hashtable.h
index a9df51f..af8b169 100644
--- a/include/linux/hashtable.h
+++ b/include/linux/hashtable.h
@@ -174,6 +174,21 @@ static inline void hash_del_rcu(struct hlist_node *node)
member)
/**
+ * hash_for_each_possible_rcu_notrace - iterate over all possible objects hashing
+ * to the same bucket in an rcu enabled hashtable in a rcu enabled hashtable
+ * @name: hashtable to iterate
+ * @obj: the type * to use as a loop cursor for each entry
+ * @member: the name of the hlist_node within the struct
+ * @key: the key of the objects to iterate over
+ *
+ * This is the same as hash_for_each_possible_rcu() except that it does
+ * not do any RCU debugging or tracing.
+ */
+#define hash_for_each_possible_rcu_notrace(name, obj, member, key) \
+ hlist_for_each_entry_rcu_notrace(obj, &name[hash_min(key, HASH_BITS(name))],\
+ member)
+
+/**
* hash_for_each_possible_safe - iterate over all possible objects hashing to the
* same bucket safe against removals
* @name: hashtable to iterate
--
1.8.3.2
next prev parent reply other threads:[~2013-08-01 4:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 4:44 [PATCH 00/10 v7] KVM: PPC: IOMMU in-kernel handling Alexey Kardashevskiy
2013-08-01 4:44 ` Alexey Kardashevskiy [this message]
2013-08-01 4:44 ` [PATCH 02/10] KVM: PPC: reserve a capability number for multitce support Alexey Kardashevskiy
2013-08-14 0:51 ` Benjamin Herrenschmidt
2013-08-26 12:37 ` Gleb Natapov
2013-08-27 4:19 ` Benjamin Herrenschmidt
2013-08-27 4:22 ` Benjamin Herrenschmidt
2013-08-27 6:41 ` Gleb Natapov
2013-08-27 7:35 ` Benjamin Herrenschmidt
2013-08-27 6:40 ` Gleb Natapov
2013-08-27 7:34 ` Benjamin Herrenschmidt
2013-08-01 4:44 ` [PATCH 03/10] KVM: PPC: reserve a capability and ioctl numbers for realmode VFIO Alexey Kardashevskiy
2013-08-15 7:16 ` Alexander Graf
2013-08-15 7:22 ` Alexey Kardashevskiy
2013-08-15 7:24 ` Alexander Graf
2013-08-15 7:25 ` Alexander Graf
2013-08-15 7:42 ` Alexey Kardashevskiy
2013-08-15 7:43 ` Alexander Graf
2013-08-15 7:54 ` Alexey Kardashevskiy
2013-08-15 7:56 ` Alexander Graf
2013-08-01 4:44 ` [PATCH 04/10] powerpc: Prepare to support kernel handling of IOMMU map/unmap Alexey Kardashevskiy
2013-08-01 4:44 ` [PATCH 05/10] powerpc: add real mode support for dma operations on powernv Alexey Kardashevskiy
2013-08-01 4:44 ` [PATCH 06/10] KVM: PPC: enable IOMMU_API for KVM_BOOK3S_64 permanently Alexey Kardashevskiy
2013-08-01 4:44 ` [PATCH 07/10] KVM: PPC: Add support for multiple-TCE hcalls Alexey Kardashevskiy
2013-08-01 4:44 ` [PATCH 08/10] powerpc/iommu: rework to support realmode Alexey Kardashevskiy
2013-08-01 4:44 ` [PATCH 09/10] KVM: PPC: Add support for IOMMU in-kernel handling Alexey Kardashevskiy
2013-08-01 4:44 ` [PATCH 10/10] KVM: PPC: Add hugepage " Alexey Kardashevskiy
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=1375332272-22176-2-git-send-email-aik@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=agraf@suse.de \
--cc=benh@kernel.crashing.org \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).