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
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:
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.
>
>
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 ==
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
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
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:
>>
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:
>>
>>
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
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
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,
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
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
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
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?
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
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
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
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
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
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
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
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
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
>>
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
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.
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
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
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:
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.
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
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
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
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
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).
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
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
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
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:
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.
>
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
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
Hello Dirk,
On 09/11/16 07:32, Dirk Behme wrote:
On 08.11.2016 13:19, Julien Grall wrote:
Hi all,
I would like to start organizing a recurring community call to discuss
and sync-up on upcoming features for Xen ARM.
Example of features that could be discussed:
- Sharing co-processor
Hello all,
Below an agenda for the call tomorrow:
* Round-table and introductions
* Features for the next release
* Stable tree maintenance
* Areas of concern
Regards,
On 18/11/16 16:07, Julien Grall wrote:
Hello all,
Based on the timezone given by each of you, the best time seems to be:
Hello all,
Based on the timezone given by each of you, the best time seems to be:
Wednesday 23rd November at 4pm UTC.
I will post an agenda beginning of next week.
Use either of the following to join the call:
Call+44 1223 406065 (Local dial in)
and enter the access code below
I will like to attend GMT -6.
Thanks,
Sameer
On 11/8/2016 5:19 AM, Julien Grall wrote:
Hi all,
I would like to start organizing a recurring community call to discuss
and sync-up on upcoming features for Xen ARM.
Example of features that could be discussed:
- Sharing co-processor between
Hi Julien, all,
> I would like to start organizing a recurring community call to discuss and
> sync-up on upcoming features for Xen ARM.
great idea, I'd like to join too (GMT).
> Example of features that could be discussed:
> - Sharing co-processor between guests
> - PCI
On 08.11.2016 13:19, Julien Grall wrote:
Hi all,
I would like to start organizing a recurring community call to discuss
and sync-up on upcoming features for Xen ARM.
Example of features that could be discussed:
- Sharing co-processor between guests
- PCI passthrough
Would it be an
On Tue, 8 Nov 2016, Julien Grall wrote:
> Hi all,
>
> I would like to start organizing a recurring community call to discuss and
> sync-up on upcoming features for Xen ARM.
>
> Example of features that could be discussed:
> - Sharing co-processor between guests
> - PCI passthrough
>
I am interested, UTC -6.
On 11/08/2016 06:19 AM, Julien Grall wrote:
> Hi all,
>
> I would like to start organizing a recurring community call to discuss
> and sync-up on upcoming features for Xen ARM.
>
> Example of features that could be discussed:
> - Sharing co-processor between guests
Please include me in the invite. Mountain time (GMT-6)
On 11/8/2016 9:56 AM, Chris Patterson wrote:
I would suggest to start with a 1 hour meeting on the Wednesday 23rd
November. I know that people are spread across different timezones, so I
would like to gather thought before choosing a
On Tue, Nov 8, 2016 at 4:19 AM, Julien Grall wrote:
> Hi all,
>
...
> I would suggest to start with a 1 hour meeting on the Wednesday 23rd
> November. I know that people are spread across different timezones, so I
> would like to gather thought before choosing a time.
I
> I would suggest to start with a 1 hour meeting on the Wednesday 23rd
> November. I know that people are spread across different timezones, so I
> would like to gather thought before choosing a time.
>
Sounds good! EST (GMT-5).
Cheers,
-Chris
___
Hello Julien,
I and Iurii Konovalenko are interesting in attending. We are in GMT+2
timezone.
With the best regards,
Iurii Mykhalskyi
On Tue, Nov 8, 2016 at 6:17 PM, Stewart Hildebrand <
stewart.hildebr...@dornerworks.com> wrote:
> Hello Julien,
>
> Yes, myself and a couple of others from
Hello Julien,
Yes, myself and a couple of others from DornerWorks are interested in
attending. We are in EST (GMT-5).
Stewart Hildebrand
Embedded Software Engineer
DornerWorks, Ltd
stewart.hildebr...@dornerworks.com
-Original Message-
From: Julien Grall [mailto:julien.gr...@arm.com]
Hi Julien,
On Tue, Nov 8, 2016 at 7:19 AM, Julien Grall wrote:
> Hi all,
>
> I would like to start organizing a recurring community call to discuss and
> sync-up on upcoming features for Xen ARM.
>
> Example of features that could be discussed:
> - Sharing
Hi Julien,
I'm interested in joining. I'm in Sweden GMT+1.
Thanks!
Edgar
On Tue, Nov 08, 2016 at 12:19:52PM +, Julien Grall wrote:
> Hi all,
>
> I would like to start organizing a recurring community call to discuss and
> sync-up on upcoming features for Xen ARM.
>
> Example of features
Hello Julien,
We will be happy to work on this. We are in GMT+2 timezone (EET).
Adding Artem Mygaiev and Oleksandr Tyshchenko who work on co-processor
sharing with me in EPAM.
Sincerely,
Andrii Anisov.
On Tue, Nov 8, 2016 at 2:19 PM, Julien Grall wrote:
> Hi all,
>
> I
Hi all,
I would like to start organizing a recurring community call to discuss
and sync-up on upcoming features for Xen ARM.
Example of features that could be discussed:
- Sharing co-processor between guests
- PCI passthrough
I would suggest to start with a 1 hour meeting on
59 matches
Mail list logo