linux-kselftest.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
	linux-kselftest@vger.kernel.org, kvm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, drjones@redhat.com,
	sean.j.christopherson@intel.com
Subject: Re: [PATCH] selftests: kvm: Adding config fragments
Date: Wed, 31 Jul 2019 15:02:17 +0200	[thread overview]
Message-ID: <43fd5a9b-7ecd-3fff-2381-1dfce7b8618a@redhat.com> (raw)
In-Reply-To: <20190731105540.28962-1-naresh.kamboju@linaro.org>

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@linaro.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).

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

Paolo

> +CONFIG_KVM=y
> +CONFIG_VHOST_NET=y
> +CONFIG_VHOST=y
> +CONFIG_VHOST_CROSS_ENDIAN_LEGACY=y
> +CONFIG_USER_RETURN_NOTIFIER=y
> +CONFIG_PREEMPT_NOTIFIERS=y
> +CONFIG_TRANSPARENT_HUGEPAGE=y
> +CONFIG_TRANSPARENT_HUGEPAGE_MADVISE=y
> +CONFIG_THP_SWAP=y
> +CONFIG_TRANSPARENT_HUGE_PAGECACHE=y
> +CONFIG_IRQ_BYPASS_MANAGER=y
> +CONFIG_XARRAY_MULTI=y
> 


  reply	other threads:[~2019-07-31 13:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-31 10:55 [PATCH] selftests: kvm: Adding config fragments Naresh Kamboju
2019-07-31 13:02 ` Paolo Bonzini [this message]
2019-07-31 14:38   ` Naresh Kamboju

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=43fd5a9b-7ecd-3fff-2381-1dfce7b8618a@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=drjones@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=sean.j.christopherson@intel.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).