From: "Radim Krčmář" <rkrcmar@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: kvm@vger.kernel.org, Joerg Roedel <joro@8bytes.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Dmitry Vyukov <dvyukov@google.com>
Subject: Re: [PATCH] KVM: svm: inititalize hash table structures directly
Date: Tue, 14 Feb 2017 16:56:56 +0100 [thread overview]
Message-ID: <20170214155655.GA8156@potion> (raw)
In-Reply-To: <20170124212116.4568-1-david@redhat.com>
2017-01-24 22:21+0100, David Hildenbrand:
> The hashtable and guarding spinlock are global data structures,
> we can inititalize them statically.
>
> Signed-off-by: David Hildenbrand <david@redhat.com>
> ---
Reviewed-by: Radim Krčmář <rkrcmar@redhat.com>
> arch/x86/kvm/svm.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
> index 08a4d3a..222b3be 100644
> --- a/arch/x86/kvm/svm.c
> +++ b/arch/x86/kvm/svm.c
> @@ -971,8 +971,8 @@ static void svm_disable_lbrv(struct vcpu_svm *svm)
> * a particular vCPU.
> */
> #define SVM_VM_DATA_HASH_BITS 8
> -DECLARE_HASHTABLE(svm_vm_data_hash, SVM_VM_DATA_HASH_BITS);
> -static spinlock_t svm_vm_data_hash_lock;
> +static DEFINE_HASHTABLE(svm_vm_data_hash, SVM_VM_DATA_HASH_BITS);
> +static DEFINE_SPINLOCK(svm_vm_data_hash_lock);
>
> /* Note:
> * This function is called from IOMMU driver to notify
> @@ -1077,8 +1077,6 @@ static __init int svm_hardware_setup(void)
> } else {
> pr_info("AVIC enabled\n");
>
> - hash_init(svm_vm_data_hash);
> - spin_lock_init(&svm_vm_data_hash_lock);
> amd_iommu_register_ga_log_notifier(&avic_ga_log_notifier);
> }
> }
> --
> 2.9.3
>
prev parent reply other threads:[~2017-02-14 15:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 21:21 [PATCH] KVM: svm: inititalize hash table structures directly David Hildenbrand
2017-02-14 15:56 ` Radim Krčmář [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=20170214155655.GA8156@potion \
--to=rkrcmar@redhat.com \
--cc=david@redhat.com \
--cc=dvyukov@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
/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