CSCE 313 - Exam I
CSCE 313
CSCE 313
Fichier Détails
| Cartes-fiches | 13 |
|---|---|
| Langue | English |
| Catégorie | Informatique |
| Niveau | Université |
| Crée / Actualisé | 23.02.2020 / 24.02.2020 |
| Lien de web |
https://card2brain.ch/box/20200223_csce_313_exam_i
|
| Intégrer |
<iframe src="https://card2brain.ch/box/20200223_csce_313_exam_i/embed" width="780" height="150" scrolling="no" frameborder="0"></iframe>
|
Créer ou copier des fichiers d'apprentissage
Avec un upgrade tu peux créer ou copier des fichiers d'apprentissage sans limite et utiliser de nombreuses fonctions supplémentaires.
Connecte-toi pour voir toutes les cartes.
After handling a fault successfully, the CPU
goes (when it does go back) to the instruction
immediately after the faulting one.
Interrupts are asynchronous events.
Memory limit protection (within a private
address space using base and bound) is
implemented in the hardware instead of
software.
Memory limit protection checks are only
performed in the User mode
Translation Look-aside Buffer (TLB) is a
cache for popular (i.e., recently used) page
table entries.
Divide by 0 is an example of a fault.
Every process has its own page table.
A process cannot access its own page table.
Trap is a type of synchronous exception.
Faults are unintentional but possibly
recoverable.
Which of the following are privileged operations
allowed only in Kernel mode?
Which of the following are privileged operations
allowed only in Kernel mode?
Why is the process state
(i.e., PC, SP, EFLAGS, general registers)
kept in the Kernel
Interrupt Stack before handling an Interrupt?
Why could we not store it in the user memory?
What is the risk?
If the process is buggy or points to an invalid
memory address, the kernel needs to still
function properly.
It is not run on User memory, that way there is
always a dedicated amount of memory used for
OS operations, in case the user memory is filled
up with other processes.
-
- 1 / 13
-
