xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: casionwoo <casionwoo@gmail.com>, xen-devel@lists.xen.org
Subject: Re: Xen ARM small task (WAS: Re: [Xen Question])
Date: Fri, 11 Nov 2016 09:46:56 +0000	[thread overview]
Message-ID: <e15ac0d4-afdd-3e45-36cf-2cf7c7e9c743@arm.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1611101813320.3491@sstabellini-ThinkPad-X260>

Hi Stefano,

On 11/11/2016 02:24, Stefano Stabellini wrote:
> On Thu, 10 Nov 2016, Julien Grall wrote:
>> (CC Stefano and change the title)
>>
>> Hello,
>>
>> On 10/11/16 12:13, casionwoo wrote:
>>> I’m pleased about your reply and you have a lot of code to clean-up.
>>>
>>> As you mentioned, It’s really huge to digest at once. Thank you for
>>> understanding me.
>>>
>>> And that’s why i need a small fix up and todo list.
>>>
>>> I feel familiar with ARM and c language and there’s no specific area yet.
>>>
>>> I think that i can find interesting area with following up the codes.
>>>
>>> I’m looking forward to being stuck on Xen.
>>>
>>> Then it would be easier for me to understand about Xen on ARM.
>>>
>>> Please let me know the TODO and bug-fix lists.
>>
>> Stefano, before giving a list of code clean-up, do you have any small TODO on
>> ARM in mind?
>
> A simple task we talked about recently is to enable the vuart
> (xen/arch/arm/vuart.c) for all guests. At the moment it is only emulated
> for Dom0, but some guests, in particular BareMetal guests
> (https://en.wikipedia.org/wiki/BareMetal), would benefit from it.
>
> It would be best to introduce an option in libxl to explicitly
> enable/disable the vuart for DomUs. Something like vuart=1 in the VM
> config file.

The vuart has not been enabled for DomU because it the UART region may 
clash with the guest memory layout (which is static).

I don't think this option should be available until we allow the guest 
to use the same memory layout as the host (see e820_host parameter for x86).

>
> BTW we should keep this up to date:
>
> https://wiki.xenproject.org/wiki/Xen_ARM_TODO

You are right, although it might be better to use the bug tracker [1] to 
stay aligned with the rest of the hypervisor.

Note that I have got a list of TODO/bugs I track myself but never 
updated the wiki.

Cheers,

[1] https://bugs.xenproject.org/xen/

-- 
Julien Grall

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

  reply	other threads:[~2016-11-11  9:46 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAMguKxbBxZ_0Za8dAUVUbz1hPT5+QfTsycZCftpi99YsJZ0+Vg@mail.gmail.com>
     [not found] ` <36d47cc0-839b-bd4d-fd73-334435e2dca1@arm.com>
2016-11-10 12:13   ` [Xen Question] casionwoo
2016-11-10 12:24     ` Xen ARM small task (WAS: Re: [Xen Question]) Julien Grall
2016-11-11  2:24       ` Stefano Stabellini
2016-11-11  9:46         ` Julien Grall [this message]
2016-11-11 16:59           ` Edgar E. Iglesias
2016-11-14  4:07             ` 유정우
2016-11-11 19:55           ` Stefano Stabellini
2016-11-14 20:12             ` Julien Grall
2016-11-17 17:26               ` Stefano Stabellini
2016-11-17 17:57                 ` Julien Grall
2016-11-18 18:58                   ` Stefano Stabellini
2016-11-21 19:50                     ` Edgar E. Iglesias
2016-11-21 21:01                       ` Stefano Stabellini
2016-11-21 21:13                         ` Edgar E. Iglesias
2016-11-21 21:24                           ` Julien Grall
2016-11-21 21:57                             ` Edgar E. Iglesias
2016-11-22 19:06                             ` Stefano Stabellini
2016-11-22 19:36                               ` Julien Grall
2016-11-23 15:10                                 ` Artem Mygaiev
2016-11-23 15:19                                   ` Julien Grall
2016-11-23 16:26                                     ` Artem Mygaiev
2016-11-23 16:38                                       ` Edgar E. Iglesias
2016-11-23 18:32                                         ` Julien Grall
2016-11-24 13:29                                           ` Edgar E. Iglesias
2016-11-23 19:55                                 ` Stefano Stabellini
2016-11-25 16:52                                   ` Julien Grall
2016-12-01  2:07                                     ` Stefano Stabellini
2016-12-01 15:47                                       ` Julien Grall
2016-12-01 21:33                                         ` Stefano Stabellini
2016-12-05 14:13                                           ` Julien Grall
2016-12-05 20:25                                             ` Stefano Stabellini
2016-12-06 16:05                                               ` 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=e15ac0d4-afdd-3e45-36cf-2cf7c7e9c743@arm.com \
    --to=julien.grall@arm.com \
    --cc=casionwoo@gmail.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).