Re: [Xen-devel] [PATCH RFC 13/18] xen: introduce and use 'dom0_rambase_pfn' setting for kernel Dom0

On Tue, May 31, 2016 at 05:04:42PM +0300, Oleksandr Dmytryshyn wrote: > On Fri, May 20, 2016 at 7:05 PM, Edgar E. Iglesias > wrote: > > Hi, > > > > We have similar needs (not exactly the same) in some of our setups. > > We need to map certain OCMs (On Chip Memories) to

Re: [Xen-devel] [PATCH RFC 13/18] xen: introduce and use 'dom0_rambase_pfn' setting for kernel Dom0

On Fri, May 20, 2016 at 7:05 PM, Edgar E. Iglesias wrote: > Hi, > > We have similar needs (not exactly the same) in some of our setups. > We need to map certain OCMs (On Chip Memories) to dom0. Among other things, > these are used to communicate with remote

Re: [Xen-devel] [PATCH RFC 13/18] xen: introduce and use 'dom0_rambase_pfn' setting for kernel Dom0

On Fri, 20 May 2016, Edgar E. Iglesias wrote: > On Fri, May 20, 2016 at 04:04:43PM +0100, Julien Grall wrote: > > Hello Oleksandr, > > > > On 20/05/16 15:19, Oleksandr Dmytryshyn wrote: > > >On Fri, May 20, 2016 at 12:59 PM, Jan Beulich wrote: > > >On 20.05.16 at 10:45,

Re: [Xen-devel] [PATCH RFC 13/18] xen: introduce and use 'dom0_rambase_pfn' setting for kernel Dom0

Hi, Edgar. On Fri, May 20, 2016 at 7:05 PM, Edgar E. Iglesias wrote: > Hi, > > We have similar needs (not exactly the same) in some of our setups. > We need to map certain OCMs (On Chip Memories) to dom0. Among other things, > these are used to communicate with remote

Re: [Xen-devel] [PATCH RFC 13/18] xen: introduce and use 'dom0_rambase_pfn' setting for kernel Dom0

On Fri, May 20, 2016 at 04:04:43PM +0100, Julien Grall wrote: > Hello Oleksandr, > > On 20/05/16 15:19, Oleksandr Dmytryshyn wrote: > >On Fri, May 20, 2016 at 12:59 PM, Jan Beulich wrote: > >On 20.05.16 at 10:45, wrote: > >>>On Thu,

Re: [Xen-devel] [PATCH RFC 13/18] xen: introduce and use 'dom0_rambase_pfn' setting for kernel Dom0

Hello Oleksandr, On 20/05/16 15:19, Oleksandr Dmytryshyn wrote: On Fri, May 20, 2016 at 12:59 PM, Jan Beulich wrote: On 20.05.16 at 10:45, wrote: On Thu, May 19, 2016 at 5:36 PM, Jan Beulich wrote: On 19.05.16 at

Re: [Xen-devel] [PATCH RFC 13/18] xen: introduce and use 'dom0_rambase_pfn' setting for kernel Dom0

On Fri, May 20, 2016 at 12:59 PM, Jan Beulich wrote: On 20.05.16 at 10:45, wrote: >> On Thu, May 19, 2016 at 5:36 PM, Jan Beulich wrote: >> On 19.05.16 at 15:58, wrote:

Re: [Xen-devel] [PATCH RFC 13/18] xen: introduce and use 'dom0_rambase_pfn' setting for kernel Dom0

>>> On 20.05.16 at 10:45, wrote: > On Thu, May 19, 2016 at 5:36 PM, Jan Beulich wrote: > On 19.05.16 at 15:58, wrote: >>> Case 1: Dom0 is driver domain: >>> There is a Ducati firmware which runs

Re: [Xen-devel] [PATCH RFC 13/18] xen: introduce and use 'dom0_rambase_pfn' setting for kernel Dom0

