From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Mazen Ezzeddine (Student)" Subject: World-switch architected component flushing/invalidating. Date: Tue, 19 May 2015 15:23:11 +0000 Message-ID: <1432048989983.29508@mail.aub.edu> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5827798169261746170==" Return-path: Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YujMS-0000HI-IO for xen-devel@lists.xenproject.org; Tue, 19 May 2015 15:23:16 +0000 Content-Language: en-US List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: "xen-devel@lists.xenproject.org" List-Id: xen-devel@lists.xenproject.org --===============5827798169261746170== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_143204898998329508mailaubedu_" --_000_143204898998329508mailaubedu_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear all, Could you please hint me about the below: I need to flush/invalidate all architected components (all levels of D-cach= e/I-cache, I-TLB D-TLB, branch predictor etc..) on Xen world/Domain switch = running on a dual core ARM cortex A-15. As such, am I on the safe side if I include the invalidate/flush code in th= e function : static void schedule(void) { ----- ----- // code for invalidation of architected components context_switch(prev, next); } Is there a header file to include and use already-implemented xen-specific = functions for cache/TLB/branchPredictor invalidating? Could you please rout= e me to the Xen file where they are implemented. Thank you for sharing your experience. Best regards. --_000_143204898998329508mailaubedu_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Dear all,


Could you please hint me about the below:

I need to flush/invalidate all architected components (all levels of D-c= ache/I-cache, I-TLB D-TLB, branch predictor etc..) on Xen world/Domain swit= ch running on a dual core ARM cortex A-15.

As such, am I on the safe side if I include the invalidate/flush co= de in the function :

static void schedule= (void)

{

-----

-----

// code for = invalidation of architected components

context_switch(prev,= next);

}


Is there a header file t= o include and use already-implemented xen-specific functions for cache= /TLB/branchPredictor invalidating? Could you please route me to the Xen fil= e where they are implemented.


Thank you for sharing yo= ur experience.



Best regards.




--_000_143204898998329508mailaubedu_-- --===============5827798169261746170== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============5827798169261746170==--