xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Richard Simpson <xen@huskydog.org.uk>
To: Julien Grall <julien@xen.org>,
	Bertrand Marquis <Bertrand.Marquis@arm.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>, nd <nd@arm.com>,
	Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: ARM - Successful install on RockPro64
Date: Wed, 17 Jun 2020 23:28:47 +0100	[thread overview]
Message-ID: <49e5b539-145a-726a-fb80-a93e65e44ca0@huskydog.org.uk> (raw)
In-Reply-To: <8013f2db-3732-0679-81f6-7b274b39c44f@xen.org>

Hello Julien,

I have just tried 4.14-rc2 and it seems to work fine.

I think that the most useful page regarding the board is the one for the 
Ibox3399 since this refers to the RK3399 chip which the RockPro64 uses 
(shouldn't the page actually be called RK3399 to make it more generic).

Perhaps I can most usefully record what I did by updating that page and 
making sure that the instructions work correctly. If there is additional 
stuff relevant to the RockPro64 over and above the generic RK3399 info 
then I'll give some thought to how to best record it.  I will eventually 
be writing a fuller report on my progress on my blog at 
funfoodfreedom.huskydog.org.uk.

I now need to finish automating the boot process (still requires manual 
u-boot command) and figure out how to get the console log to work.  
Currently I can either see the xen and linux kernel boot messages OR see 
the dom0 console, but not both.  I then want to wipe the install and 
start again without all the blind alleys that I went down the first time 
(mostly a function of my ignorance). This should allow me to clearly 
document what is actually required from both a Xen and Gentoo perspective.

I'll also try to more of the Xen config options to see what works and 
what is actually needed.

On one more related note:  I suspect that Xen would run on the 
PineBookPro as well as I get the impression that it uses very similar 
hardware.  Of course that would rely on the GPU etc which I haven't 
tested at all as I am using the serial console.

Finally, when I joined this mailing list I asked for a daily digest.  
However I seem to be getting a new digest every hour or so.  Is this right?

Regards,

     Richard

On 6/16/20 11:26 AM, Julien Grall wrote:
> Hello,
>
> On 16/06/2020 09:33, Richard Simpson wrote:
>> I would be happy to try to report my success via the smoke test page 
>> (https://wiki.xenproject.org/wiki/Xen_ARM_Manual_Smoke_Test/Results) 
>> if I can figure out how.  Strangely, I can't see anything listed 
>> under "Test Results" from anyone else.  Perhaps it is a problem with 
>> my browser.
> This is not a browser problem :). In the past, we did attempt to list 
> all the boards we know works on a given version of Xen. But this never 
> really gain any momentum.
>
> If there is any specific setup you need for your board (e.g. 
> non-upstream kernel, a new U-boot...), then I would suggest to create 
> a new page with steps to boot Xen the platform. You can have a look 
> how we list the other boards in [1].
>
>>
>> I also notice an instruction which reads "Test hypervisor 
>> functionalities: clone raisin on the platform and run ./raise test".  
>> I can try to do this if it will help.  Do I just run "git clone <link 
>> from web page>" and then presumably the test prints out some results?
>
> It is just meant to be an easy way to test basic functionality of Xen 
> (e.g booting a guest). You seem to have done it manually, so it should 
> be sufficient.
>
>>
>> Happy to try a beta version of Xen if you decide to include the patch 
>> and I can also try some of the interrupt config options if you want.
>
> The patch should already be included in xen 4.14-rc2. Would you mind 
> to give a spin?
>
> Best regards,
>
> [1] 
> https://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions
>


  reply	other threads:[~2020-06-17 22:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-15 22:29 ARM - Successful install on RockPro64 Richard Simpson
2020-06-16  8:03 ` Bertrand Marquis
2020-06-16  8:33   ` Richard Simpson
2020-06-16 10:26     ` Julien Grall
2020-06-17 22:28       ` Richard Simpson [this message]
2020-06-24 12:42         ` Julien Grall
2020-06-26 23:02           ` Richard Simpson
2020-06-27 20:58           ` Richard Simpson
2020-06-16 10:14   ` 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=49e5b539-145a-726a-fb80-a93e65e44ca0@huskydog.org.uk \
    --to=xen@huskydog.org.uk \
    --cc=Bertrand.Marquis@arm.com \
    --cc=julien@xen.org \
    --cc=nd@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 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).