From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Babu Moger <babu.moger@amd.com>
Cc: joro@8bytes.org, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, x86@kernel.org, pbonzini@redhat.com,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/5] KVM: VMX: Bring the common code to header file
Date: Wed, 28 Mar 2018 22:26:41 +0200 [thread overview]
Message-ID: <20180328202640.GJ26753@flask> (raw)
In-Reply-To: <1521232646-79580-4-git-send-email-babu.moger@amd.com>
2018-03-16 16:37-0400, Babu Moger:
> This patch brings some of the code from vmx to x86.h header file. Now, we
> can share this code between vmx and svm. Modified couple functions to make
> it common.
>
> Signed-off-by: Babu Moger <babu.moger@amd.com>
> ---
> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
> @@ -6683,8 +6652,9 @@ static void shrink_ple_window(struct kvm_vcpu *vcpu)
> struct vcpu_vmx *vmx = to_vmx(vcpu);
> int old = vmx->ple_window;
>
> - vmx->ple_window = __shrink_ple_window(old,
> - ple_window_shrink, ple_window);
> + vmx->ple_window = __shrink_ple_window(old, ple_window,
> + ple_window_shrink,
> + 0);
I have preserved the old minumum (ple_window, so we could't get
uselessly small values).
next prev parent reply other threads:[~2018-03-28 20:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 20:37 [PATCH v2 0/5] KVM: x86: Implement Pause Loop Exit for SVM Babu Moger
2018-03-16 20:37 ` [PATCH v2 1/5] KVM: VMX: Fix the module parameters for vmx Babu Moger
2018-03-16 20:37 ` [PATCH v2 2/5] KVM: VMX: Remove ple_window_actual_max Babu Moger
2018-03-28 20:24 ` Radim Krčmář
2018-03-16 20:37 ` [PATCH v2 3/5] KVM: VMX: Bring the common code to header file Babu Moger
2018-03-28 20:26 ` Radim Krčmář [this message]
2018-03-28 21:12 ` Moger, Babu
2018-03-16 20:37 ` [PATCH v2 4/5] KVM: SVM: Add pause filter threshold Babu Moger
2018-03-16 20:37 ` [PATCH v2 5/5] KVM: SVM: Implement pause loop exit logic in SVM Babu Moger
2018-03-28 20:30 ` Radim Krčmář
2018-03-28 21:14 ` Moger, Babu
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=20180328202640.GJ26753@flask \
--to=rkrcmar@redhat.com \
--cc=babu.moger@amd.com \
--cc=hpa@zytor.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--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