From: Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
To: Stefano Stabellini <sstabellini@kernel.org>,
Julien Grall <julien.grall@arm.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
Subject: [Xen-devel] [PATCH] docs, arm: add documentation on available defconfigs
Date: Fri, 14 Jun 2019 15:23:09 +0000 [thread overview]
Message-ID: <20190614152301.29592-1-volodymyr_babchuk@epam.com> (raw)
As build system now have *_defconfig targets defined,
lets describe available defconfig files for the Arm architecture.
Signed-off-by: Volodymyr Babchuk <volodymyr_babchuk@epam.com>
---
docs/misc/arm/defconfigs.txt | 23 +++++++++++++++++++++++
1 file changed, 23 insertions(+)
create mode 100644 docs/misc/arm/defconfigs.txt
diff --git a/docs/misc/arm/defconfigs.txt b/docs/misc/arm/defconfigs.txt
new file mode 100644
index 0000000000..46c5039eba
--- /dev/null
+++ b/docs/misc/arm/defconfigs.txt
@@ -0,0 +1,23 @@
+Xen hypervisor for Arm architecture have a number of defconfigs, which
+can be used by issuing
+
+ make xxxxx_defconfig
+
+Those defconfigs are located in xen/arch/arm/configs.
+
+Generally, you don't need to use any particular defconfig if you want
+to build default version of Xen. This is because default Xen
+configuration is intended to run on any supported platform.
+
+Anyways, there is a number of defconfig files which have special use:
+
+ - arm32_defconfig is the special defconfig file used by build system as
+ the default configuration for the arm32 sub-architecture.
+
+ - arm64_defconfig is the same as arm32_defconfig, but for arm64 builds.
+
+ - tiny64_defconfig configures Xen hypervisor for the minimal possible
+ build for arm64 architecture. It disables most of the configuration
+ options, except the credit scheduler. Use 'make menuconfig' to
+ enable features needed for your platform, or produced image will
+ be non-functional.
--
2.21.0
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2019-06-14 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 15:23 Volodymyr Babchuk [this message]
2019-08-07 12:14 ` [Xen-devel] [PATCH] docs, arm: add documentation on available defconfigs Julien Grall
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=20190614152301.29592-1-volodymyr_babchuk@epam.com \
--to=volodymyr_babchuk@epam.com \
--cc=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.