All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Abele <will.abele@starlab.io>
To: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: Julien Grall <julien.grall@arm.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
	Will Abele <will.abele@starlab.io>
Subject: [Xen-devel] [PATCH 0/1] Dom0less guest device tree format
Date: Sat, 6 Jul 2019 18:02:34 +0000	[thread overview]
Message-ID: <cover.1562435004.git.will.abele@starlab.io> (raw)

From: Will Abele <will.abele@starlab.io>

Hi,

I've been using dom0less Xen on the Hikey 960 with a 4.14 Linux Kernel. I had
trouble getting the 4.14 Linux Kernel to boot as a dom0less domU because it was
misinterpreting the device tree version. Linux 4.14 and earlier interpret device
trees with a "/" in the root node as version 16. Xen produces a version 17
device tree, so the root node needs to be "" to work with 4.14 and earlier Linux
Kernels. Linux 4.15 and later assume that the version is 17, so this patch does
not have any impact.

Please let me know if you need any more information or have suggestions for
other ways to handle this.

Thanks,
Will

Will Abele (1):
  xen/arm: Use "" instead of "/" for domU root node.

 xen/arch/arm/domain_build.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
2.20.1 (Apple Git-117)


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

             reply	other threads:[~2019-07-06 18:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-06 18:02 Will Abele [this message]
2019-07-06 18:02 ` [Xen-devel] [PATCH 1/1] xen/arm: Use "" instead of "/" for domU root node Will Abele
2019-07-06 18:17 ` [Xen-devel] [PATCH 0/1] Dom0less guest device tree format Julien Grall
2019-07-06 18:19   ` Julien Grall
2019-07-06 21:10     ` Will Abele
2019-07-08  7:39       ` Viktor Mitin
2019-07-08 15:18       ` Julien Grall
2019-07-08 18:27         ` Will Abele
2019-07-08 22:28       ` Stefano Stabellini
2019-07-09 13:17         ` Will Abele

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=cover.1562435004.git.will.abele@starlab.io \
    --to=will.abele@starlab.io \
    --cc=Volodymyr_Babchuk@epam.com \
    --cc=julien.grall@arm.com \
    --cc=sstabellini@kernel.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.