On Thu, May 19, 2016 at 5:36 PM, Jan Beulich wrote: On 19.05.16 at 15:58, wrote: >> Case 1: Dom0 is driver domain: >> There is a Ducati firmware which runs on dedicated M4 core and decodes >> video. This firmware uses hardcoded

Re: [Xen-devel] [PATCH RFC 13/18] xen: introduce and use 'dom0_rambase_pfn' setting for kernel Dom0

Oleksandr Dmytryshyn | Product Engineering and Development GlobalLogic M +38.067.382.2525 www.globallogic.com http://www.globallogic.com/email_disclaimer.txt On Thu, May 19, 2016 at 5:34 PM, Julien Grall wrote: > Hello Oleksandr, > > > On 19/05/16 14:58, Oleksandr

Re: [Xen-devel] [PATCH RFC 13/18] xen: introduce and use 'dom0_rambase_pfn' setting for kernel Dom0

>>> On 19.05.16 at 15:58, wrote: > Case 1: Dom0 is driver domain: > There is a Ducati firmware which runs on dedicated M4 core and decodes > video. This firmware uses hardcoded physical addresses for graphics > buffers. Those addresses should be inside

Re: [Xen-devel] [PATCH RFC 13/18] xen: introduce and use 'dom0_rambase_pfn' setting for kernel Dom0

Hello Oleksandr, On 19/05/16 14:58, Oleksandr Dmytryshyn wrote: Why would a user want to allocate DOM0 RAM bank to a specific address? If I understand correctly your patch, DOM0 will only able to allocate one bank of the given size at the specific address. You also add this possibility for

Re: [Xen-devel] [PATCH RFC 13/18] xen: introduce and use 'dom0_rambase_pfn' setting for kernel Dom0

> Why would a user want to allocate DOM0 RAM bank to a specific address? > > If I understand correctly your patch, DOM0 will only able to allocate one > bank of the given size at the specific address. You also add this possibility > for guest domain (see patch #4) and try to control where the

Re: [Xen-devel] [PATCH RFC 13/18] xen: introduce and use 'dom0_rambase_pfn' setting for kernel Dom0

Hello, On 18/05/16 17:32, Andrii Anisov wrote: From: Oleksandr Dmytryshyn This setting is used to adjust starting memory address allocated for kernel Dom0. To use 'rambase_pfn' setting just add for example 'dom0_rambase_pfn=0x8' to the hypervisor

Re: [Xen-devel] [PATCH RFC 13/18] xen: introduce and use 'dom0_rambase_pfn' setting for kernel Dom0

>>> On 19.05.16 at 14:26, wrote: > On 19/05/16 10:41, Jan Beulich wrote: > On 18.05.16 at 18:32, wrote: >>> --- a/xen/arch/arm/domain_build.c >>> +++ b/xen/arch/arm/domain_build.c >>> @@ -27,6 +27,9 @@ >>> static unsigned int __initdata

Re: [Xen-devel] [PATCH RFC 13/18] xen: introduce and use 'dom0_rambase_pfn' setting for kernel Dom0

Hi Jan, On 19/05/16 10:41, Jan Beulich wrote: On 18.05.16 at 18:32, wrote: --- a/xen/arch/arm/domain_build.c +++ b/xen/arch/arm/domain_build.c @@ -27,6 +27,9 @@ static unsigned int __initdata opt_dom0_max_vcpus; integer_param("dom0_max_vcpus",

Re: [Xen-devel] [PATCH RFC 13/18] xen: introduce and use 'dom0_rambase_pfn' setting for kernel Dom0

>>> On 18.05.16 at 18:32, wrote: > --- a/xen/arch/arm/domain_build.c > +++ b/xen/arch/arm/domain_build.c > @@ -27,6 +27,9 @@ > static unsigned int __initdata opt_dom0_max_vcpus; > integer_param("dom0_max_vcpus", opt_dom0_max_vcpus); > > +static u64 __initdata