From: Maxim Levitsky <mlevitsk@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, kvm@vger.kernel.org
Cc: Sean Christopherson <seanjc@google.com>,
Shuah Khan <shuah@kernel.org>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
linux-kernel@vger.kernel.org,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH] KVM: selftests: fix hyperv_clock test
Date: Wed, 04 Aug 2021 16:02:58 +0300 [thread overview]
Message-ID: <dcb6aad4e544bed88dd05d3d3c64ac4b9b9f5a25.camel@redhat.com> (raw)
In-Reply-To: <74cec7b5-ae92-2f34-9aa5-30306509f933@redhat.com>
On Wed, 2021-08-04 at 14:24 +0200, Paolo Bonzini wrote:
> On 04/08/21 13:20, Maxim Levitsky wrote:
> > The test was mistakenly using addr_gpa2hva on a gva
> > and that happened to work accidentally.
> >
> > commit 106a2e766eae ("KVM: selftests:
> > Lower the min virtual address for misc page allocations")
> > revealed this bug.
> >
> > Fixes: 106a2e766eae ("KVM: selftests: Lower the min virtual address for misc page allocations")
>
> The right "Fixes" is 2c7f76b4c42b ("selftests: kvm: Add basic Hyper-V
> clocksources tests", 2021-03-18).
Makes sense. I wasn't sure about which commit to blame here.
I'll resend the patch.
Best regards,
Maxim Levitsky
>
> Paolo
>
> > Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com>
> > ---
> > tools/testing/selftests/kvm/x86_64/hyperv_clock.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/tools/testing/selftests/kvm/x86_64/hyperv_clock.c b/tools/testing/selftests/kvm/x86_64/hyperv_clock.c
> > index bab10ae787b6..e0b2bb1339b1 100644
> > --- a/tools/testing/selftests/kvm/x86_64/hyperv_clock.c
> > +++ b/tools/testing/selftests/kvm/x86_64/hyperv_clock.c
> > @@ -215,7 +215,7 @@ int main(void)
> > vcpu_set_hv_cpuid(vm, VCPU_ID);
> >
> > tsc_page_gva = vm_vaddr_alloc_page(vm);
> > - memset(addr_gpa2hva(vm, tsc_page_gva), 0x0, getpagesize());
> > + memset(addr_gva2hva(vm, tsc_page_gva), 0x0, getpagesize());
> > TEST_ASSERT((addr_gva2gpa(vm, tsc_page_gva) & (getpagesize() - 1)) == 0,
> > "TSC page has to be page aligned\n");
> > vcpu_args_set(vm, VCPU_ID, 2, tsc_page_gva, addr_gva2gpa(vm, tsc_page_gva));
> >
prev parent reply other threads:[~2021-08-04 13:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 11:20 Maxim Levitsky
2021-08-04 12:24 ` Paolo Bonzini
2021-08-04 13:02 ` Maxim Levitsky [this message]
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=dcb6aad4e544bed88dd05d3d3c64ac4b9b9f5a25.camel@redhat.com \
--to=mlevitsk@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=shuah@kernel.org \
--cc=vkuznets@redhat.com \
/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
all inboxes | Powered by JetHome®