<?xml version="1.0" encoding="UTF-8"?>
<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
  <responseDate>2026-07-20T05:09:22Z</responseDate>
  <request identifier="676" metadataPrefix="oai_dc" verb="GetRecord">https://drops.dagstuhl.de/oai</request>
  <GetRecord>
    <record>
      <header>
        <identifier>oai:drops-oai.dagstuhl.de:676</identifier>
        <datestamp>2024-03-06T10:28:23Z</datestamp>
        <setSpec>ddc:004</setSpec>
        <setSpec>open_access</setSpec>
      </header>
      <metadata>
        <oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
          <dc:title>A Framework for the Busy Time Calculation of Multiple Correlated Events</dc:title>
          <dc:creator>Schliecker, Simon</dc:creator>
          <dc:creator>Ivers, Matthias</dc:creator>
          <dc:creator>Staschulat, Jan</dc:creator>
          <dc:creator>Ernst, Rolf</dc:creator>
          <dc:subject>Response time analysis</dc:subject>
          <dc:subject>multiple memory accesses</dc:subject>
          <dc:subject>multiprocessor</dc:subject>
          <dc:subject>hard real-time</dc:subject>
          <dc:subject>busy time</dc:subject>
          <dc:description>Many approaches to determine the response time of a&#13;
task have difficulty to model tasks with multiple memory&#13;
or coprocessor accesses with variable access times during&#13;
the execution. As the request times highly depend on system&#13;
setup and state, they can not be trivially bounded. If&#13;
they are bounded by a constant value, large discrepancies&#13;
between average and worst case make the focus on single&#13;
worst cases vulnerable to overestimation.&#13;
&#13;
We present a novel approach to include remote busy time&#13;
in the execution time analysis of tasks. We determine the&#13;
time for multiple requests by a task efficiently and and far&#13;
less conservative than previous approaches. These requests&#13;
may be disturbed by other events in the system. We show&#13;
how to integrate such a multiple event busy time analysis to&#13;
take into account behavior of tasks that voluntarily suspend&#13;
themselves and require multiple data from remote parts of&#13;
the system.</dc:description>
          <dc:publisher>Schloss Dagstuhl – Leibniz-Zentrum für Informatik</dc:publisher>
          <dc:contributor>Simon Schliecker and Matthias Ivers and Jan Staschulat and Rolf Ernst</dc:contributor>
          <dc:date>2006</dc:date>
          <dc:relation>Is Part Of OASIcs, Volume 4, 6th International Workshop on Worst-Case Execution Time Analysis (WCET'06) (2006)</dc:relation>
          <dc:type>InProceedings</dc:type>
          <dc:type>Text</dc:type>
          <dc:type>doc-type:ResearchArticle</dc:type>
          <dc:type>publishedVersion</dc:type>
          <dc:format>application/pdf</dc:format>
          <dc:identifier>doi:10.4230/OASIcs.WCET.2006.676</dc:identifier>
          <dc:identifier>urn:nbn:de:0030-drops-6767</dc:identifier>
          <dc:identifier>https://drops.dagstuhl.de/entities/document/10.4230/OASIcs.WCET.2006.676</dc:identifier>
          <dc:language>eng</dc:language>
          <dc:rights>https://creativecommons.org/licenses/by-nc-nd/3.0/legalcode</dc:rights>
        </oai_dc:dc>
      </metadata>
    </record>
  </GetRecord>
</OAI-PMH>
