From: "Radim Krčmář" <rkrcmar@redhat.com>
To: "Longpeng(Mike)" <longpeng2@huawei.com>
Cc: pbonzini@redhat.com, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, arei.gonglei@huawei.com,
weidong.huang@huawei.com
Subject: Re: [PATCH] kvm: x86: remove efer_reload entry in kvm_vcpu_stat
Date: Tue, 30 Jan 2018 15:06:22 +0100 [thread overview]
Message-ID: <20180130140621.GC22015@flask> (raw)
In-Reply-To: <1516959248-67928-1-git-send-email-longpeng2@huawei.com>
2018-01-26 17:34+0800, Longpeng(Mike):
> The efer_reload is never used since
> commit 26bb0981b3ff ("KVM: VMX: Use shared msr infrastructure"),
> so remove it.
>
> Signed-off-by: Longpeng(Mike) <longpeng2@huawei.com>
> ---
Queued, thanks.
prev parent reply other threads:[~2018-01-30 14:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 9:34 [PATCH] kvm: x86: remove efer_reload entry in kvm_vcpu_stat Longpeng(Mike)
2018-01-30 14:06 ` 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=20180130140621.GC22015@flask \
--to=rkrcmar@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longpeng2@huawei.com \
--cc=pbonzini@redhat.com \
--cc=weidong.huang@huawei.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;
as well as URLs for NNTP newsgroup(s).