On 20.12.2016 19:01, Julien Grall wrote:
Hi Andrii,
On 20/12/2016 19:00, Andrii Anisov wrote:
Sorry for the mess,
I mean the xen-swiotlb issue on renesas board:
Bosch: problem with xen-swiotlb. It does not work properly on renesas
board.
Stefano: please report the error on the ML
ACTION:
On 10.11.2016 10:25, Iurii Mykhalskyi wrote:
Hello Dirk,
On Thu, Nov 10, 2016 at 8:54 AM, Dirk Behme mailto:dirk.be...@de.bosch.com>> wrote:
On 09.11.2016 13:14, Julien Grall wrote:
Hello,
On 09/11/16 07:14, Dirk Behme wrote:
On 08.11.2016 16:41,
On 09.11.2016 13:14, Julien Grall wrote:
Hello,
On 09/11/16 07:14, Dirk Behme wrote:
On 08.11.2016 16:41, Iurii Mykhalskyi wrote:
Hello Dirk,
I have made only single change - I recompile ATF to leave CPU in EL2
mode and reflash it.
Yes, this is what I meant with 'modifying fir
On 08.11.2016 13:19, Julien Grall wrote:
Hi all,
I would like to start organizing a recurring community call to discuss
and sync-up on upcoming features for Xen ARM.
Example of features that could be discussed:
- Sharing co-processor between guests
- PCI passthrough
Would it be an op
//github.com/renesas-rcar/meta-renesas
If you don't mind - I can create & handle documentation page about board
setup and take ownership about further board support.
I'm fine with that. Thanks!
Best regards
Dirk
On Tue, Nov 8, 2016 at 5:22 PM, Dirk Behme mailto:dirk.be...@gmail.
On 08.11.2016 15:30, Julien Grall wrote:
Hello Iurii,
Dirk (in CC) sent a similar patch few months ago to add support for
this board (see [1]).
I didn't ack the patch back then because I wanted to see documentation
on the wiki to bring up Xen on this board (see [2] for the
requirements). I didn
On 28.07.2016 13:17, Julien Grall wrote:
Hi Dirk,
On 27/07/16 06:05, Dirk Behme wrote:
Hi Michael, Stefano and Julien,
On 22.07.2016 03:16, Stefano Stabellini wrote:
On Thu, 21 Jul 2016, Michael Turquette wrote:
Quoting Stefano Stabellini (2016-07-14 03:38:04)
On Thu, 14 Jul 2016, Dirk
Hi Michael, Stefano and Julien,
On 22.07.2016 03:16, Stefano Stabellini wrote:
On Thu, 21 Jul 2016, Michael Turquette wrote:
Quoting Stefano Stabellini (2016-07-14 03:38:04)
On Thu, 14 Jul 2016, Dirk Behme wrote:
On 13.07.2016 23:03, Michael Turquette wrote:
Quoting Dirk Behme (2016-07-13
, Dirk Behme
wrote:
Clocks described by this property are reserved for use by Xen, and the
OS
must not alter their state any way, such as disabling or gating a
clock,
or modifying its rate. Ensuring this may impose constraints on parent
clocks or other resources used by the clock tree.
This property
On 14.07.2016 19:14, Julien Grall wrote:
Hello,
On 14/07/16 17:30, Dirk Behme wrote:
On 14.07.2016 17:55, Stefano Stabellini wrote:
On Thu, 14 Jul 2016, Dirk Behme wrote:
On 14.07.2016 12:38, Stefano Stabellini wrote:
On Thu, 14 Jul 2016, Dirk Behme wrote:
On 13.07.2016 23:03, Michael
On 14.07.2016 17:55, Stefano Stabellini wrote:
On Thu, 14 Jul 2016, Dirk Behme wrote:
On 14.07.2016 12:38, Stefano Stabellini wrote:
On Thu, 14 Jul 2016, Dirk Behme wrote:
On 13.07.2016 23:03, Michael Turquette wrote:
Quoting Dirk Behme (2016-07-13 11:56:30)
On 13.07.2016 20:43, Stefano
On 14.07.2016 12:38, Stefano Stabellini wrote:
On Thu, 14 Jul 2016, Dirk Behme wrote:
On 13.07.2016 23:03, Michael Turquette wrote:
Quoting Dirk Behme (2016-07-13 11:56:30)
On 13.07.2016 20:43, Stefano Stabellini wrote:
On Wed, 13 Jul 2016, Dirk Behme wrote:
On 13.07.2016 00:26, Michael
On 14.07.2016 12:14, Julien Grall wrote:
Hi Dirk,
On 14/07/16 07:31, Dirk Behme wrote:
On 13.07.2016 23:03, Michael Turquette wrote:
Quoting Dirk Behme (2016-07-13 11:56:30)
On 13.07.2016 20:43, Stefano Stabellini wrote:
On Wed, 13 Jul 2016, Dirk Behme wrote:
On 13.07.2016 00:26, Michael
On 13.07.2016 23:03, Michael Turquette wrote:
Quoting Dirk Behme (2016-07-13 11:56:30)
On 13.07.2016 20:43, Stefano Stabellini wrote:
On Wed, 13 Jul 2016, Dirk Behme wrote:
On 13.07.2016 00:26, Michael Turquette wrote:
Quoting Dirk Behme (2016-07-12 00:46:45)
Clocks described by this
On 13.07.2016 21:07, Stefano Stabellini wrote:
On Wed, 13 Jul 2016, Dirk Behme wrote:
On 13.07.2016 20:35, Stefano Stabellini wrote:
On Tue, 12 Jul 2016, Dirk Behme wrote:
Clocks described by this property are reserved for use by Xen, and the OS
must not alter their state any way, such as
On 13.07.2016 20:43, Stefano Stabellini wrote:
On Wed, 13 Jul 2016, Dirk Behme wrote:
On 13.07.2016 00:26, Michael Turquette wrote:
Quoting Dirk Behme (2016-07-12 00:46:45)
Clocks described by this property are reserved for use by Xen, and the OS
must not alter their state any way, such as
On 13.07.2016 20:35, Stefano Stabellini wrote:
On Tue, 12 Jul 2016, Dirk Behme wrote:
Clocks described by this property are reserved for use by Xen, and the OS
must not alter their state any way, such as disabling or gating a clock,
or modifying its rate. Ensuring this may impose constraints on
On 13.07.2016 00:26, Michael Turquette wrote:
Quoting Dirk Behme (2016-07-12 00:46:45)
Clocks described by this property are reserved for use by Xen, and the OS
must not alter their state any way, such as disabling or gating a clock,
or modifying its rate. Ensuring this may impose constraints
ct.org/xen/bug/45
too.
Signed-off-by: Dirk Behme
---
Changes in v4: Switch to the xen.txt description proposed by Mark:
https://www.spinics.net/lists/arm-kernel/msg516158.html
Changes in v3: Use the xen.txt description proposed by Michael. Thanks!
Changes in v2: Drop the Linux impl
Hi,
On 11.07.2016 11:25, Andre Przywara wrote:
Hi Dirk,
On 08/07/16 12:38, Dirk Behme wrote:
Hi Andre,
On 05.07.2016 16:29, Andre Przywara wrote:
Hi,
On 05/07/16 15:22, Dirk Behme wrote:
On 05.07.2016 15:45, Andre Przywara wrote:
Hi,
On 05/07/16 14:34, Julien Grall wrote:
(CC Andre
Hi Andre,
On 05.07.2016 16:29, Andre Przywara wrote:
Hi,
On 05/07/16 15:22, Dirk Behme wrote:
On 05.07.2016 15:45, Andre Przywara wrote:
Hi,
On 05/07/16 14:34, Julien Grall wrote:
(CC Andre)
On 05/07/16 14:04, Dirk Behme wrote:
On 05.07.2016 14:45, Julien Grall wrote:
On 05/07/16 13
Hi Michael and Julien,
On 08.07.2016 11:34, Julien Grall wrote:
Hi Dirk,
On 08/07/16 08:44, Dirk Behme wrote:
Xen hypervisor drivers might replace native OS drivers. The result is
that some important clocks that are enabled by the OS in the non-Xen
case are not properly enabled in the
in the hypervisor node
and if so consume and enable the given clocks. This prevents the clocks
from being disabled by the OS.
Signed-off-by: Dirk Behme
---
Changes in v3: Use the xen.txt description proposed by Michael. Thanks!
Changes in v2: Drop the Linux implementation details like clk_di
Hi,
On 06.07.2016 03:34, Michael Turquette wrote:
Hi!
Quoting Dirk Behme (2016-06-30 03:32:32)
Some clocks might be used by the Xen hypervisor and not by the Linux
kernel. If these are not registered by the Linux kernel, they might be
disabled by clk_disable_unused() as the kernel doesn&#
On 08.07.2016 04:50, Michael Turquette wrote:
Quoting Dirk Behme (2016-07-07 00:32:34)
Hi Michael,
On 06.07.2016 22:42, Michael Turquette wrote:
Hi Julien,
Quoting Julien Grall (2016-07-06 06:10:52)
On 06/07/16 02:34, Michael Turquette wrote:
Hi!
Hello Michael,
Quoting Dirk Behme (2016
Hi Julien,
On 06.07.2016 16:21, Julien Grall wrote:
On 06/07/16 15:03, Dirk Behme wrote:
On 06.07.2016 15:17, Julien Grall wrote:
Hi Dirk,
On 06/07/16 07:33, Dirk Behme wrote:
Could you share the U-Boot commands how you load and esp. start Xen?
For
loading you use TFTP? How do you start
Hi Michael,
On 06.07.2016 22:42, Michael Turquette wrote:
Hi Julien,
Quoting Julien Grall (2016-07-06 06:10:52)
On 06/07/16 02:34, Michael Turquette wrote:
Hi!
Hello Michael,
Quoting Dirk Behme (2016-06-30 03:32:32)
Some clocks might be used by the Xen hypervisor and not by the Linux
On 06.07.2016 15:17, Julien Grall wrote:
Hi Dirk,
On 06/07/16 07:33, Dirk Behme wrote:
Could you share the U-Boot commands how you load and esp. start Xen? For
loading you use TFTP? How do you start Xen with U-Boot, then? I think we
have to pass the device tree address in x0 and the Linux
Hi Andre,
On 05.07.2016 16:29, Andre Przywara wrote:
Hi,
On 05/07/16 15:22, Dirk Behme wrote:
On 05.07.2016 15:45, Andre Przywara wrote:
Hi,
On 05/07/16 14:34, Julien Grall wrote:
(CC Andre)
On 05/07/16 14:04, Dirk Behme wrote:
On 05.07.2016 14:45, Julien Grall wrote:
On 05/07/16 13
On 05.07.2016 15:45, Andre Przywara wrote:
Hi,
On 05/07/16 14:34, Julien Grall wrote:
(CC Andre)
On 05/07/16 14:04, Dirk Behme wrote:
On 05.07.2016 14:45, Julien Grall wrote:
On 05/07/16 13:09, Dirk Behme wrote:
Hi Julien,
On 05.07.2016 13:39, Julien Grall wrote:
Hi Dirk,
On 05/07/16
On 05.07.2016 14:45, Julien Grall wrote:
On 05/07/16 13:09, Dirk Behme wrote:
Hi Julien,
On 05.07.2016 13:39, Julien Grall wrote:
Hi Dirk,
On 05/07/16 07:37, Dirk Behme wrote:
Signed-off-by: Dirk Behme
This patch looks good to me, however I would like to see the
documentation on the
Hi Julien,
On 05.07.2016 13:39, Julien Grall wrote:
Hi Dirk,
On 05/07/16 07:37, Dirk Behme wrote:
Signed-off-by: Dirk Behme
This patch looks good to me, however I would like to see the
documentation on the wiki page (see [1]) before giving any formal ack.
Ok, many thanks for your review
Hi Mark,
On 05.07.2016 12:39, Mark Rutland wrote:
Hi,
On Tue, Jul 05, 2016 at 08:50:23AM +0200, Dirk Behme wrote:
Some clocks might be used by the Xen hypervisor and not by the Linux
kernel. If these are not registered by the Linux kernel, they might be
disabled by clk_disable_unused() as the
d with this mark them as used. This prevents the clocks
from being disabled.
Signed-off-by: Dirk Behme
---
Changes in v2: Drop the Linux implementation details like clk_disable_unused
in xen.txt.
Documentation/devicetree/bindings/arm/xen.txt | 13
arch/arm/xen/en
Signed-off-by: Dirk Behme
---
Changes in v2: Drop unneeded rcar3.c
docs/misc/arm/early-printk.txt| 1 +
xen/arch/arm/Rules.mk | 1 +
xen/arch/arm/arm64/debug-scif.inc | 54 +++
xen/drivers/char/Kconfig | 2 +-
4 files
Signed-off-by: Dirk Behme
---
docs/misc/arm/early-printk.txt| 1 +
xen/arch/arm/Rules.mk | 1 +
xen/arch/arm/arm64/debug-scif.inc | 54 +++
xen/arch/arm/platforms/Makefile | 1 +
xen/arch/arm/platforms/rcar3.c| 41
On 30.06.2016 16:21, Mark Rutland wrote:
On Thu, Jun 30, 2016 at 12:32:32PM +0200, Dirk Behme wrote:
Some clocks might be used by the Xen hypervisor and not by the Linux
kernel. If these are not registered by the Linux kernel, they might be
disabled by clk_disable_unused() as the kernel doesn&#
d with this mark them as used. This prevents the clocks
from being disabled.
Signed-off-by: Dirk Behme
---
Changes in v2:
- Rebase against git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
for-linus-4.8
- Add changes to Documentation/devicetree/bindings/arm/xen.txt
Documentation/d
Hi Julien,
On 22.06.2016 17:26, Julien Grall wrote:
Hello Dirk,
On 21/06/16 11:16, Dirk Behme wrote:
Some clocks might be used by the Xen hypervisor and not by the Linux
kernel. If these are not registered by the Linux kernel, they might be
disabled by clk_disable_unused() as the kernel
On 29.06.2016 13:47, Julien Grall wrote:
On 29/06/2016 12:31, Dirk Behme wrote:
On 29.06.2016 13:08, Dirk Behme wrote:
Hi Julien,
On 29.06.2016 12:32, Julien Grall wrote:
Hi Dirk,
On 27/06/2016 08:53, Dirk Behme wrote:
+if ( (end - start) > size ) {
+printk(XENLOG_ERR &qu
Hi Julien,
On 29.06.2016 13:33, Julien Grall wrote:
On 29/06/2016 12:08, Dirk Behme wrote:
On 29.06.2016 12:32, Julien Grall wrote:
Hi Dirk,
On 27/06/2016 08:53, Dirk Behme wrote:
+if ( (end - start) > size ) {
+printk(XENLOG_ERR "Error: Kernel Image size: %
On 29.06.2016 13:08, Dirk Behme wrote:
Hi Julien,
On 29.06.2016 12:32, Julien Grall wrote:
Hi Dirk,
On 27/06/2016 08:53, Dirk Behme wrote:
+if ( (end - start) > size ) {
+printk(XENLOG_ERR "Error: Kernel Image size: %lu bytes >
bootmodule size:
On 29.06.2016 13:08, Dirk Behme wrote:
Hi Julien,
On 29.06.2016 12:32, Julien Grall wrote:
Hi Dirk,
On 27/06/2016 08:53, Dirk Behme wrote:
+if ( (end - start) > size ) {
+printk(XENLOG_ERR "Error: Kernel Image size: %lu bytes >
bootmodule size:
Hi Julien,
On 29.06.2016 12:32, Julien Grall wrote:
Hi Dirk,
On 27/06/2016 08:53, Dirk Behme wrote:
+if ( (end - start) > size ) {
+printk(XENLOG_ERR "Error: Kernel Image size: %lu bytes >
bootmodule size: %lu bytes\n",
+ zimage.image_size
ls and X-gene. And for the latter it was an early
support with only the serial and timer upstreamed.
Signed-off-by: Dirk Behme
---
Changes in v4: Print header error only based on ZIMAGE64_MAGIC_V0. Drop comment
and unnecessary if statement.
Changes in v3: Just update of the commit
Hi Julien,
On 26.06.2016 10:29, Julien Grall wrote:
Hello Dirk,
On 26/06/2016 06:47, Dirk Behme wrote:
On 23.06.2016 17:18, Julien Grall wrote:
On 23/06/16 07:38, Dirk Behme wrote:
+uint64_t res2;
uint64_t res3;
uint64_t res4;
-uint64_t res5
Hi Julien,
On 23.06.2016 17:18, Julien Grall wrote:
Hi Dirk,
On 23/06/16 07:38, Dirk Behme wrote:
With the Linux kernel commits
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/Documentation/arm64/booting.txt?id=4370eec05a887b0cd4392cd5dc5b2713174745c0
https
The scif-uart.c is an ARM specific UART driver for the Renesas RCar
SoC family.
Signed-off-by: Dirk Behme
---
Note: This has been discussed in
https://lists.xen.org/archives/html/xen-devel/2016-06/msg03051.html
https://lists.xen.org/archives/html/xen-devel/2016-06/msg03062.html
MAINTAINERS
On 23.06.2016 17:02, Julien Grall wrote:
On 22/06/16 16:58, Julien Grall wrote:
On 21/06/16 11:15, Dirk Behme wrote:
+printk("Failed to remember the clock node of %s\n",
path);
+printk("Use the Linux kernel command
'clk_ignore_unused'\n"
ls and X-gene. And for the latter it was an early
support with only the serial and timer upstreamed.
Signed-off-by: Dirk Behme
---
Changes in v3: Just update of the commit message regarding the support
for kernels < 3.12. No change to the patch itself.
xen/a
On 22.06.2016 15:44, Julien Grall wrote:
Hi Konrad,
On 22/06/16 14:30, Konrad Rzeszutek Wilk wrote:
On Wed, Jun 22, 2016 at 10:59:19AM +0200, Dirk Behme wrote:
With the Linux kernel commits
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/Documentation/arm64/booting.txt
On 22.06.2016 15:30, Konrad Rzeszutek Wilk wrote:
On Wed, Jun 22, 2016 at 10:59:19AM +0200, Dirk Behme wrote:
With the Linux kernel commits
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/Documentation/arm64/booting.txt?id=4370eec05a887b0cd4392cd5dc5b2713174745c0
https
done by the firmware.
Signed-off-by: Dirk Behme
---
xen/drivers/char/scif-uart.c | 40
1 file changed, 40 deletions(-)
diff --git a/xen/drivers/char/scif-uart.c b/xen/drivers/char/scif-uart.c
index bc157fe..f9ae257 100644
--- a/xen/drivers/char/scif
The two struct members baud and clock_hz are in the end read only
variables nowhere used for anything useful. Removing them makes
the code much simpler without changing any functionality.
Signed-off-by: Dirk Behme
---
xen/drivers/char/scif-uart.c| 24 +---
xen/include
/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4370eec05a887b0cd4392cd5dc5b2713174745c0
Signed-off-by: Dirk Behme
---
xen/arch/arm/kernel.c | 43 ++-
1 file changed, 26 insertions(+), 17 deletions(-)
diff --git a/xen/arch/arm/kernel.c b/xen/arch/
The two struct members baud and clock_hz are in the end read only
variables nowhere used for anything useful. Removing them makes
the code much simpler without changing any functionality.
Signed-off-by: Dirk Behme
---
xen/drivers/char/scif-uart.c| 24 +---
xen/include
Besides the 14MHz external clock, the SCIF might be clocked by an
internal 66MHz clock. If this is the case, the current clock source
selection breaks this configuration. Completely drop this and rely
on the settings done by the firmware.
Signed-off-by: Dirk Behme
---
xen/drivers/char/scif
Hello Oleksandr,
On 21.06.2016 14:54, Oleksandr Tyshchenko wrote:
On Tue, Jun 21, 2016 at 3:15 PM, Julien Grall wrote:
On 21/06/16 11:16, Oleksandr Tyshchenko wrote:
Hi, Dirk.
Hello Oleksandr,
Hello Julien.
On Tue, Jun 21, 2016 at 12:15 PM, Dirk Behme
wrote:
In scif_uart_init
Hi Julien,
On 21.06.2016 14:20, Julien Grall wrote:
Hello Dirk,
On 21/06/16 10:15, Dirk Behme wrote:
Besides the 14MHz external clock, the SCIF might be clocked by an
internal 66MHz clock. Detect this clock based on the SCIF_DL register
being 0 (internal clock) or != 0 (external clock).
Do
Hi Julien,
On 21.06.2016 13:14, Julien Grall wrote:
Hello Dirk,
On 21/06/16 10:08, Dirk Behme wrote:
With the Linux kernel commits
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/Documentation/arm64/booting.txt?id=4370eec05a887b0cd4392cd5dc5b2713174745c0
https
Subject: Re: ARM Xen Bug #45: Is there a solution?
Date: Tue, 31 May 2016 11:44:23 +0100
From: Julien Grall
To: Dirk Behme , xen-devel@lists.xen.org
CC: Stefano Stabellini , Ian Jackson
Hello Dirk,
On 27/05/16 13:34, Dirk Behme wrote:
On 26.05.2016 11:00, Julien Grall wrote:
On 25/05
On 21.06.2016 12:16, Dirk Behme wrote:
Some clocks might be used by the Xen hypervisor and not by the Linux
kernel. If these are not registered by the Linux kernel, they might be
disabled by clk_disable_unused() as the kernel doesn't know that they
are used. The clock of the serial co
On 21.06.2016 12:15, Dirk Behme wrote:
Some clocks might be used by Xen (drivers) and not by the Linux kernel. If
these are not registered by the Linux kernel, they might be disabled by the
Linux kernel's clk_disable_unused() as the kernel doesn't know that
they are used (by Xen dri
d with this mark them as used. This prevents the clocks
from being disabled.
Signed-off-by: Dirk Behme
---
arch/arm/xen/enlighten.c | 35 +++
1 file changed, 35 insertions(+)
diff --git a/arch/arm/xen/enlighten.c b/arch/arm/xen/enlighten.c
index 75cd734..ee6e81f 10
hypervisor node
containing all these clocks. The Linux kernel can register all these clocks,
preventing them from being disabled, then.
Signed-off-by: Dirk Behme
---
xen/arch/arm/domain_build.c | 20
xen/arch/arm/kernel.h | 7 +++
2 files changed, 27 insertions
In scif_uart_init() uart->baud is set to BAUD_AUTO. So its a basic error
if this is different later. Detect this by an ASSERT, but remove the
dead code normally never reached.
Signed-off-by: Dirk Behme
---
xen/drivers/char/scif-uart.c | 23 ++-
1 file changed, 6 inserti
The two struct members baud and clock_hz are in the end read only
variables nowhere used for anything useful. Removing them makes
the code much simpler without changing any functionality.
Signed-off-by: Dirk Behme
---
xen/drivers/char/scif-uart.c| 13 +
xen/include/asm-arm/scif
Besides the 14MHz external clock, the SCIF might be clocked by an
internal 66MHz clock. Detect this clock based on the SCIF_DL register
being 0 (internal clock) or != 0 (external clock).
Signed-off-by: Dirk Behme
---
xen/drivers/char/scif-uart.c | 15 +--
1 file changed, 13
size != 0, let's use this image size, now. This does
allow us to warn if the kernel Image is larger than the size given in
the device tree, too.
Signed-off-by: Dirk Behme
---
xen/arch/arm/kernel.c | 41 -
1 file changed, 24 insertions(+), 17 deletion
On 26.05.2016 11:00, Julien Grall wrote:
On 25/05/2016 16:10, Dirk Behme wrote:
On 24.05.2016 22:05, Julien Grall wrote:
On 24/05/2016 14:39, Dirk Behme wrote:
On 23.05.2016 22:15, Julien Grall wrote:
Hello Dirk,
is there a solution for
arm: domain 0 disables clocks which are in fact
Hi Julien,
On 24.05.2016 22:05, Julien Grall wrote:
On 24/05/2016 14:39, Dirk Behme wrote:
Hi Julien,
Hello Dirk,
On 23.05.2016 22:15, Julien Grall wrote:
Hello Dirk,
is there a solution for
arm: domain 0 disables clocks which are in fact being used
http://bugs.xenproject.org/xen/bug
Hi Julien,
On 23.05.2016 22:15, Julien Grall wrote:
Hello Dirk,
is there a solution for
arm: domain 0 disables clocks which are in fact being used
http://bugs.xenproject.org/xen/bug/45
?
On an ARM based board I have to use 'clk_ignore_unused' preventing that
Dom0 disables the UART clock for
Hello,
is there a solution for
arm: domain 0 disables clocks which are in fact being used
http://bugs.xenproject.org/xen/bug/45
?
On an ARM based board I have to use 'clk_ignore_unused' preventing
that Dom0 disables the UART clock for the console UART configured with
console=hvc0.
Best reg
From: Dirk Behme
Add a section about what the firmware should do in EL3 before starting Xen.
E.g guest will use HVC instruction to issue hypercall. As this can be set only
at EL3, i.e. outside Xen, document this boot requirement.
Signed-off-by: Dirk Behme
---
docs/misc/arm/booting.txt | 11
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 forg
On 20.04.2016 15:21, Julien Grall wrote:
(CC REST maintainers)
Hello Dirk,
Please CC the relevant maintainers for this patch. You can use
scripts/get_maintainers.pl for this purpose.
On 19/04/16 06:59, Dirk Behme wrote:
On ARM64 Linux the HVC instruction is used to trap into Xen. As this
can
Add a section about what the firmware should do in EL3 before starting Xen.
E.g. on ARM Linux the HVC instruction is used to trap into Xen. As this
can be set only at EL3, i.e. outside from Xen, document this boot requirement.
Signed-off-by: Dirk Behme
---
docs/misc/arm/booting.txt | 15
Xen needs to blacklist any PSCI node as it will be recreated for DOM0.
Up to now, this was done only for arm,psci and arm,psci-0.2 compatible
nodes. Add PSCI 1.0 compatibility to make device tree nodes with
compatible = "arm,psci-1.0";
blacklisted, too
Signed-off-by: Dirk Behme
---
Add PSCI 1.0 compatibility strings to make Xen behave correctly with
device trees having
compatible = "arm,psci-1.0";
Signed-off-by: Dirk Behme
---
xen/arch/arm/domain_build.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/xen/arch/arm/domain_build.c b/xen/arch/arm/domain_bui
On ARM64 Linux the HVC instruction is used to trap into Xen. As this
can be set only at EL3, i.e. outside from Xen, document this boot
requirement.
Signed-off-by: Dirk Behme
---
docs/misc/arm/booting.txt | 4
1 file changed, 4 insertions(+)
diff --git a/docs/misc/arm/booting.txt b/docs
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
---
Note: I'd be happy to move this to an other documentati
On 18.04.2016 10:17, Julien Grall wrote:
On 16/04/2016 18:39, Dirk Behme wrote:
Hi Julien,
Hi Dirk,
On 06.04.2016 12:48, Julien Grall wrote:
On 04/04/2016 16:44, Dirk Behme wrote:
Hi Julien,
I'm using
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/
Hi Julien,
On 06.04.2016 12:48, Julien Grall wrote:
On 04/04/2016 16:44, Dirk Behme wrote:
Hi Julien,
Hello Dirk,
On 01.04.2016 18:34, Julien Grall wrote:
On 31/03/16 18:41, Dirk Behme wrote:
Also have you tried a newer version of Xen?
I've switched to the recent master
a6f2
Hi Julien,
On 01.04.2016 18:34, Julien Grall wrote:
On 31/03/16 18:41, Dirk Behme wrote:
Hello Julien,
Hello Dirk,
On 29.03.2016 20:53, Julien Grall wrote:
On 23/03/16 17:24, Dirk Behme wrote:
trying to bring up Xen on a new ARMv8 64-bit Cortex A57 eval board, I
get [1] and then its
Hello Julien,
On 29.03.2016 20:53, Julien Grall wrote:
On 23/03/16 17:24, Dirk Behme wrote:
Hi,
Hello Dirk,
Sorry for the late answer.
Many thanks for answering at all :)
trying to bring up Xen on a new ARMv8 64-bit Cortex A57 eval board, I
get [1] and then its hanging there.
The
Hi,
trying to bring up Xen on a new ARMv8 64-bit Cortex A57 eval board, I
get [1] and then its hanging there.
I'd guess that it hangs due to missing timer interrupt, maybe missing
interrupts at all?
Any hints how to debug this? Or where to look?
It might be possible that the board's firmwa
On 04.02.2016 18:07, Dirk Behme wrote:
On 04.02.2016 18:00, Ian Campbell wrote:
On Thu, 2016-02-04 at 17:49 +0100, Dirk Behme wrote:
From: Dirk Behme
Starting in the wrong ELx mode I get the following debug output:
...
- Current EL 0004 -
- Xen must be entered in NS EL2 mode -
- Boot
Hi,
trying to bring up Xen on an ARM64 CA57 device (1 core atm) using a
recent Xen 4.7-unstable and Linux kernel 4.4.0+ I'm getting [1]. The
device tree configures arm,gic-400.
Regarding the , the Linux kernel boot messages are stopping
here. The debugger shows the system looping in xen/arch
On 04.02.2016 18:00, Ian Campbell wrote:
On Thu, 2016-02-04 at 17:49 +0100, Dirk Behme wrote:
From: Dirk Behme
Starting in the wrong ELx mode I get the following debug output:
...
- Current EL 0004 -
- Xen must be entered in NS EL2 mode -
- Boot failed -
The output of "Please updat
From: Dirk Behme
Starting in the wrong ELx mode I get the following debug output:
...
- Current EL 0004 -
- Xen must be entered in NS EL2 mode -
- Boot failed -
The output of "Please update the bootloader" is missing here.
Make sure this is output, too. With this, we get
...
-
90 matches
Mail list logo
