From: Julien Grall <julien.grall@arm.com>
To: Dirk Behme <dirk.behme@de.bosch.com>,
xen-devel@lists.xen.org,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [PATCH 2/2] xen: arm64: doc: Add some details about interrupt handling
Date: Wed, 20 Apr 2016 14:26:11 +0100 [thread overview]
Message-ID: <57178373.60605@arm.com> (raw)
In-Reply-To: <1461045570-6138-2-git-send-email-dirk.behme@de.bosch.com>
Hello Dirk,
On 19/04/16 06:59, Dirk Behme wrote:
> In some mailing list discussion
>
> http://lists.xen.org/archives/html/xen-devel/2016-04/msg00214.html
>
> some details about the interrupt handling of Xen were given.
> Add that so it's not forgotten.
For your information, this is described on the wiki [1]. Although, not
in the most obvious place.
I would prefer to see this kind of documentation on the wiki page under
"Porting Xen on a new SOC".
>
> Signed-off-by: Dirk Behme <dirk.behme@de.bosch.com>
> ---
> Note: I'd be happy to move this to an other documentation file if
> any other file fits better.
>
> docs/misc/arm/booting.txt | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/docs/misc/arm/booting.txt b/docs/misc/arm/booting.txt
> index ffc9029..69b7d81 100644
> --- a/docs/misc/arm/booting.txt
> +++ b/docs/misc/arm/booting.txt
> @@ -27,6 +27,21 @@ On ARM64 Linux it has to be ensured that the Secure Configuration
> Register has the HVC instructions enabled at EL1 and above
> (SCR_EL3.HCE == 1).
>
> +
> +Interrupt usage
> +===============
> +
> +All interrupts are taken by Xen. The function do_IRQ in Xen will
> +dispatch the IRQ either to a guest or call a Xen specific handler.
> +
> +Xen handles only a limited number of interrupt:
> +* timers
> +* UART
> +* SMMU
> +
> +The rest is either routed to guests or blacklisted by Xen.
> +
> +
> [1] linux/Documentation/arm/Booting
> Latest version: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/arm/Booting
>
>
Regards,
[1]
http://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions_whitepaper
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-20 13:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 5:59 [PATCH 1/2] xen: arm64: doc: Add the requirement that SCR_EL3.HCE is enabled Dirk Behme
2016-04-19 5:59 ` [PATCH 2/2] xen: arm64: doc: Add some details about interrupt handling Dirk Behme
2016-04-20 13:26 ` Julien Grall [this message]
2016-04-25 8:56 ` Dirk Behme
2016-04-25 11:06 ` Julien Grall
2016-04-20 13:21 ` [PATCH 1/2] xen: arm64: doc: Add the requirement that SCR_EL3.HCE is enabled Julien Grall
2016-04-22 6:23 ` Dirk Behme
2016-04-22 9:16 ` 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=57178373.60605@arm.com \
--to=julien.grall@arm.com \
--cc=dirk.behme@de.bosch.com \
--cc=sstabellini@kernel.org \
--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 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).