From: Peter Xu <peterx@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Andrew Jones" <drjones@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>
Subject: Re: [PATCH] KVM: selftests: Detect max PA width from cpuid
Date: Mon, 26 Aug 2019 16:18:47 +0800 [thread overview]
Message-ID: <20190826081847.GB1785@xz-x1> (raw)
In-Reply-To: <00533992-f6e9-3c06-3342-b2b8a95b61d7@redhat.com>
On Mon, Aug 26, 2019 at 10:11:34AM +0200, Thomas Huth wrote:
> On 26/08/2019 09.57, Peter Xu wrote:
> > The dirty_log_test is failing on some old machines like Xeon E3-1220
> > with tripple faults when writting to the tracked memory region:
> >
> > Test iterations: 32, interval: 10 (ms)
> > Testing guest mode: PA-bits:52, VA-bits:48, 4K pages
> > guest physical test memory offset: 0x7fbffef000
> > ==== Test Assertion Failure ====
> > dirty_log_test.c:138: false
> > pid=6137 tid=6139 - Success
> > 1 0x0000000000401ca1: vcpu_worker at dirty_log_test.c:138
> > 2 0x00007f3dd9e392dd: ?? ??:0
> > 3 0x00007f3dd9b6a132: ?? ??:0
> > Invalid guest sync status: exit_reason=SHUTDOWN
> >
> > It's because previously we moved the testing memory region from a
> > static place (1G) to the top of the system's physical address space,
> > meanwhile we stick to 39 bits PA for all the x86_64 machines. That's
> > not true for machines like Xeon E3-1220 where it only supports 36.
> >
> > Let's unbreak this test by dynamically detect PA width from CPUID
> > 0x80000008. Meanwhile, even allow kvm_get_supported_cpuid_index() to
> > fail. I don't know whether that could be useful because I think
> > 0x80000008 should be there for all x86_64 hosts, but I also think it's
> > not really helpful to assert in the kvm_get_supported_cpuid_index().
> [...]
> > diff --git a/tools/testing/selftests/kvm/lib/x86_64/processor.c b/tools/testing/selftests/kvm/lib/x86_64/processor.c
> > index 6cb34a0fa200..9de2fd310ac8 100644
> > --- a/tools/testing/selftests/kvm/lib/x86_64/processor.c
> > +++ b/tools/testing/selftests/kvm/lib/x86_64/processor.c
> > @@ -760,9 +760,6 @@ kvm_get_supported_cpuid_index(uint32_t function, uint32_t index)
> > break;
> > }
> > }
> > -
> > - TEST_ASSERT(entry, "Guest CPUID entry not found: (EAX=%x, ECX=%x).",
> > - function, index);
> > return entry;
> > }
>
> You should also adjust the comment of the function. It currently says
> "Never returns NULL". Not it can return NULL.
Yeh that's better.
>
> And maybe add a TEST_ASSERT() to the other callers instead, which do not
> expect a NULL to be returned?
I think it's fine because it's the same as moving the assert from here
to the callers because when the caller uses entry->xxx it'll assert. :)
Thanks,
--
Peter Xu
next prev parent reply other threads:[~2019-08-26 8:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 7:57 Peter Xu
2019-08-26 8:11 ` Thomas Huth
2019-08-26 8:18 ` Peter Xu [this message]
2019-08-26 8:25 ` Vitaly Kuznetsov
2019-08-26 10:47 ` Peter Xu
2019-08-26 11:34 ` Vitaly Kuznetsov
2019-08-26 11:39 ` Peter Xu
2019-08-26 11:09 ` Andrew Jones
2019-08-26 11:22 ` Peter Xu
2019-08-26 11:43 ` Andrew Jones
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=20190826081847.GB1785@xz-x1 \
--to=peterx@redhat.com \
--cc=drjones@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=thuth@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®