a5802c823f
This changeset adds functionality that allows system calls to retry without affecting thread context state such as the program counter or register values for the associated thread context (when system calls return with a retry fault). This functionality is needed to solve problems with blocking system calls in multi-process or multi-threaded simulations where information is passed between processes/threads. Blocking system calls can cause deadlock because the simulator itself is single threaded. There is only a single thread servicing the event queue which can cause deadlock if the thread hits a blocking system call instruction. To illustrate the problem, consider two processes using the producer/consumer sharing model. The processes can use file descriptors and the read and write calls to pass information to one another. If the consumer calls the blocking read system call before the producer has produced anything, the call will block the event queue (while executing the system call instruction) and deadlock the simulation. The solution implemented in this changeset is to recognize that the system calls will block and then generate a special retry fault. The fault will be sent back up through the function call chain until it is exposed to the cpu model's pipeline where the fault becomes visible. The fault will trigger the cpu model to replay the instruction at a future tick where the call has a chance to succeed without actually going into a blocking state. In subsequent patches, we recognize that a syscall will block by calling a non-blocking poll (from inside the system call implementation) and checking for events. When events show up during the poll, it signifies that the call would not have blocked and the syscall is allowed to proceed (calling an underlying host system call if necessary). If no events are returned from the poll, we generate the fault and try the instruction for the thread context at a distant tick. Note that retrying every tick is not efficient. As an aside, the simulator has some multi-threading support for the event queue, but it is not used by default and needs work. Even if the event queue was completely multi-threaded, meaning that there is a hardware thread on the host servicing a single simulator thread contexts with a 1:1 mapping between them, it's still possible to run into deadlock due to the event queue barriers on quantum boundaries. The solution of replaying at a later tick is the simplest solution and solves the problem generally.
91 lines
3.2 KiB
C++
91 lines
3.2 KiB
C++
/*
|
|
* Copyright (c) 2014 Advanced Micro Devices, Inc.
|
|
* All rights reserved.
|
|
*
|
|
* Redistribution and use in source and binary forms, with or without
|
|
* modification, are permitted provided that the following conditions are
|
|
* met: redistributions of source code must retain the above copyright
|
|
* notice, this list of conditions and the following disclaimer;
|
|
* redistributions in binary form must reproduce the above copyright
|
|
* notice, this list of conditions and the following disclaimer in the
|
|
* documentation and/or other materials provided with the distribution;
|
|
* neither the name of the copyright holders nor the names of its
|
|
* contributors may be used to endorse or promote products derived from
|
|
* this software without specific prior written permission.
|
|
*
|
|
* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
|
|
* "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
|
|
* LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
|
|
* A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
|
|
* OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
|
|
* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
|
|
* LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
|
|
* DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
|
|
* THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
|
|
* (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
|
|
* OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|
*
|
|
* Authors: Alexandru Dutu
|
|
*/
|
|
|
|
#include "arch/x86/pseudo_inst.hh"
|
|
|
|
#include "arch/x86/system.hh"
|
|
#include "cpu/thread_context.hh"
|
|
#include "debug/PseudoInst.hh"
|
|
#include "mem/se_translating_port_proxy.hh"
|
|
#include "sim/process.hh"
|
|
|
|
using namespace X86ISA;
|
|
|
|
namespace X86ISA {
|
|
|
|
/*
|
|
* This function is executed when the simulation is executing the syscall
|
|
* handler in System Emulation mode.
|
|
*/
|
|
void
|
|
m5Syscall(ThreadContext *tc)
|
|
{
|
|
DPRINTF(PseudoInst, "PseudoInst::m5Syscall()\n");
|
|
|
|
Fault fault;
|
|
tc->syscall(tc->readIntReg(INTREG_RAX), &fault);
|
|
|
|
MiscReg rflags = tc->readMiscReg(MISCREG_RFLAGS);
|
|
rflags &= ~(1 << 16);
|
|
tc->setMiscReg(MISCREG_RFLAGS, rflags);
|
|
}
|
|
|
|
/*
|
|
* This function is executed when the simulation is executing the pagefault
|
|
* handler in System Emulation mode.
|
|
*/
|
|
void
|
|
m5PageFault(ThreadContext *tc)
|
|
{
|
|
DPRINTF(PseudoInst, "PseudoInst::m5PageFault()\n");
|
|
|
|
Process *p = tc->getProcessPtr();
|
|
if (!p->fixupStackFault(tc->readMiscReg(MISCREG_CR2))) {
|
|
SETranslatingPortProxy proxy = tc->getMemProxy();
|
|
// at this point we should have 6 values on the interrupt stack
|
|
int size = 6;
|
|
uint64_t is[size];
|
|
// reading the interrupt handler stack
|
|
proxy.readBlob(ISTVirtAddr + PageBytes - size*sizeof(uint64_t),
|
|
(uint8_t *)&is, sizeof(is));
|
|
panic("Page fault at addr %#x\n\tInterrupt handler stack:\n"
|
|
"\tss: %#x\n"
|
|
"\trsp: %#x\n"
|
|
"\trflags: %#x\n"
|
|
"\tcs: %#x\n"
|
|
"\trip: %#x\n"
|
|
"\terr_code: %#x\n",
|
|
tc->readMiscReg(MISCREG_CR2),
|
|
is[5], is[4], is[3], is[2], is[1], is[0]);
|
|
}
|
|
}
|
|
|
|
} // namespace X86ISA
|