From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Julien Grall <julien.grall@linaro.org>
Cc: xen-devel@lists.xenproject.org, stefano.stabellini@citrix.com,
ian.campbell@citrix.com, tim@xen.org
Subject: Re: [PATCH 3/6] xen/arm: kernel: Move kernel loading code in init section
Date: Fri, 16 Jan 2015 18:33:04 +0100 [thread overview]
Message-ID: <87vbk63a27.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <1421425248-8727-4-git-send-email-julien.grall@linaro.org> (Julien Grall's message of "Fri, 16 Jan 2015 16:20:45 +0000")
Julien Grall <julien.grall@linaro.org> writes:
> The code to load the kernel is only used when Xen builds dom0. It
> happens during the boot.
I suppose we don't have dom0 kexec for ARM now or this code is not
(won't be) required?
--
Vitaly
next prev parent reply other threads:[~2015-01-16 17:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 16:20 [PATCH 0/6] xen/arm: Move in/out code to/from init section Julien Grall
2015-01-16 16:20 ` [PATCH 1/6] arm/setup: Add missing __init to add_boot_module Julien Grall
2015-01-16 16:28 ` Andrew Cooper
2015-01-16 16:33 ` Julien Grall
2015-01-16 16:20 ` [PATCH 2/6] xen/arm: domain_build: Move all DOM0 building code in init section Julien Grall
2015-01-16 16:20 ` [PATCH 3/6] xen/arm: kernel: Move kernel loading " Julien Grall
2015-01-16 17:33 ` Vitaly Kuznetsov [this message]
2015-01-16 17:49 ` Julien Grall
2015-01-19 10:31 ` Ian Campbell
2015-01-16 16:20 ` [PATCH 4/6] xen/arm: device: Move device_type " Julien Grall
2015-01-16 16:20 ` [PATCH 5/6] xen/arm: platforms: Move init_time and specific_mapping " Julien Grall
2015-01-16 16:20 ` [PATCH 6/6] xen/arm: SMP: Move out of the init section the code to bring up a CPU Julien Grall
2015-01-29 18:32 ` [PATCH 0/6] xen/arm: Move in/out code to/from init section Julien Grall
2015-01-30 11:30 ` Ian Campbell
2015-01-30 11:33 ` Julien Grall
2015-02-02 10:58 ` Ian Campbell
2015-02-02 11:15 ` Jan Beulich
2015-02-02 12:52 ` Julien Grall
2015-02-02 13:12 ` Jan Beulich
2015-02-02 13:34 ` Julien Grall
2015-02-02 12:48 ` Julien Grall
2015-02-02 13:03 ` Ian Campbell
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=87vbk63a27.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=ian.campbell@citrix.com \
--cc=julien.grall@linaro.org \
--cc=stefano.stabellini@citrix.com \
--cc=tim@xen.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.