Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2017-05-03 Thread Volodymyr Babchuk
Hello guys, I'm following the OP-TEE discussion. At [1] you can find my patch series for OP-TEE calls handling. It is very old thing, but it worked (and even had nice features like ability to handle domain crash in the middle of OP-TEE session). If you want latest version, just take a look at

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2017-05-02 Thread Julien Grall
Hi all, A quick reminder, the Community Call will be tomorrow (Wednesday 3rd May) at 5PM BST. For joining the call, please use either: Call+44 1223 406065 (Local dial in) and enter the access code below followed by # key. Participant code: 4915191 Mobile Auto Dial: VoIP:

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2017-04-20 Thread Stefano Stabellini
On Thu, 20 Apr 2017, Julien Grall wrote: > == Cross-compiling == > > Anastasios: We are looking at support Xen in Buildroot. The use case is a > small initramfs. > > Potential task: Keep Xen updated on buildroot. Anastasios could help on that. > > Stefano: Xen is compiling fine with Yocto. > >

[Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2017-04-20 Thread Julien Grall
Hi all, Below the meeting minutes for the previous Xen community call. Feel free to reply if I missed some parts. I suggest to have the next call on the 3rd May at 5PM BST. Any opinions. Also, do you have any specific topic you would like to talk during this call? Cheers, == Attendees ==

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2017-04-04 Thread Julien Grall
Hi, Quick reminder the community call will be tomorrow at 5pm BST (i.e UTC + 1). Let me know if you have any specific topic you would like to talk during this call. For joining the call, please use either: Call+44 1223 406065 (Local dial in) and enter the access code below

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2017-03-31 Thread Julien Grall
On 03/30/2017 09:17 PM, Volodymyr Babchuk wrote: Hi Julien, Hi Volodymyr, On 30 March 2017 at 22:57, Julien Grall wrote: Hi Volodymyr On 30/03/2017 20:19, Volodymyr Babchuk wrote: On 30 March 2017 at 21:52, Stefano Stabellini wrote: On

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2017-03-30 Thread Artem Mygaiev
Lets make it clear - there must be one translation table for EL0 apps... On Mar 30, 2017 23:18, Volodymyr Babchuk wrote: Hi Julien, On 30 March 2017 at 22:57, Julien Grall wrote: > Hi Volodymyr > > On 30/03/2017 20:19, Volodymyr Babchuk wrote: >>

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2017-03-30 Thread Volodymyr Babchuk
Hi Julien, On 30 March 2017 at 22:57, Julien Grall wrote: > Hi Volodymyr > > On 30/03/2017 20:19, Volodymyr Babchuk wrote: >> >> On 30 March 2017 at 21:52, Stefano Stabellini >> wrote: >>> >>> On Thu, 30 Mar 2017, Volodymyr Babchuk wrote: >> >>

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2017-03-30 Thread Julien Grall
Hi Volodymyr On 30/03/2017 20:19, Volodymyr Babchuk wrote: On 30 March 2017 at 21:52, Stefano Stabellini wrote: On Thu, 30 Mar 2017, Volodymyr Babchuk wrote: And yes, my profiler shows that there are ways to further decrease latency. Most obvious way is to get rid of

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2017-03-30 Thread Julien Grall
Hi Volodymyr On 30/03/2017 20:19, Volodymyr Babchuk wrote: On 30 March 2017 at 21:52, Stefano Stabellini wrote: On Thu, 30 Mar 2017, Volodymyr Babchuk wrote: And yes, my profiler shows that there are ways to further decrease latency. Most obvious way is to get rid of

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2017-03-30 Thread Volodymyr Babchuk
Hi Stefano, On 30 March 2017 at 21:52, Stefano Stabellini wrote: > On Thu, 30 Mar 2017, Volodymyr Babchuk wrote: >> Hi Julien, >> >> 5pm UTC+1 will be fine for me. >> >> I just finished my EL0 PoC and want to share benchmark results. >> >> My benchmark setup is primitive,

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2017-03-30 Thread Stefano Stabellini
On Thu, 30 Mar 2017, Volodymyr Babchuk wrote: > Hi Julien, > > 5pm UTC+1 will be fine for me. > > I just finished my EL0 PoC and want to share benchmark results. > > My benchmark setup is primitive, but results are reproducible. I have > wrote small driver that calls SMC 10.000.000 times in a

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2017-03-30 Thread Volodymyr Babchuk
Hi Julien, 5pm UTC+1 will be fine for me. I just finished my EL0 PoC and want to share benchmark results. My benchmark setup is primitive, but results are reproducible. I have wrote small driver that calls SMC 10.000.000 times in a loop. So, benchmark looks like this: root@xenaarch64:~# time

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2017-03-29 Thread Stefano Stabellini
On Wed, 29 Mar 2017, Julien Grall wrote: > Hi, > > On 28/03/2017 16:23, Julien Grall wrote: > > Hi all, > > > > Apologies for the late sending, you will find at the end of the e-mail a > > summary of the discussion from the previous call. Feel free to reply if I > > missed some parts. > > > > I

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2017-03-29 Thread Julien Grall
Hi, On 28/03/2017 16:23, Julien Grall wrote: Hi all, Apologies for the late sending, you will find at the end of the e-mail a summary of the discussion from the previous call. Feel free to reply if I missed some parts. I suggest to have the next call on the 5th April at 5PM UTC. Any opinions?

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2017-03-29 Thread Edgar E. Iglesias
On Tue, Mar 28, 2017 at 04:23:03PM +0100, Julien Grall wrote: > Hi all, > > Apologies for the late sending, you will find at the end of the e-mail a > summary of the discussion from the previous call. Feel free to reply if I > missed some parts. > > I suggest to have the next call on the 5th

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2017-03-29 Thread Artem Mygaiev
Hello Julien 5th works for us. We will collect topics internally and send to this thread. ARTEM MYGAIEV Director, Technology Solutions Office: +380 44 390 5457 x 65570 Cell: +380 67 921 1131 Email: artem_myga...@epam.com Kyiv, Ukraine (GMT+3) epam.com CONFIDENTIALITY CAUTION AND

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2017-03-28 Thread Stefano Stabellini
On Tue, 28 Mar 2017, Julien Grall wrote: > Hi all, > > Apologies for the late sending, you will find at the end of the e-mail a > summary of the discussion from the previous call. Feel free to reply if I > missed some parts. > > I suggest to have the next call on the 5th April at 5PM UTC. Any

[Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2017-03-28 Thread Julien Grall
Hi all, Apologies for the late sending, you will find at the end of the e-mail a summary of the discussion from the previous call. Feel free to reply if I missed some parts. I suggest to have the next call on the 5th April at 5PM UTC. Any opinions? Also do you have any specific topic you would

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2017-01-19 Thread Stefano Stabellini
On Thu, 19 Jan 2017, Pooya Keshavarzi wrote: > Hi Stefano, > > On 01/13/2017 07:39 PM, Stefano Stabellini wrote: > > On Fri, 13 Jan 2017, Pooya.Keshavarzi wrote: > >> On 01/12/2017 07:50 PM, Stefano Stabellini wrote: > >>> On Thu, 12 Jan 2017, Pooya.Keshavarzi wrote: > > Firstly sorry

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2017-01-19 Thread Pooya Keshavarzi
Hi Stefano, On 01/13/2017 07:39 PM, Stefano Stabellini wrote: > On Fri, 13 Jan 2017, Pooya.Keshavarzi wrote: >> On 01/12/2017 07:50 PM, Stefano Stabellini wrote: >>> On Thu, 12 Jan 2017, Pooya.Keshavarzi wrote: Firstly sorry for the late reply on this. Regarding the problem

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2017-01-13 Thread Stefano Stabellini
On Fri, 13 Jan 2017, Pooya.Keshavarzi wrote: > On 01/12/2017 07:50 PM, Stefano Stabellini wrote: > > On Thu, 12 Jan 2017, Pooya.Keshavarzi wrote: > >> > >> Firstly sorry for the late reply on this. > >> > >> Regarding the problem with swiotlb-xen here are some more details: > >> > >> If we limit

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2017-01-13 Thread Pooya . Keshavarzi
Dear Andrii, On 01/13/2017 11:47 AM, Andrii Anisov wrote: > > Dear Pooya, > > On our site we did not face those issues 'cause we limited dom0 memory space > to the 32-bit addressable range. Could you give it a try? Maybe there is something wrong on our side and it works for you. > BTW, it

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2017-01-13 Thread Pooya . Keshavarzi
On 01/12/2017 07:50 PM, Stefano Stabellini wrote: > On Thu, 12 Jan 2017, Pooya.Keshavarzi wrote: >> >> Firstly sorry for the late reply on this. >> >> Regarding the problem with swiotlb-xen here are some more details: >> >> If we limit Dom0's memory such that only low-memory (up to 32-bit >>

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2017-01-13 Thread Andrii Anisov
Dear Pooya, On our site we did not face those issues 'cause we limited dom0 memory space to the 32-bit addressable range. BTW, it looks you use nfs root in you setups, do you? Issues we faced and got fixes/workarounds was as following: MMC driver did not work due to dma_mmap fixed with the

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2017-01-12 Thread Stefano Stabellini
On Thu, 12 Jan 2017, Pooya.Keshavarzi wrote: > > The other issue I heard about was some root file system corruptions after > > two or three re-boots we haven't observed in the native Linux case. The > > plan was to do some further analysis, first, before we blame Xen regarding > > this, though.

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2017-01-12 Thread Pooya . Keshavarzi
Hi, On 01/03/2017 12:33 PM, Dirk Behme wrote: > On 20.12.2016 19:01, Julien Grall wrote: >> Hi Andrii, >> >> On 20/12/2016 19:00, Andrii Anisov wrote: >>> Sorry for the mess, >>> >>> I mean the xen-swiotlb issue on renesas board: >>> Bosch: problem with xen-swiotlb. It does not work properly

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2016-12-21 Thread Andrii Anisov
Hello Dirk, Except those two issues did you face some issues with PVR KM? ANDRII ANISOV Lead Systems Engineer   Office: +380 44 390 5457 x 66766   Cell: +380 50 573 8852   Email:  andrii_ani...@epam.com Kyiv, Ukraine (GMT+3)   epam.com   CONFIDENTIALITY CAUTION AND DISCLAIMER This message

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2016-12-21 Thread Dirk Behme
On 20.12.2016 19:01, Julien Grall wrote: Hi Andrii, On 20/12/2016 19:00, Andrii Anisov wrote: Sorry for the mess, I mean the xen-swiotlb issue on renesas board: Bosch: problem with xen-swiotlb. It does not work properly on renesas board. Stefano: please report the error on the ML ACTION:

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2016-12-20 Thread Konrad Rzeszutek Wilk
On Tue, Dec 20, 2016 at 08:00:27PM +0200, Andrii Anisov wrote: > Sorry for the mess, > > I mean the xen-swiotlb issue on renesas board: Can you make sure to CC me on it (since I am the maintainer of that code). > > > Bosch: problem with xen-swiotlb. It does not work properly on renesas > board.

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2016-12-20 Thread Julien Grall
Hi Andrii, On 20/12/2016 19:00, Andrii Anisov wrote: Sorry for the mess, I mean the xen-swiotlb issue on renesas board: Bosch: problem with xen-swiotlb. It does not work properly on renesas board. Stefano: please report the error on the ML ACTION: Bosch to send a bug report regarding

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2016-12-20 Thread Andrii Anisov
Sorry for the mess, I mean the xen-swiotlb issue on renesas board: > Bosch: problem with xen-swiotlb. It does not work properly on renesas board. > Stefano: please report the error on the ML > > ACTION: Bosch to send a bug report regarding xen-swiotlb -- *Andrii Anisov* *Lead Systems

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2016-12-20 Thread Andrii Anisov
Julien, Stefano, Are there any updates about: ACTION: Bosch to send a bug report regarding xen-swiotlb Edgar: IOMMU could not be used by the guest (Stage-1). This would be useful to implement driver in userspace. Julien: When will it be required? Edgar: It is a trend Any mailing

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2016-12-15 Thread Julien Grall
On 14/12/16 21:18, Edgar E. Iglesias wrote: On Wed, Dec 14, 2016 at 03:59:00PM +0100, Dario Faggioli wrote: On Tue, 2016-12-13 at 19:00 +, Julien Grall wrote: Hi all, Stefano suggested to move the call at 5pm and I haven't seen any disagreement. So the call will be tomorrow (Wednesday

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2016-12-14 Thread Edgar E. Iglesias
On Wed, Dec 14, 2016 at 03:59:00PM +0100, Dario Faggioli wrote: > On Tue, 2016-12-13 at 19:00 +, Julien Grall wrote: > > Hi all, > > > > Stefano suggested to move the call at 5pm and I haven't seen any  > > disagreement. > > > > So the call will be tomorrow (Wednesday 14th December at 5pm).

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2016-12-14 Thread Dario Faggioli
On Tue, 2016-12-13 at 19:00 +, Julien Grall wrote: > Hi all, > > Stefano suggested to move the call at 5pm and I haven't seen any  > disagreement. > > So the call will be tomorrow (Wednesday 14th December at 5pm). > Hey, I'm not sure I will be able join today. Both my interest and my

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2016-12-13 Thread Julien Grall
Hi all, Stefano suggested to move the call at 5pm and I haven't seen any disagreement. So the call will be tomorrow (Wednesday 14th December at 5pm). The conference details are the same as last time. For reminder: Use either of the following to join the call: Call+44 1223 406065

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2016-12-09 Thread Edgar E. Iglesias
On Tue, Dec 06, 2016 at 11:02:20AM -0800, Stefano Stabellini wrote: > On Tue, 6 Dec 2016, Julien Grall wrote: > > Hi all, > > > > Apologies for the late sending. You will find at the end of the mail a > > summary > > of the discussion. Feel free to reply if I missed some parts. > > > > At the

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2016-12-07 Thread Dario Faggioli
On Wed, 2016-12-07 at 19:38 +0100, Dario Faggioli wrote: >  [DOC RFC] Heterogeneous Multi Processing Support in Xen >  <1481135379.3445.142.ca...@citrix.com> > > (I wanted to post a link to the message in the archives, but I'm not > seeing it there yet... oh, well.) > It appeared:

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2016-12-07 Thread Dario Faggioli
On Tue, 2016-12-06 at 13:48 +, Julien Grall wrote: > === big.LITTLE === > > Anastassios:interested in knowing the status of big.LITTLE > support in Xen > Dario:  went through the thread on the ML. The consensus > seems to be > based on vcpu pin/affinity. >

Re: [Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2016-12-06 Thread Stefano Stabellini
On Tue, 6 Dec 2016, Julien Grall wrote: > Hi all, > > Apologies for the late sending. You will find at the end of the mail a summary > of the discussion. Feel free to reply if I missed some parts. > > At the end of the call we agreed to have another meeting before the end of the > year. Given

[Xen-devel] Xen ARM community call - meeting minutes and date for the next one

2016-12-06 Thread Julien Grall
Hi all, Apologies for the late sending. You will find at the end of the mail a summary of the discussion. Feel free to reply if I missed some parts. At the end of the call we agreed to have another meeting before the end of the year. Given that the Christmas is approaching and some people may