mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: shijie001@208suo.com
To: tglx@linutronix.d, mingo@redhat.com, bp@alien8.de,
	dave.hansen@linux.intel.com, x86@kernel.org
Cc: hpa@zytor.com, kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] KVM: x86: Fix warnings in kvm_cache_regs.h
Date: Wed, 12 Jul 2023 14:56:43 +0800	[thread overview]
Message-ID: <a82cd82f9aa495c45ce0ac3806f92547@208suo.com> (raw)
In-Reply-To: <tencent_68C96D2AD6D16593114698F6D388FC86BF06@qq.com>

The following checkpatch warnings are removed:
WARNING: Missing a blank line after declarations

Signed-off-by: Jie Shi <shijie001@208suo.com>
---
  arch/x86/kvm/kvm_cache_regs.h | 2 ++
  1 file changed, 2 insertions(+)

diff --git a/arch/x86/kvm/kvm_cache_regs.h 
b/arch/x86/kvm/kvm_cache_regs.h
index 75eae9c4998a..0e3808b40974 100644
--- a/arch/x86/kvm/kvm_cache_regs.h
+++ b/arch/x86/kvm/kvm_cache_regs.h
@@ -151,6 +151,7 @@ static inline void kvm_pdptr_write(struct kvm_vcpu 
*vcpu, int index, u64 value)
  static inline ulong kvm_read_cr0_bits(struct kvm_vcpu *vcpu, ulong 
mask)
  {
      ulong tmask = mask & KVM_POSSIBLE_CR0_GUEST_BITS;
+
      if ((tmask & vcpu->arch.cr0_guest_owned_bits) &&
          !kvm_register_is_available(vcpu, VCPU_EXREG_CR0))
          static_call(kvm_x86_cache_reg)(vcpu, VCPU_EXREG_CR0);
@@ -173,6 +174,7 @@ static inline ulong kvm_read_cr0(struct kvm_vcpu 
*vcpu)
  static inline ulong kvm_read_cr4_bits(struct kvm_vcpu *vcpu, ulong 
mask)
  {
      ulong tmask = mask & KVM_POSSIBLE_CR4_GUEST_BITS;
+
      if ((tmask & vcpu->arch.cr4_guest_owned_bits) &&
          !kvm_register_is_available(vcpu, VCPU_EXREG_CR4))
          static_call(kvm_x86_cache_reg)(vcpu, VCPU_EXREG_CR4);

           reply	other threads:[~2023-07-12  6:56 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <tencent_68C96D2AD6D16593114698F6D388FC86BF06@qq.com>]

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=a82cd82f9aa495c45ce0ac3806f92547@208suo.com \
    --to=shijie001@208suo.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.d \
    --cc=x86@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®