diff mbox

[2/2] xen: arm64: doc: Add some details about interrupt handling

Message ID 1461045570-6138-2-git-send-email-dirk.behme@de.bosch.com (mailing list archive)
State New, archived
Headers show

Commit Message

Dirk Behme April 19, 2016, 5:59 a.m. UTC
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.

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(+)

Comments

Julien Grall April 20, 2016, 1:26 p.m. UTC | #1
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
Dirk Behme April 25, 2016, 8:56 a.m. UTC | #2
Hi Julien,

On 20.04.2016 15:26, Julien Grall wrote:
> 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".


Anything like

http://wiki.xenproject.org/wiki?title=Xen_ARM_with_Virtualization_Extensions_whitepaper&diff=16710&oldid=11342

?

Best regards

Dirk


>>
>> 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 April 25, 2016, 11:06 a.m. UTC | #3
On 25/04/16 09:56, Dirk Behme wrote:
> Hi Julien,

Hello Dirk,

> On 20.04.2016 15:26, Julien Grall wrote:
>> 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".
>
>
> Anything like
>
> http://wiki.xenproject.org/wiki?title=Xen_ARM_with_Virtualization_Extensions_whitepaper&diff=16710&oldid=11342

It sounds good for me.

Regards,
diff mbox

Patch

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