From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Andrew Jones <drjones@redhat.com>, Shuah Khan <shuah@kernel.org>,
open list <linux-kernel@vger.kernel.org>,
sean.j.christopherson@intel.com,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>, kvm list <kvm@vger.kernel.org>
Subject: Re: [PATCH v2] selftests: kvm: Adding config fragments
Date: Fri, 9 Aug 2019 13:05:59 +0530 [thread overview]
Message-ID: <CA+G9fYv7RZgm36fbQU5yH=58sX84TxgE93SneB_UhRsD1ivGhg@mail.gmail.com> (raw)
In-Reply-To: <b34e8232-ccfd-898c-49de-afef4168a165@redhat.com>
On Thu, 8 Aug 2019 at 21:30, Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> On 08/08/19 17:10, Andrew Jones wrote:
> >>
> > What does the kselftests config file do? I was about to complain that this
> > would break compiling on non-x86 platforms, but 'make kselftest' and other
> > forms of invoking the build work fine on aarch64 even with this config
> > file. So is this just for documentation? If so, then its still obviously
> > wrong for non-x86 platforms. The only config that makes sense here is KVM.
> > If the other options need to be documented for x86, then should they get
> > an additional config file? tools/testing/selftests/kvm/x86_64/config?
>
> My understanding is that a config file fragment requires some kind of
> kconfig invocation to create a full .config file. When you do that,
> unknown configurations are dropped silently.
You are right on this point. As you said, unknown configs getting dropped for
arm64 cross compilation.
- Naresh
next prev parent reply other threads:[~2019-08-09 7:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 12:31 [PATCH v2] selftests: kvm: Adding config fragments Naresh Kamboju
2019-08-08 15:10 ` Andrew Jones
2019-08-08 16:00 ` Paolo Bonzini
2019-08-09 7:35 ` Naresh Kamboju [this message]
2019-08-09 7:27 ` Naresh Kamboju
2019-08-08 17:22 ` shuah
-- strict thread matches above, loose matches on Subject: below --
2019-08-07 13:58 Naresh Kamboju
2019-08-07 15:52 ` shuah
2019-08-07 16:19 ` Paolo Bonzini
2019-08-07 16:25 ` shuah
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='CA+G9fYv7RZgm36fbQU5yH=58sX84TxgE93SneB_UhRsD1ivGhg@mail.gmail.com' \
--to=naresh.kamboju@linaro.org \
--cc=drjones@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=shuah@kernel.org \
/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).