From: Julien Grall <julien.grall@linaro.org>
To: burak sarac <burak@linux.com>, xen-devel@lists.xen.org
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: building xen activated arm kernel for Tegra k1
Date: Fri, 01 Aug 2014 22:22:12 +0100 [thread overview]
Message-ID: <53DC0504.7020503@linaro.org> (raw)
In-Reply-To: <CALS5s1-mA87d22VPRAJ+4hDinMhnMOoe=t-VKqnnsx3h8gjDXQ@mail.gmail.com>
On 01/08/14 19:34, burak sarac wrote:
> Dear all,
Hi,
> I just get my Jetson Tegra k1 and was planning to try out Xen on it.
> It has a 3.10 kernel with Ubuntu 14.04. Also I have downloaded kernel
> source. I am quite new on kernel building but I have done before via
> menuconfig for additional modules. My question is; as I have already
> source and .config from Nvidia do you think below guide would be enough
> for me to rebuild kernel for arm?
>
> http://wiki.xen.org/wiki/Mainline_Linux_Kernel_Configs
This is a good start for building the kernel. Although, some options may
not work/exist on ARM such as:
- *X86* of course :)
- CONFIG_*_PCI_*
- CONFIG_PARAVIRT_*
- CONFIG_HYPERVISOR_GUEST
- all tmem support (I don't even know if someone tried to use it on ARM)
- CONFIG_ACPI
I will see if we can update this page during the next document day for ARM.
You can also give a look to the xen wiki page about ARM. It will give
you some tips about building Xen and debugging guest kernel.
http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions
If something is missing or you have an issue that you don't understand,
just let us know.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-08-01 21:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 18:34 building xen activated arm kernel for Tegra k1 burak sarac
2014-08-01 21:22 ` Julien Grall [this message]
2014-08-02 23:26 ` burak sarac
2014-08-04 9:42 ` Stefano Stabellini
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=53DC0504.7020503@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=burak@linux.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.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.