aboutsummaryrefslogtreecommitdiff
path: root/qemu-tech.texi
diff options
context:
space:
mode:
authorStefan Weil <weil@mail.berlios.de>2011-01-07 21:31:39 +0100
committerBlue Swirl <blauwirbel@gmail.com>2011-01-09 20:59:53 +0000
commite8dc09382289fee771999e135c05e8938900c410 (patch)
treebe108d0079e4c427703107153684c2e1af8413ee /qemu-tech.texi
parent40c5c6cd2bb2b6cc2e15fbd071dab956811f3266 (diff)
downloadqemu-arm-e8dc09382289fee771999e135c05e8938900c410.tar.gz
qemu-tech: Spelling fixes
Signed-off-by: Stefan Weil <weil@mail.berlios.de> Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
Diffstat (limited to 'qemu-tech.texi')
-rw-r--r--qemu-tech.texi4
1 files changed, 2 insertions, 2 deletions
diff --git a/qemu-tech.texi b/qemu-tech.texi
index 2e2a081d92..138e3ce9ad 100644
--- a/qemu-tech.texi
+++ b/qemu-tech.texi
@@ -516,7 +516,7 @@ timers, especially together with the use of bottom halves (BHs).
@section Hardware interrupts
In order to be faster, QEMU does not check at every basic block if an
-hardware interrupt is pending. Instead, the user must asynchrously
+hardware interrupt is pending. Instead, the user must asynchronously
call a specific function to tell that an interrupt is pending. This
function resets the chaining of the currently executing basic
block. It ensures that the execution will return soon in the main loop
@@ -548,7 +548,7 @@ Linux kernel does. The @code{sigreturn()} system call is emulated to return
from the virtual signal handler.
Some signals (such as SIGALRM) directly come from the host. Other
-signals are synthetized from the virtual CPU exceptions such as SIGFPE
+signals are synthesized from the virtual CPU exceptions such as SIGFPE
when a division by zero is done (see @code{main.c:cpu_loop()}).
The blocked signal mask is still handled by the host Linux kernel so