Thank you for your attention.

>From upper emails, https://bugs.xenproject.org/xen/ this is the small TODO
list, which i follow up right?



2016-11-12 1:59 GMT+09:00 Edgar E. Iglesias <edgar.igles...@gmail.com>:

> On Fri, Nov 11, 2016 at 09:46:56AM +0000, Julien Grall wrote:
> > 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).
>
> Yes, we were thinking to give the mem layout one a try in 4.9 hopefully.
>
> Another task that is not too huge is the one to allow Xen to map in
> arbitrary memory regions as Normal Memory into domUs.
> We discussed the possibility of having additional arch specific arguments
> to the iomem settings.
>
> This is for example useful to give DomU guests direct access to on chip
> memories or to specific ranges of DRAM that may be needed to communicate
> with devices.
>
>
> >
> > >
> > >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.
>
> Good idea, I'll add some stuff into that list!
>
> Best regards,
> Edgar
>
>
>
> >
> > Cheers,
> >
> > [1] https://bugs.xenproject.org/xen/
> >
> > --
> > Julien Grall
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xen.org
> > https://lists.xen.org/xen-devel
>



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

Reply via email to