[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <abfa3fbc-e234-d0ab-ec35-90d9c251bf79@loongson.cn>
Date: Wed, 22 Feb 2023 09:52:23 +0800
From: Tianrui Zhao <zhaotianrui@...ngson.cn>
To: Paolo Bonzini <pbonzini@...hat.com>
Cc: Huacai Chen <chenhuacai@...nel.org>,
WANG Xuerui <kernel@...0n.name>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
loongarch@...ts.linux.dev, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org, Jens Axboe <axboe@...nel.dk>,
Mark Brown <broonie@...nel.org>,
Alex Deucher <alexander.deucher@....com>,
Oliver Upton <oliver.upton@...ux.dev>, maobibo@...ngson.cn
Subject: Re: [PATCH v2 06/29] LoongArch: KVM: Implement vcpu create and
destroy interface
在 2023年02月21日 01:53, Paolo Bonzini 写道:
> On 2/20/23 07:57, Tianrui Zhao wrote:
>> + vcpu->arch.guest_eentry = (unsigned long)kvm_context->kvm_eentry;
>> + vcpu->arch.vcpu_run = kvm_context->kvm_enter_guest;
>> + vcpu->arch.handle_exit = _kvm_handle_exit;
>
> Here as well, whatever is constant must not be stored in struct
> kvm_arch_vcpu.
>
> Paolo
Thanks, we use this in vcpu_arch because the vcpu_arch is used as
argument in switch.S' methods, we can quickly access the guest_eentry
and handle_exit by using the KVM_ARCH_GEENTRY, KVM_ARCH_HANDLE_EXIT
offsets. If we change to global variable , we should relocate it in
switch.S and may lead to lower accessing speed.
Powered by blists - more mailing lists