From: Paolo Bonzini <pbonzini@redhat.com>
To: Dan Rue <dan.rue@linaro.org>,
Sean Christopherson <sean.j.christopherson@intel.com>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
Andrew Jones <drjones@redhat.com>, kvm list <kvm@vger.kernel.org>,
yzt356@gmail.com, lkft-triage@lists.linaro.org, namit@vmware.com,
Basil Eljuse <Basil.Eljuse@arm.com>,
Krish Sadhukhan <krish.sadhukhan@oracle.com>,
Alexandru Elisei <alexandru.elisei@arm.com>,
jmattson@google.com
Subject: Re: kvm-unit-tests : Kconfigs and extra kernel args for full coverage
Date: Tue, 25 Feb 2020 08:31:32 +0100 [thread overview]
Message-ID: <ea030d10-04a3-6fee-8a63-8fc0d767c230@redhat.com> (raw)
In-Reply-To: <20200224212234.m4gqvgxoqj3elni2@xps.therub.org>
On 24/02/20 22:22, Dan Rue wrote:
> We would also like to be able to verify the additional test coverage
> that may be added to kvm-unit-tests against older kernels (I assume it's
> not all just new features that tests are added for?)
Depending on what you mean by "features". Most changes to
kvm-unit-tests are for aspects of the processor that are emulated more
correctly. These are rarely if ever backported to stable kernels, and
they show up as test failures.
Paolo
next prev parent reply other threads:[~2020-02-25 7:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 12:53 kvm-unit-tests : Kconfigs and extra kernel args for full coverage Naresh Kamboju
2020-02-24 13:06 ` Paolo Bonzini
2020-02-24 17:06 ` Naresh Kamboju
2020-02-24 17:30 ` Sean Christopherson
2020-02-24 21:22 ` Dan Rue
2020-02-25 7:31 ` Paolo Bonzini [this message]
2020-02-24 13:21 ` Alexandru Elisei
2020-02-24 13:38 ` Andrew Jones
2020-02-24 13:47 ` Alexandru Elisei
2020-02-24 14:59 ` Andrew Jones
2020-02-24 16:55 ` Naresh Kamboju
2020-02-24 17:36 ` Alexandru Elisei
2020-02-24 17:44 ` Naresh Kamboju
2020-02-25 8:20 ` Naresh Kamboju
2020-03-03 16:02 ` Alexandru Elisei
2020-03-03 18:53 ` Naresh Kamboju
2020-03-05 10:11 ` Marc Zyngier
2020-02-24 17:29 ` Naresh Kamboju
2020-02-24 20:02 ` Paolo Bonzini
2020-02-25 9:55 ` Naresh Kamboju
2020-02-25 14:21 ` Paolo Bonzini
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=ea030d10-04a3-6fee-8a63-8fc0d767c230@redhat.com \
--to=pbonzini@redhat.com \
--cc=Basil.Eljuse@arm.com \
--cc=alexandru.elisei@arm.com \
--cc=dan.rue@linaro.org \
--cc=drjones@redhat.com \
--cc=jmattson@google.com \
--cc=krish.sadhukhan@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=namit@vmware.com \
--cc=naresh.kamboju@linaro.org \
--cc=sean.j.christopherson@intel.com \
--cc=yzt356@gmail.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;
as well as URLs for NNTP newsgroup(s).