From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Jim Mattson <jmattson@google.com>,
Andrew Honig <ahonig@google.com>, Barret Rhoden <brho@google.com>
Subject: [PATCH 0/3] KVM: Clean up guest/host cache read/write code
Date: Thu, 9 Jan 2020 15:56:17 -0800 [thread overview]
Message-ID: <20200109235620.6536-1-sean.j.christopherson@intel.com> (raw)
Minor cleanup to fix the underlying crustiness that led to an uninitialized
variable warning reported by Barret.
The first two patches are tagged with Fixes:, but I don't know that they're
actually worth backporting to stable. Functionally, everthing works, it's
just a bit weird and AFAICT not what is intended. It might be preferable
to take Barret's patch[*] first and only mark that for stable, as it fixes
the immediate issue without revamping __kvm_gfn_to_hva_cache_init().
[*] https://lkml.kernel.org/r/20200109195855.17353-1-brho@google.com
Sean Christopherson (3):
KVM: Check for a bad hva before dropping into the ghc slow path
KVM: Clean up __kvm_gfn_to_hva_cache_init() and its callers
KVM: Return immediately if __kvm_gfn_to_hva_cache_init() fails
virt/kvm/kvm_main.c | 45 ++++++++++++++++++++++++++-------------------
1 file changed, 26 insertions(+), 19 deletions(-)
--
2.24.1
next reply other threads:[~2020-01-09 23:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 23:56 Sean Christopherson [this message]
2020-01-09 23:56 ` [PATCH 1/3] KVM: Check for a bad hva before dropping into the ghc slow path Sean Christopherson
2020-01-09 23:56 ` [PATCH 2/3] KVM: Clean up __kvm_gfn_to_hva_cache_init() and its callers Sean Christopherson
2020-01-09 23:56 ` [PATCH 3/3] KVM: Return immediately if __kvm_gfn_to_hva_cache_init() fails Sean Christopherson
2020-01-21 13:51 ` [PATCH 0/3] KVM: Clean up guest/host cache read/write code Paolo Bonzini
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=20200109235620.6536-1-sean.j.christopherson@intel.com \
--to=sean.j.christopherson@intel.com \
--cc=ahonig@google.com \
--cc=brho@google.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®