From: Sean Christopherson <seanjc@google.com>
To: Kai Huang <kai.huang@intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"imbrenda@linux.ibm.com" <imbrenda@linux.ibm.com>,
"frankja@linux.ibm.com" <frankja@linux.ibm.com>,
"maz@kernel.org" <maz@kernel.org>,
"chenhuacai@kernel.org" <chenhuacai@kernel.org>,
"borntraeger@linux.ibm.com" <borntraeger@linux.ibm.com>,
"aou@eecs.berkeley.edu" <aou@eecs.berkeley.edu>,
"maobibo@loongson.cn" <maobibo@loongson.cn>,
"loongarch@lists.linux.dev" <loongarch@lists.linux.dev>,
"paul.walmsley@sifive.com" <paul.walmsley@sifive.com>,
"kvmarm@lists.linux.dev" <kvmarm@lists.linux.dev>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
"oliver.upton@linux.dev" <oliver.upton@linux.dev>,
"palmer@dabbelt.com" <palmer@dabbelt.com>,
"kvm-riscv@lists.infradead.org" <kvm-riscv@lists.infradead.org>,
"anup@brainfault.org" <anup@brainfault.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"zhaotianrui@loongson.cn" <zhaotianrui@loongson.cn>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH v2 3/6] KVM: x86: Fold kvm_arch_sched_in() into kvm_arch_vcpu_load()
Date: Wed, 29 May 2024 05:54:18 -0700 [thread overview]
Message-ID: <ZlclevRvntUMYG6O@google.com> (raw)
In-Reply-To: <2a221116a03f57dca8274b6bc2da7541b21d86bb.camel@intel.com>
On Wed, May 29, 2024, Kai Huang wrote:
> I am not familiar with SVM, but it seems the relevant parts are:
>
> control->pause_filter_count;
> vmcb_mark_dirty(svm->vmcb, VMCB_INTERCEPTS);
>
> And it seems they are directly related to programming the hardware, i.e.,
> they got automatically loaded to hardware during VMRUN.
"control" is the control area of the VMCB, i.e. the above pause_filter_count is
equivalent to a VMCS field.
> They need to be updated in the SVM specific code when @ple_window_dirty is
> true in the relevant code path.
>
> Anyway, even it is feasible and worth to do, we should do in a separate
> patchset.
Ya.
next prev parent reply other threads:[~2024-05-29 13:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 1:40 [PATCH v2 0/6] KVM: Fold kvm_arch_sched_in() into kvm_arch_vcpu_load() Sean Christopherson
2024-05-22 1:40 ` [PATCH v2 1/6] KVM: Add a flag to track if a loaded vCPU is scheduled out Sean Christopherson
2024-05-22 15:16 ` Oliver Upton
2024-05-22 1:40 ` [PATCH v2 2/6] KVM: VMX: Move PLE grow/shrink helpers above vmx_vcpu_load() Sean Christopherson
2024-05-22 1:40 ` [PATCH v2 3/6] KVM: x86: Fold kvm_arch_sched_in() into kvm_arch_vcpu_load() Sean Christopherson
2024-05-23 22:47 ` Huang, Kai
2024-05-28 19:16 ` Sean Christopherson
2024-05-29 10:50 ` Huang, Kai
2024-05-29 12:54 ` Sean Christopherson [this message]
2024-05-22 1:40 ` [PATCH v2 4/6] KVM: Delete the now unused kvm_arch_sched_in() Sean Christopherson
2024-05-24 1:50 ` maobibo
2024-05-22 1:40 ` [PATCH v2 5/6] KVM: x86: Unconditionally set l1tf_flush_l1d during vCPU load Sean Christopherson
2024-05-23 22:42 ` Huang, Kai
2024-05-22 1:40 ` [PATCH v2 6/6] KVM: x86: Drop now-superflous setting of l1tf_flush_l1d in vcpu_run() Sean Christopherson
2024-05-23 22:48 ` [PATCH v2 0/6] KVM: Fold kvm_arch_sched_in() into kvm_arch_vcpu_load() Huang, Kai
2024-06-12 1:18 ` Sean Christopherson
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=ZlclevRvntUMYG6O@google.com \
--to=seanjc@google.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=borntraeger@linux.ibm.com \
--cc=chenhuacai@kernel.org \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kai.huang@intel.com \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=loongarch@lists.linux.dev \
--cc=maobibo@loongson.cn \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=pbonzini@redhat.com \
--cc=zhaotianrui@loongson.cn \
/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).