[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DM6PR12MB3500F48AD42562C7DB7A3DEACAAD9@DM6PR12MB3500.namprd12.prod.outlook.com>
Date: Wed, 15 Jun 2022 18:21:53 +0000
From: Kechen Lu <kechenl@...dia.com>
To: Chao Gao <chao.gao@...el.com>
CC: "kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"pbonzini@...hat.com" <pbonzini@...hat.com>,
"seanjc@...gle.com" <seanjc@...gle.com>,
"vkuznets@...hat.com" <vkuznets@...hat.com>,
Somdutta Roy <somduttar@...dia.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [RFC PATCH v3 7/7] KVM: selftests: Add tests for VM and vCPU cap
KVM_CAP_X86_DISABLE_EXITS
Hi Chao,
> -----Original Message-----
> From: Chao Gao <chao.gao@...el.com>
> Sent: Tuesday, June 14, 2022 8:14 PM
> To: Kechen Lu <kechenl@...dia.com>
> Cc: kvm@...r.kernel.org; pbonzini@...hat.com; seanjc@...gle.com;
> vkuznets@...hat.com; Somdutta Roy <somduttar@...dia.com>; linux-
> kernel@...r.kernel.org
> Subject: Re: [RFC PATCH v3 7/7] KVM: selftests: Add tests for VM and vCPU
> cap KVM_CAP_X86_DISABLE_EXITS
>
> External email: Use caution opening links or attachments
>
>
> >+/* Set debug control for trapped instruction exiting to userspace */
> >+static void vcpu_set_debug_exit_userspace(struct kvm_vm *vm, int
> vcpuid,
> >+ struct kvm_guest_debug *debug) {
>
> The debug argument looks pointless. Probably you can remove it.
Makes sense. Thanks for pointing out. Will remove it.
BR,
Kechen
>
> >+ memset(debug, 0, sizeof(*debug));
> >+ debug->control = KVM_GUESTDBG_ENABLE |
> KVM_GUESTDBG_EXIT_USERSPACE;
> >+ vcpu_set_guest_debug(vm, VCPU_ID_1, debug); }
Powered by blists - more mailing lists