lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Wed, 31 Jul 2019 20:08:51 +0530
From:   Naresh Kamboju <naresh.kamboju@...aro.org>
To:     Paolo Bonzini <pbonzini@...hat.com>, Shuah Khan <shuah@...nel.org>
Cc:     "open list:KERNEL SELFTEST FRAMEWORK" 
        <linux-kselftest@...r.kernel.org>, kvm list <kvm@...r.kernel.org>,
        open list <linux-kernel@...r.kernel.org>,
        Andrew Jones <drjones@...hat.com>,
        sean.j.christopherson@...el.com, lkft-triage@...ts.linaro.org
Subject: Re: [PATCH] selftests: kvm: Adding config fragments

On Wed, 31 Jul 2019 at 18:32, Paolo Bonzini <pbonzini@...hat.com> wrote:
>
> On 31/07/19 12:55, Naresh Kamboju wrote:
> > selftests kvm test cases need pre-required kernel configs for the test
> > to get pass.
> >
> > Signed-off-by: Naresh Kamboju <naresh.kamboju@...aro.org>
>
> Most of these are selected by other items.  CONFIG_KVM should be enough
> on ARM and s390 but MIPS, x86 and PPC may also need to select the
> specific "flavors" (for example Intel/AMD for x86).

If the below listed configs are not harmful i would like to keep all listed
configs. Because we (Linaro 's test farm) building kernels with maximum
available kernel fragments for a given test case to get better coverage.

>
> How are these used?  Are they used to build a kernel, or to check that
> an existing kernel supports virtualization?

"make kselftest-merge"
will get configs from tools/testing/selftests/*/config
and enables configs fragments and we build kernel for running
kvm-unit-tests, kselftests, LTP, libhugetlbfs, ssuite, perf and
v4l2-compliance.

- Naresh

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