------------------------------------------------------------------------------
------------------------------------------------------------------------------
-- Cheddar is a GNU GPL real-time scheduling analysis tool.
-- This program provides services to automatically check schedulability and
-- other performance criteria of real-time architecture models.
--
-- Copyright (C) 2002-2023, Frank Singhoff, Alain Plantec, Jerome Legrand,
--                          Hai Nam Tran, Stephane Rubini
--
-- The Cheddar project was started in 2002 by
-- Frank Singhoff, Lab-STICC UMR 6285, Université de Bretagne Occidentale
--
-- Cheddar has been published in the "Agence de Protection des Programmes/France" in 2008.
-- Since 2008, Ellidiss technologies also contributes to the development of
-- Cheddar and provides industrial support.
--
-- The full list of contributors and sponsors can be found in README.md
--
-- This program is free software; you can redistribute it and/or modify
-- it under the terms of the GNU General Public License as published by
-- the Free Software Foundation; either version 2 of the License, or
-- (at your option) any later version.
--
-- This program is distributed in the hope that it will be useful,
-- but WITHOUT ANY WARRANTY; without even the implied warranty of
-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-- GNU General Public License for more details.
--
-- You should have received a copy of the GNU General Public License
-- along with this program; if not, write to the Free Software
-- Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
--
--
-- Contact : cheddar@listes.univ-brest.fr
--
------------------------------------------------------------------------------
-- Last update :
--    $Rev$
--    $Date$
--    $Author$
------------------------------------------------------------------------------
------------------------------------------------------------------------------

with systems; use systems;

package multicore_analysis is

-- calcul temps de blocage min et max pour un emetteur
--   ordo emetteur : le WCET d un emetteur doit etre augmenter
--                   de ce temps de blocage
-- calcul latence d'un message max et min
-- le recepteur va etre reveille avec un offset min et max 
 teur va etre reveille avec un offset min et max 
--   correspondant au temps que le dispatcher rend disponible le message
--  ordo recepteur : il a la période du dispatcheur ou une periode multiple du dispatcheur
--          le recepteur est reveille avec un offset max et/ou min correspondant au temps de livraison du message
--                est ce sustainable cote emetteur et recepteur ???


   procedure compute_icq_latencies
     (a_system      : in  system);

end multicore_analysis;