From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: Re: RT Xen on ARM - R-Car series Date: Tue, 12 Feb 2019 20:21:10 +0100 Message-ID: References: <2a651c5d-3f94-378d-baf9-f52cab0cdc62@arm.com> <20190201165314.ofuvpddlfpzbc247@mac> <56b433e0-645e-997d-1bff-de3c4f7fe250@arm.com> <20190204125307.aft4tzkjjrxdd34o@mac> <6457d3e5-1897-d124-ba49-c6325076b393@gmail.com> <20190207103513.ky7xnftn3pj7r2lf@mac> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0639735871274902361==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Sender: "Xen-devel" To: Andrii Anisov Cc: Julien Grall , Stefano Stabellini , xen-devel@lists.xen.org, "LOPEZ, FUENTES NACARINO Jairo Eduardo" , Roger Pau Monne List-Id: xen-devel@lists.xenproject.org --===============0639735871274902361== Content-Type: multipart/alternative; boundary="000000000000e093230581b754bc" --000000000000e093230581b754bc Content-Type: text/plain; charset="UTF-8" On Tue, 12 Feb 2019, 19:21 Andrii Anisov, wrote: > Hello Julien, > Hi, Sorry for the formatting. > On 07.02.19 12:59, Julien Grall wrote: > > In that case I would prefer if we don't keep the runstate mapped. > > Actually I'm going to see runstate update impact on the context switch > time. For that I will extend TBM with runstate setup. > I really do not like a bunch of `copy_to_guest()` done on each context > switch because of runstate. Please provide more meaningful arguments other than "I don't like it". I provided potential drawbacks on my previous e-mails that you haven't yet addressed. FWIW, Volodymyr had the same argument on OP-TEE and I requested to avoid the global mapping. I haven't seen any concern for performance devredation afterwards. Please feel free to come with numbers here. If you are against runstate mapping, I'd like to fit runstate into a page, > than access it directly from the hypervisor. This is not really a policy in Xen. If the guest cares about it, it can ensure that the runstate does not cross a page boundary. Cheers, > -- > Sincerely, > Andrii Anisov. > --000000000000e093230581b754bc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Tue, 12 Feb 2019, 19= :21 Andrii Anisov, <andrii.an= isov@gmail.com> wrote:
Hello= Julien,

Hi,

=
Sorry for the formatting.


On 07.02.19 12:59, Julien Grall wrote:
> In that case I would prefer if we don't keep the runstate mapped.<= br>
Actually I'm going to see runstate update impact on the context switch = time. For that I will extend TBM with runstate setup.
I really do not like a bunch of `copy_to_guest()` done on each context swit= ch because of runstate.

Please provid= e more meaningful arguments other than "I don't like it". I p= rovided potential drawbacks on my previous e-mails that you haven't yet= addressed.

FWIW, Volodymyr had the same argument = on OP-TEE and I requested to avoid the global mapping. I haven't seen a= ny concern for performance devredation afterwards. Please feel free to come= with numbers here.

If you are against runstate mapping, I'd like to fit runstate into a pa= ge, than access it directly from the hypervisor.

This is not really a policy in= Xen. If the guest cares about it, it can ensure that the runstate does not= cross a page boundary.

Cheers,


--
Sincerely,
Andrii Anisov.
--000000000000e093230581b754bc-- --===============0639735871274902361== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVucHJvamVjdC5vcmcKaHR0cHM6Ly9saXN0 cy54ZW5wcm9qZWN0Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL3hlbi1kZXZlbA== --===============0639735871274902361==--