[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Xen ARM small task (WAS: Re: [Xen Question])
On Fri, 11 Nov 2016, 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). Actually there is no reason for the vuart to use the same address as the physical uart on the platform, is there? In fact it doesn't even have to prentend to be the same uart as the one on the board, right? The vuart MMIO address could be completely configurable and independent from the one of the physical uart. > > 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. I agree that we should all use the same tool, but I didn't realize there has been a decision on using the bug tracker for this. In fact it doesn't seem to be much used at the moment. Maybe we should start a good old bikeshedding thread with other maintainers on what we should use. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx https://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |