From: Andrii Anisov <Andrii_Anisov@epam.com>
To: "Pooya.Keshavarzi" <Pooya.Keshavarzi@de.bosch.com>,
Dirk Behme <dirk.behme@de.bosch.com>,
Julien Grall <julien.grall@arm.com>,
Stefano Stabellini <sstabellini@kernel.org>
Cc: Artem Mygaiev <Artem_Mygaiev@epam.com>,
"Edgar E. Iglesias" <edgar.iglesias@xilinx.com>,
Lars Kurth <lars.kurth@citrix.com>,
Dario Faggioli <dario.faggioli@citrix.com>,
Andrii Anisov <andrii.anisov@gmail.com>,
Alex Agizim <Alex_Agizim@epam.com>,
"anastassios.nanos@onapp.com" <anastassios.nanos@onapp.com>,
Meng Xu <mengxu@seas.upenn.edu>,
"stewart.hildebrand@dornerworks.com"
<Stewart.Hildebrand@dornerworks.com>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
Xen Devel <xen-devel@lists.xen.org>
Subject: Re: Xen ARM community call - meeting minutes and date for the next one
Date: Fri, 13 Jan 2017 10:47:54 +0000 [thread overview]
Message-ID: <VI1PR03MB1631D758CF1FFD5CC2F1DDB3E6780@VI1PR03MB1631.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <e8043026-a45f-1952-8316-0b3943cee35e@de.bosch.com>
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 code similar to https://lists.xenproject.org/archives/html/xen-devel/2017-01/msg00874.html
PVR KM suffered from two issues fixed by https://lists.xenproject.org/archives/html/xen-devel/2017-01/msg00873.html and https://github.com/xen-troops/pvr_km/commit/b413e02af3df6e69afc4070a247fa740e32819ba
ANDRII ANISOV
Lead Systems Engineer
Office: +380 44 390 5457 x 66766 Cell: +380 50 573 8852 Email: andrii_anisov@epam.com
Kyiv, Ukraine (GMT+3) epam.com
CONFIDENTIALITY CAUTION AND DISCLAIMER
This message is intended only for the use of the individual(s) or entity(ies) to which it is addressed and contains information that is legally privileged and confidential. If you are not the intended recipient, or the person responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. All unintended recipients are obliged to delete this message and destroy any printed copies.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-01-13 10:47 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 13:48 Xen ARM community call - meeting minutes and date for the next one Julien Grall
2016-12-06 19:02 ` Stefano Stabellini
2016-12-09 14:12 ` Edgar E. Iglesias
2016-12-07 18:38 ` Dario Faggioli
2016-12-07 19:15 ` Dario Faggioli
2016-12-13 19:00 ` Julien Grall
2016-12-14 14:59 ` Dario Faggioli
2016-12-14 21:18 ` Edgar E. Iglesias
2016-12-15 13:38 ` Julien Grall
2016-12-20 17:45 ` Andrii Anisov
2016-12-20 18:00 ` Andrii Anisov
2016-12-20 18:01 ` Julien Grall
2016-12-21 8:12 ` Dirk Behme
2016-12-21 9:00 ` Andrii Anisov
[not found] ` <2a5febf2-31c2-9002-55c9-b39e809f01f0@de.bosch.com>
2017-01-12 15:39 ` Pooya.Keshavarzi
2017-01-12 18:50 ` Stefano Stabellini
2017-01-13 15:05 ` Pooya.Keshavarzi
2017-01-13 18:39 ` Stefano Stabellini
2017-01-19 14:59 ` Pooya Keshavarzi
2017-01-19 18:30 ` Stefano Stabellini
2017-01-13 10:47 ` Andrii Anisov [this message]
2017-01-13 15:24 ` Pooya.Keshavarzi
2016-12-20 18:36 ` Konrad Rzeszutek Wilk
2017-03-28 15:23 Julien Grall
2017-03-28 16:40 ` Stefano Stabellini
2017-03-29 8:47 ` Artem Mygaiev
2017-03-29 10:06 ` Edgar E. Iglesias
2017-03-29 21:48 ` Julien Grall
2017-03-29 21:53 ` Stefano Stabellini
2017-03-30 15:41 ` Volodymyr Babchuk
2017-03-30 18:52 ` Stefano Stabellini
2017-03-30 19:19 ` Volodymyr Babchuk
2017-03-30 19:57 ` Julien Grall
2017-03-30 20:17 ` Volodymyr Babchuk
2017-03-31 10:08 ` Julien Grall
2017-03-30 19:58 ` Julien Grall
2017-04-04 11:25 ` Julien Grall
2017-03-30 20:24 Artem Mygaiev
2017-04-20 16:44 Julien Grall
2017-04-20 22:32 ` Stefano Stabellini
2017-05-02 18:00 ` Julien Grall
2017-05-03 16:50 ` Volodymyr Babchuk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=VI1PR03MB1631D758CF1FFD5CC2F1DDB3E6780@VI1PR03MB1631.eurprd03.prod.outlook.com \
--to=andrii_anisov@epam.com \
--cc=Alex_Agizim@epam.com \
--cc=Artem_Mygaiev@epam.com \
--cc=Pooya.Keshavarzi@de.bosch.com \
--cc=Stewart.Hildebrand@dornerworks.com \
--cc=anastassios.nanos@onapp.com \
--cc=andrii.anisov@gmail.com \
--cc=dario.faggioli@citrix.com \
--cc=dirk.behme@de.bosch.com \
--cc=edgar.iglesias@gmail.com \
--cc=edgar.iglesias@xilinx.com \
--cc=julien.grall@arm.com \
--cc=lars.kurth@citrix.com \
--cc=mengxu@seas.upenn.edu \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.