[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f374979b-e2e3-ca6c-9055-a5e9ac107a2d@redhat.com>
Date: Fri, 22 Oct 2021 15:48:20 +0200
From: Emanuele Giuseppe Esposito <eesposit@...hat.com>
To: Paolo Bonzini <pbonzini@...hat.com>, kvm@...r.kernel.org
Cc: Maxim Levitsky <mlevitsk@...hat.com>,
Sean Christopherson <seanjc@...gle.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
Wanpeng Li <wanpengli@...cent.com>,
Jim Mattson <jmattson@...gle.com>,
Joerg Roedel <joro@...tes.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
x86@...nel.org, "H. Peter Anvin" <hpa@...or.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 4/8] nSVM: use vmcb_save_area_cached in
nested_vmcb_valid_sregs()
On 22/10/2021 09:14, Paolo Bonzini wrote:
> On 11/10/21 16:36, Emanuele Giuseppe Esposito wrote:
>> +
>> +out_free_save:
>> + memset(&svm->nested.save, 0, sizeof(struct vmcb_save_area_cached));
>> +
>
> This memset is not strictly necessary, is it? (Same for out_free_ctl
> later on).
>
It was just to keep the struct clean in case of error, but
you are right, it can be removed.
Thank you,
Emanuele
Powered by blists - more mailing lists