iio: imu: mpu6050: Fix name/chip_id when using ACPI
[deliverable/linux.git] / drivers / lguest / interrupts_and_traps.c
CommitLineData
2e04ef76
RR
1/*P:800
2 * Interrupts (traps) are complicated enough to earn their own file.
f938d2c8
RR
3 * There are three classes of interrupts:
4 *
5 * 1) Real hardware interrupts which occur while we're running the Guest,
6 * 2) Interrupts for virtual devices attached to the Guest, and
7 * 3) Traps and faults from the Guest.
8 *
9 * Real hardware interrupts must be delivered to the Host, not the Guest.
10 * Virtual interrupts must be delivered to the Guest, but we make them look
11 * just like real hardware would deliver them. Traps from the Guest can be set
12 * up to go directly back into the Guest, but sometimes the Host wants to see
13 * them first, so we also have a way of "reflecting" them into the Guest as if
2e04ef76
RR
14 * they had been delivered to it directly.
15:*/
d7e28ffe 16#include <linux/uaccess.h>
c18acd73
RR
17#include <linux/interrupt.h>
18#include <linux/module.h>
d43c36dc 19#include <linux/sched.h>
d7e28ffe
RR
20#include "lg.h"
21
c18acd73 22/* Allow Guests to use a non-128 (ie. non-Linux) syscall trap. */
f435e68f 23static unsigned int syscall_vector = IA32_SYSCALL_VECTOR;
c18acd73
RR
24module_param(syscall_vector, uint, 0444);
25
bff672e6 26/* The address of the interrupt handler is split into two bits: */
d7e28ffe
RR
27static unsigned long idt_address(u32 lo, u32 hi)
28{
29 return (lo & 0x0000FFFF) | (hi & 0xFFFF0000);
30}
31
2e04ef76
RR
32/*
33 * The "type" of the interrupt handler is a 4 bit field: we only support a
34 * couple of types.
35 */
d7e28ffe
RR
36static int idt_type(u32 lo, u32 hi)
37{
38 return (hi >> 8) & 0xF;
39}
40
bff672e6 41/* An IDT entry can't be used unless the "present" bit is set. */
df1693ab 42static bool idt_present(u32 lo, u32 hi)
d7e28ffe
RR
43{
44 return (hi & 0x8000);
45}
46
2e04ef76
RR
47/*
48 * We need a helper to "push" a value onto the Guest's stack, since that's a
49 * big part of what delivering an interrupt does.
50 */
382ac6b3 51static void push_guest_stack(struct lg_cpu *cpu, unsigned long *gstack, u32 val)
d7e28ffe 52{
bff672e6 53 /* Stack grows upwards: move stack then write value. */
d7e28ffe 54 *gstack -= 4;
382ac6b3 55 lgwrite(cpu, *gstack, u32, val);
d7e28ffe
RR
56}
57
2e04ef76 58/*H:210
3eebd233
RR
59 * The push_guest_interrupt_stack() routine saves Guest state on the stack for
60 * an interrupt or trap. The mechanics of delivering traps and interrupts to
61 * the Guest are the same, except some traps have an "error code" which gets
62 * pushed onto the stack as well: the caller tells us if this is one.
bff672e6
RR
63 *
64 * We set up the stack just like the CPU does for a real interrupt, so it's
65 * identical for the Guest (and the standard "iret" instruction will undo
2e04ef76
RR
66 * it).
67 */
3eebd233 68static void push_guest_interrupt_stack(struct lg_cpu *cpu, bool has_err)
d7e28ffe 69{
47436aa4 70 unsigned long gstack, origstack;
d7e28ffe 71 u32 eflags, ss, irq_enable;
47436aa4 72 unsigned long virtstack;
d7e28ffe 73
2e04ef76
RR
74 /*
75 * There are two cases for interrupts: one where the Guest is already
bff672e6 76 * in the kernel, and a more complex one where the Guest is in
2e04ef76
RR
77 * userspace. We check the privilege level to find out.
78 */
a53a35a8 79 if ((cpu->regs->ss&0x3) != GUEST_PL) {
2e04ef76
RR
80 /*
81 * The Guest told us their kernel stack with the SET_STACK
82 * hypercall: both the virtual address and the segment.
83 */
4665ac8e
GOC
84 virtstack = cpu->esp1;
85 ss = cpu->ss1;
47436aa4 86
1713608f 87 origstack = gstack = guest_pa(cpu, virtstack);
2e04ef76
RR
88 /*
89 * We push the old stack segment and pointer onto the new
bff672e6
RR
90 * stack: when the Guest does an "iret" back from the interrupt
91 * handler the CPU will notice they're dropping privilege
2e04ef76
RR
92 * levels and expect these here.
93 */
382ac6b3
GOC
94 push_guest_stack(cpu, &gstack, cpu->regs->ss);
95 push_guest_stack(cpu, &gstack, cpu->regs->esp);
d7e28ffe 96 } else {
bff672e6 97 /* We're staying on the same Guest (kernel) stack. */
a53a35a8
GOC
98 virtstack = cpu->regs->esp;
99 ss = cpu->regs->ss;
47436aa4 100
1713608f 101 origstack = gstack = guest_pa(cpu, virtstack);
d7e28ffe
RR
102 }
103
2e04ef76
RR
104 /*
105 * Remember that we never let the Guest actually disable interrupts, so
bff672e6 106 * the "Interrupt Flag" bit is always set. We copy that bit from the
e1e72965 107 * Guest's "irq_enabled" field into the eflags word: we saw the Guest
2e04ef76
RR
108 * copy it back in "lguest_iret".
109 */
a53a35a8 110 eflags = cpu->regs->eflags;
382ac6b3 111 if (get_user(irq_enable, &cpu->lg->lguest_data->irq_enabled) == 0
e5faff45
RR
112 && !(irq_enable & X86_EFLAGS_IF))
113 eflags &= ~X86_EFLAGS_IF;
d7e28ffe 114
2e04ef76
RR
115 /*
116 * An interrupt is expected to push three things on the stack: the old
bff672e6 117 * "eflags" word, the old code segment, and the old instruction
2e04ef76
RR
118 * pointer.
119 */
382ac6b3
GOC
120 push_guest_stack(cpu, &gstack, eflags);
121 push_guest_stack(cpu, &gstack, cpu->regs->cs);
122 push_guest_stack(cpu, &gstack, cpu->regs->eip);
d7e28ffe 123
bff672e6 124 /* For the six traps which supply an error code, we push that, too. */
d7e28ffe 125 if (has_err)
382ac6b3 126 push_guest_stack(cpu, &gstack, cpu->regs->errcode);
d7e28ffe 127
3eebd233 128 /* Adjust the stack pointer and stack segment. */
a53a35a8
GOC
129 cpu->regs->ss = ss;
130 cpu->regs->esp = virtstack + (gstack - origstack);
3eebd233
RR
131}
132
133/*
134 * This actually makes the Guest start executing the given interrupt/trap
135 * handler.
136 *
137 * "lo" and "hi" are the two parts of the Interrupt Descriptor Table for this
138 * interrupt or trap. It's split into two parts for traditional reasons: gcc
139 * on i386 used to be frightened by 64 bit numbers.
140 */
141static void guest_run_interrupt(struct lg_cpu *cpu, u32 lo, u32 hi)
142{
143 /* If we're already in the kernel, we don't change stacks. */
144 if ((cpu->regs->ss&0x3) != GUEST_PL)
145 cpu->regs->ss = cpu->esp1;
146
147 /*
148 * Set the code segment and the address to execute.
149 */
a53a35a8
GOC
150 cpu->regs->cs = (__KERNEL_CS|GUEST_PL);
151 cpu->regs->eip = idt_address(lo, hi);
d7e28ffe 152
98fb4e5e
RR
153 /*
154 * Trapping always clears these flags:
155 * TF: Trap flag
156 * VM: Virtual 8086 mode
157 * RF: Resume
158 * NT: Nested task.
159 */
160 cpu->regs->eflags &=
161 ~(X86_EFLAGS_TF|X86_EFLAGS_VM|X86_EFLAGS_RF|X86_EFLAGS_NT);
162
2e04ef76
RR
163 /*
164 * There are two kinds of interrupt handlers: 0xE is an "interrupt
165 * gate" which expects interrupts to be disabled on entry.
166 */
d7e28ffe 167 if (idt_type(lo, hi) == 0xE)
382ac6b3
GOC
168 if (put_user(0, &cpu->lg->lguest_data->irq_enabled))
169 kill_guest(cpu, "Disabling interrupts");
d7e28ffe
RR
170}
171
3eebd233
RR
172/* This restores the eflags word which was pushed on the stack by a trap */
173static void restore_eflags(struct lg_cpu *cpu)
174{
175 /* This is the physical address of the stack. */
176 unsigned long stack_pa = guest_pa(cpu, cpu->regs->esp);
177
178 /*
179 * Stack looks like this:
180 * Address Contents
181 * esp EIP
182 * esp + 4 CS
183 * esp + 8 EFLAGS
184 */
185 cpu->regs->eflags = lgread(cpu, stack_pa + 8, u32);
186 cpu->regs->eflags &=
187 ~(X86_EFLAGS_TF|X86_EFLAGS_VM|X86_EFLAGS_RF|X86_EFLAGS_NT);
188}
189
e1e72965 190/*H:205
bff672e6
RR
191 * Virtual Interrupts.
192 *
abd41f03
RR
193 * interrupt_pending() returns the first pending interrupt which isn't blocked
194 * by the Guest. It is called before every entry to the Guest, and just before
2e04ef76
RR
195 * we go to sleep when the Guest has halted itself.
196 */
a32a8813 197unsigned int interrupt_pending(struct lg_cpu *cpu, bool *more)
d7e28ffe
RR
198{
199 unsigned int irq;
200 DECLARE_BITMAP(blk, LGUEST_IRQS);
d7e28ffe 201
bff672e6 202 /* If the Guest hasn't even initialized yet, we can do nothing. */
382ac6b3 203 if (!cpu->lg->lguest_data)
abd41f03 204 return LGUEST_IRQS;
d7e28ffe 205
2e04ef76
RR
206 /*
207 * Take our "irqs_pending" array and remove any interrupts the Guest
208 * wants blocked: the result ends up in "blk".
209 */
382ac6b3 210 if (copy_from_user(&blk, cpu->lg->lguest_data->blocked_interrupts,
d7e28ffe 211 sizeof(blk)))
abd41f03 212 return LGUEST_IRQS;
177e449d 213 bitmap_andnot(blk, cpu->irqs_pending, blk, LGUEST_IRQS);
d7e28ffe 214
bff672e6 215 /* Find the first interrupt. */
d7e28ffe 216 irq = find_first_bit(blk, LGUEST_IRQS);
a32a8813 217 *more = find_next_bit(blk, LGUEST_IRQS, irq+1);
abd41f03
RR
218
219 return irq;
220}
221
2e04ef76
RR
222/*
223 * This actually diverts the Guest to running an interrupt handler, once an
224 * interrupt has been identified by interrupt_pending().
225 */
a32a8813 226void try_deliver_interrupt(struct lg_cpu *cpu, unsigned int irq, bool more)
abd41f03
RR
227{
228 struct desc_struct *idt;
229
230 BUG_ON(irq >= LGUEST_IRQS);
d7e28ffe 231
bff672e6 232 /* If they're halted, interrupts restart them. */
66686c2a 233 if (cpu->halted) {
d7e28ffe 234 /* Re-enable interrupts. */
382ac6b3
GOC
235 if (put_user(X86_EFLAGS_IF, &cpu->lg->lguest_data->irq_enabled))
236 kill_guest(cpu, "Re-enabling interrupts");
66686c2a 237 cpu->halted = 0;
d7e28ffe 238 } else {
bff672e6 239 /* Otherwise we check if they have interrupts disabled. */
d7e28ffe 240 u32 irq_enabled;
382ac6b3 241 if (get_user(irq_enabled, &cpu->lg->lguest_data->irq_enabled))
d7e28ffe 242 irq_enabled = 0;
a32a8813
RR
243 if (!irq_enabled) {
244 /* Make sure they know an IRQ is pending. */
245 put_user(X86_EFLAGS_IF,
246 &cpu->lg->lguest_data->irq_pending);
d7e28ffe 247 return;
a32a8813 248 }
d7e28ffe
RR
249 }
250
2e04ef76
RR
251 /*
252 * Look at the IDT entry the Guest gave us for this interrupt. The
bff672e6 253 * first 32 (FIRST_EXTERNAL_VECTOR) entries are for traps, so we skip
2e04ef76
RR
254 * over them.
255 */
fc708b3e 256 idt = &cpu->arch.idt[FIRST_EXTERNAL_VECTOR+irq];
bff672e6 257 /* If they don't have a handler (yet?), we just ignore it */
d7e28ffe 258 if (idt_present(idt->a, idt->b)) {
bff672e6 259 /* OK, mark it no longer pending and deliver it. */
177e449d 260 clear_bit(irq, cpu->irqs_pending);
3eebd233 261
2e04ef76 262 /*
3eebd233
RR
263 * They may be about to iret, where they asked us never to
264 * deliver interrupts. In this case, we can emulate that iret
265 * then immediately deliver the interrupt. This is basically
266 * a noop: the iret would pop the interrupt frame and restore
267 * eflags, and then we'd set it up again. So just restore the
268 * eflags word and jump straight to the handler in this case.
269 *
270 * Denys Vlasenko points out that this isn't quite right: if
271 * the iret was returning to userspace, then that interrupt
272 * would reset the stack pointer (which the Guest told us
273 * about via LHCALL_SET_STACK). But unless the Guest is being
274 * *really* weird, that will be the same as the current stack
275 * anyway.
2e04ef76 276 */
3eebd233
RR
277 if (cpu->regs->eip == cpu->lg->noirq_iret) {
278 restore_eflags(cpu);
279 } else {
280 /*
281 * set_guest_interrupt() takes a flag to say whether
282 * this interrupt pushes an error code onto the stack
283 * as well: virtual interrupts never do.
284 */
285 push_guest_interrupt_stack(cpu, false);
286 }
287 /* Actually make Guest cpu jump to handler. */
288 guest_run_interrupt(cpu, idt->a, idt->b);
d7e28ffe 289 }
6c8dca5d 290
2e04ef76
RR
291 /*
292 * Every time we deliver an interrupt, we update the timestamp in the
6c8dca5d
RR
293 * Guest's lguest_data struct. It would be better for the Guest if we
294 * did this more often, but it can actually be quite slow: doing it
295 * here is a compromise which means at least it gets updated every
2e04ef76
RR
296 * timer interrupt.
297 */
382ac6b3 298 write_timestamp(cpu);
a32a8813 299
2e04ef76
RR
300 /*
301 * If there are no other interrupts we want to deliver, clear
302 * the pending flag.
303 */
a32a8813
RR
304 if (!more)
305 put_user(0, &cpu->lg->lguest_data->irq_pending);
d7e28ffe 306}
9f155a9b
RR
307
308/* And this is the routine when we want to set an interrupt for the Guest. */
309void set_interrupt(struct lg_cpu *cpu, unsigned int irq)
310{
2e04ef76
RR
311 /*
312 * Next time the Guest runs, the core code will see if it can deliver
313 * this interrupt.
314 */
9f155a9b
RR
315 set_bit(irq, cpu->irqs_pending);
316
2e04ef76
RR
317 /*
318 * Make sure it sees it; it might be asleep (eg. halted), or running
319 * the Guest right now, in which case kick_process() will knock it out.
320 */
9f155a9b
RR
321 if (!wake_up_process(cpu->tsk))
322 kick_process(cpu->tsk);
323}
c18acd73
RR
324/*:*/
325
2e04ef76
RR
326/*
327 * Linux uses trap 128 for system calls. Plan9 uses 64, and Ron Minnich sent
c18acd73
RR
328 * me a patch, so we support that too. It'd be a big step for lguest if half
329 * the Plan 9 user base were to start using it.
330 *
331 * Actually now I think of it, it's possible that Ron *is* half the Plan 9
2e04ef76
RR
332 * userbase. Oh well.
333 */
c18acd73
RR
334static bool could_be_syscall(unsigned int num)
335{
f435e68f
IM
336 /* Normal Linux IA32_SYSCALL_VECTOR or reserved vector? */
337 return num == IA32_SYSCALL_VECTOR || num == syscall_vector;
c18acd73
RR
338}
339
340/* The syscall vector it wants must be unused by Host. */
341bool check_syscall_vector(struct lguest *lg)
342{
343 u32 vector;
344
345 if (get_user(vector, &lg->lguest_data->syscall_vec))
346 return false;
347
348 return could_be_syscall(vector);
349}
350
351int init_interrupts(void)
352{
353 /* If they want some strange system call vector, reserve it now */
f435e68f 354 if (syscall_vector != IA32_SYSCALL_VECTOR) {
b77b881f
YL
355 if (test_bit(syscall_vector, used_vectors) ||
356 vector_used_by_percpu_irq(syscall_vector)) {
357 printk(KERN_ERR "lg: couldn't reserve syscall %u\n",
358 syscall_vector);
359 return -EBUSY;
360 }
361 set_bit(syscall_vector, used_vectors);
c18acd73 362 }
b77b881f 363
c18acd73
RR
364 return 0;
365}
366
367void free_interrupts(void)
368{
f435e68f 369 if (syscall_vector != IA32_SYSCALL_VECTOR)
c18acd73
RR
370 clear_bit(syscall_vector, used_vectors);
371}
d7e28ffe 372
2e04ef76
RR
373/*H:220
374 * Now we've got the routines to deliver interrupts, delivering traps like
a6bd8e13 375 * page fault is easy. The only trick is that Intel decided that some traps
2e04ef76
RR
376 * should have error codes:
377 */
df1693ab 378static bool has_err(unsigned int trap)
d7e28ffe
RR
379{
380 return (trap == 8 || (trap >= 10 && trap <= 14) || trap == 17);
381}
382
bff672e6 383/* deliver_trap() returns true if it could deliver the trap. */
df1693ab 384bool deliver_trap(struct lg_cpu *cpu, unsigned int num)
d7e28ffe 385{
2e04ef76
RR
386 /*
387 * Trap numbers are always 8 bit, but we set an impossible trap number
388 * for traps inside the Switcher, so check that here.
389 */
fc708b3e 390 if (num >= ARRAY_SIZE(cpu->arch.idt))
df1693ab 391 return false;
d7e28ffe 392
2e04ef76
RR
393 /*
394 * Early on the Guest hasn't set the IDT entries (or maybe it put a
395 * bogus one in): if we fail here, the Guest will be killed.
396 */
fc708b3e 397 if (!idt_present(cpu->arch.idt[num].a, cpu->arch.idt[num].b))
df1693ab 398 return false;
3eebd233
RR
399 push_guest_interrupt_stack(cpu, has_err(num));
400 guest_run_interrupt(cpu, cpu->arch.idt[num].a,
401 cpu->arch.idt[num].b);
df1693ab 402 return true;
d7e28ffe
RR
403}
404
2e04ef76
RR
405/*H:250
406 * Here's the hard part: returning to the Host every time a trap happens
bff672e6 407 * and then calling deliver_trap() and re-entering the Guest is slow.
e1e72965
RR
408 * Particularly because Guest userspace system calls are traps (usually trap
409 * 128).
bff672e6
RR
410 *
411 * So we'd like to set up the IDT to tell the CPU to deliver traps directly
412 * into the Guest. This is possible, but the complexities cause the size of
413 * this file to double! However, 150 lines of code is worth writing for taking
414 * system calls down from 1750ns to 270ns. Plus, if lguest didn't do it, all
e1e72965 415 * the other hypervisors would beat it up at lunchtime.
bff672e6 416 *
56adbe9d 417 * This routine indicates if a particular trap number could be delivered
2e04ef76
RR
418 * directly.
419 */
df1693ab 420static bool direct_trap(unsigned int num)
d7e28ffe 421{
2e04ef76
RR
422 /*
423 * Hardware interrupts don't go to the Guest at all (except system
424 * call).
425 */
c18acd73 426 if (num >= FIRST_EXTERNAL_VECTOR && !could_be_syscall(num))
df1693ab 427 return false;
d7e28ffe 428
2e04ef76
RR
429 /*
430 * The Host needs to see page faults (for shadow paging and to save the
bff672e6 431 * fault address), general protection faults (in/out emulation) and
6d7a5d1e 432 * device not available (TS handling) and of course, the hypercall trap.
2e04ef76 433 */
6d7a5d1e 434 return num != 14 && num != 13 && num != 7 && num != LGUEST_TRAP_ENTRY;
d7e28ffe 435}
f56a384e
RR
436/*:*/
437
2e04ef76
RR
438/*M:005
439 * The Guest has the ability to turn its interrupt gates into trap gates,
f56a384e
RR
440 * if it is careful. The Host will let trap gates can go directly to the
441 * Guest, but the Guest needs the interrupts atomically disabled for an
2f921b5b
RR
442 * interrupt gate. The Host could provide a mechanism to register more
443 * "no-interrupt" regions, and the Guest could point the trap gate at
444 * instructions within that region, where it can safely disable interrupts.
2e04ef76 445 */
f56a384e 446
2e04ef76
RR
447/*M:006
448 * The Guests do not use the sysenter (fast system call) instruction,
f56a384e
RR
449 * because it's hardcoded to enter privilege level 0 and so can't go direct.
450 * It's about twice as fast as the older "int 0x80" system call, so it might
451 * still be worthwhile to handle it in the Switcher and lcall down to the
452 * Guest. The sysenter semantics are hairy tho: search for that keyword in
2e04ef76
RR
453 * entry.S
454:*/
d7e28ffe 455
2e04ef76
RR
456/*H:260
457 * When we make traps go directly into the Guest, we need to make sure
bff672e6
RR
458 * the kernel stack is valid (ie. mapped in the page tables). Otherwise, the
459 * CPU trying to deliver the trap will fault while trying to push the interrupt
460 * words on the stack: this is called a double fault, and it forces us to kill
461 * the Guest.
462 *
2e04ef76
RR
463 * Which is deeply unfair, because (literally!) it wasn't the Guests' fault.
464 */
4665ac8e 465void pin_stack_pages(struct lg_cpu *cpu)
d7e28ffe
RR
466{
467 unsigned int i;
468
2e04ef76
RR
469 /*
470 * Depending on the CONFIG_4KSTACKS option, the Guest can have one or
471 * two pages of stack space.
472 */
382ac6b3 473 for (i = 0; i < cpu->lg->stack_pages; i++)
2e04ef76
RR
474 /*
475 * The stack grows *upwards*, so the address we're given is the
8057d763
RR
476 * start of the page after the kernel stack. Subtract one to
477 * get back onto the first stack page, and keep subtracting to
2e04ef76
RR
478 * get to the rest of the stack pages.
479 */
1713608f 480 pin_page(cpu, cpu->esp1 - 1 - i * PAGE_SIZE);
d7e28ffe
RR
481}
482
2e04ef76
RR
483/*
484 * Direct traps also mean that we need to know whenever the Guest wants to use
9f54288d
RR
485 * a different kernel stack, so we can change the guest TSS to use that
486 * stack. The TSS entries expect a virtual address, so unlike most addresses
bff672e6
RR
487 * the Guest gives us, the "esp" (stack pointer) value here is virtual, not
488 * physical.
489 *
490 * In Linux each process has its own kernel stack, so this happens a lot: we
2e04ef76
RR
491 * change stacks on each context switch.
492 */
4665ac8e 493void guest_set_stack(struct lg_cpu *cpu, u32 seg, u32 esp, unsigned int pages)
d7e28ffe 494{
2e04ef76
RR
495 /*
496 * You're not allowed a stack segment with privilege level 0: bad Guest!
497 */
d7e28ffe 498 if ((seg & 0x3) != GUEST_PL)
382ac6b3 499 kill_guest(cpu, "bad stack segment %i", seg);
bff672e6 500 /* We only expect one or two stack pages. */
d7e28ffe 501 if (pages > 2)
382ac6b3 502 kill_guest(cpu, "bad stack pages %u", pages);
bff672e6 503 /* Save where the stack is, and how many pages */
4665ac8e
GOC
504 cpu->ss1 = seg;
505 cpu->esp1 = esp;
506 cpu->lg->stack_pages = pages;
bff672e6 507 /* Make sure the new stack pages are mapped */
4665ac8e 508 pin_stack_pages(cpu);
d7e28ffe
RR
509}
510
2e04ef76
RR
511/*
512 * All this reference to mapping stacks leads us neatly into the other complex
513 * part of the Host: page table handling.
514 */
bff672e6 515
2e04ef76
RR
516/*H:235
517 * This is the routine which actually checks the Guest's IDT entry and
518 * transfers it into the entry in "struct lguest":
519 */
382ac6b3 520static void set_trap(struct lg_cpu *cpu, struct desc_struct *trap,
d7e28ffe
RR
521 unsigned int num, u32 lo, u32 hi)
522{
523 u8 type = idt_type(lo, hi);
524
bff672e6 525 /* We zero-out a not-present entry */
d7e28ffe
RR
526 if (!idt_present(lo, hi)) {
527 trap->a = trap->b = 0;
528 return;
529 }
530
bff672e6 531 /* We only support interrupt and trap gates. */
d7e28ffe 532 if (type != 0xE && type != 0xF)
382ac6b3 533 kill_guest(cpu, "bad IDT type %i", type);
d7e28ffe 534
2e04ef76
RR
535 /*
536 * We only copy the handler address, present bit, privilege level and
bff672e6
RR
537 * type. The privilege level controls where the trap can be triggered
538 * manually with an "int" instruction. This is usually GUEST_PL,
2e04ef76
RR
539 * except for system calls which userspace can use.
540 */
d7e28ffe
RR
541 trap->a = ((__KERNEL_CS|GUEST_PL)<<16) | (lo&0x0000FFFF);
542 trap->b = (hi&0xFFFFEF00);
543}
544
2e04ef76
RR
545/*H:230
546 * While we're here, dealing with delivering traps and interrupts to the
bff672e6
RR
547 * Guest, we might as well complete the picture: how the Guest tells us where
548 * it wants them to go. This would be simple, except making traps fast
549 * requires some tricks.
550 *
551 * We saw the Guest setting Interrupt Descriptor Table (IDT) entries with the
2e04ef76
RR
552 * LHCALL_LOAD_IDT_ENTRY hypercall before: that comes here.
553 */
fc708b3e 554void load_guest_idt_entry(struct lg_cpu *cpu, unsigned int num, u32 lo, u32 hi)
d7e28ffe 555{
2e04ef76
RR
556 /*
557 * Guest never handles: NMI, doublefault, spurious interrupt or
558 * hypercall. We ignore when it tries to set them.
559 */
d7e28ffe
RR
560 if (num == 2 || num == 8 || num == 15 || num == LGUEST_TRAP_ENTRY)
561 return;
562
2e04ef76
RR
563 /*
564 * Mark the IDT as changed: next time the Guest runs we'll know we have
565 * to copy this again.
566 */
ae3749dc 567 cpu->changed |= CHANGED_IDT;
bff672e6 568
56adbe9d 569 /* Check that the Guest doesn't try to step outside the bounds. */
fc708b3e 570 if (num >= ARRAY_SIZE(cpu->arch.idt))
382ac6b3 571 kill_guest(cpu, "Setting idt entry %u", num);
56adbe9d 572 else
382ac6b3 573 set_trap(cpu, &cpu->arch.idt[num], num, lo, hi);
d7e28ffe
RR
574}
575
2e04ef76
RR
576/*
577 * The default entry for each interrupt points into the Switcher routines which
bff672e6 578 * simply return to the Host. The run_guest() loop will then call
2e04ef76
RR
579 * deliver_trap() to bounce it back into the Guest.
580 */
d7e28ffe
RR
581static void default_idt_entry(struct desc_struct *idt,
582 int trap,
0c12091d
RR
583 const unsigned long handler,
584 const struct desc_struct *base)
d7e28ffe 585{
bff672e6 586 /* A present interrupt gate. */
d7e28ffe
RR
587 u32 flags = 0x8e00;
588
2e04ef76
RR
589 /*
590 * Set the privilege level on the entry for the hypercall: this allows
591 * the Guest to use the "int" instruction to trigger it.
592 */
d7e28ffe
RR
593 if (trap == LGUEST_TRAP_ENTRY)
594 flags |= (GUEST_PL << 13);
0c12091d 595 else if (base)
2e04ef76
RR
596 /*
597 * Copy privilege level from what Guest asked for. This allows
598 * debug (int 3) traps from Guest userspace, for example.
599 */
0c12091d 600 flags |= (base->b & 0x6000);
d7e28ffe 601
bff672e6 602 /* Now pack it into the IDT entry in its weird format. */
d7e28ffe
RR
603 idt->a = (LGUEST_CS<<16) | (handler&0x0000FFFF);
604 idt->b = (handler&0xFFFF0000) | flags;
605}
606
bff672e6 607/* When the Guest first starts, we put default entries into the IDT. */
d7e28ffe
RR
608void setup_default_idt_entries(struct lguest_ro_state *state,
609 const unsigned long *def)
610{
611 unsigned int i;
612
613 for (i = 0; i < ARRAY_SIZE(state->guest_idt); i++)
0c12091d 614 default_idt_entry(&state->guest_idt[i], i, def[i], NULL);
d7e28ffe
RR
615}
616
2e04ef76
RR
617/*H:240
618 * We don't use the IDT entries in the "struct lguest" directly, instead
bff672e6 619 * we copy them into the IDT which we've set up for Guests on this CPU, just
2e04ef76
RR
620 * before we run the Guest. This routine does that copy.
621 */
fc708b3e 622void copy_traps(const struct lg_cpu *cpu, struct desc_struct *idt,
d7e28ffe
RR
623 const unsigned long *def)
624{
625 unsigned int i;
626
2e04ef76
RR
627 /*
628 * We can simply copy the direct traps, otherwise we use the default
629 * ones in the Switcher: they will return to the Host.
630 */
fc708b3e 631 for (i = 0; i < ARRAY_SIZE(cpu->arch.idt); i++) {
0c12091d
RR
632 const struct desc_struct *gidt = &cpu->arch.idt[i];
633
56adbe9d
RR
634 /* If no Guest can ever override this trap, leave it alone. */
635 if (!direct_trap(i))
636 continue;
637
2e04ef76
RR
638 /*
639 * Only trap gates (type 15) can go direct to the Guest.
56adbe9d
RR
640 * Interrupt gates (type 14) disable interrupts as they are
641 * entered, which we never let the Guest do. Not present
0c12091d
RR
642 * entries (type 0x0) also can't go direct, of course.
643 *
644 * If it can't go direct, we still need to copy the priv. level:
645 * they might want to give userspace access to a software
2e04ef76
RR
646 * interrupt.
647 */
0c12091d
RR
648 if (idt_type(gidt->a, gidt->b) == 0xF)
649 idt[i] = *gidt;
d7e28ffe 650 else
0c12091d 651 default_idt_entry(&idt[i], i, def[i], gidt);
d7e28ffe 652 }
d7e28ffe
RR
653}
654
e1e72965
RR
655/*H:200
656 * The Guest Clock.
657 *
658 * There are two sources of virtual interrupts. We saw one in lguest_user.c:
659 * the Launcher sending interrupts for virtual devices. The other is the Guest
660 * timer interrupt.
661 *
662 * The Guest uses the LHCALL_SET_CLOCKEVENT hypercall to tell us how long to
663 * the next timer interrupt (in nanoseconds). We use the high-resolution timer
664 * infrastructure to set a callback at that time.
665 *
2e04ef76
RR
666 * 0 means "turn off the clock".
667 */
ad8d8f3b 668void guest_set_clockevent(struct lg_cpu *cpu, unsigned long delta)
d7e28ffe
RR
669{
670 ktime_t expires;
671
672 if (unlikely(delta == 0)) {
673 /* Clock event device is shutting down. */
ad8d8f3b 674 hrtimer_cancel(&cpu->hrt);
d7e28ffe
RR
675 return;
676 }
677
2e04ef76
RR
678 /*
679 * We use wallclock time here, so the Guest might not be running for
e1e72965 680 * all the time between now and the timer interrupt it asked for. This
2e04ef76
RR
681 * is almost always the right thing to do.
682 */
d7e28ffe 683 expires = ktime_add_ns(ktime_get_real(), delta);
ad8d8f3b 684 hrtimer_start(&cpu->hrt, expires, HRTIMER_MODE_ABS);
d7e28ffe
RR
685}
686
e1e72965 687/* This is the function called when the Guest's timer expires. */
d7e28ffe
RR
688static enum hrtimer_restart clockdev_fn(struct hrtimer *timer)
689{
ad8d8f3b 690 struct lg_cpu *cpu = container_of(timer, struct lg_cpu, hrt);
d7e28ffe 691
e1e72965 692 /* Remember the first interrupt is the timer interrupt. */
9f155a9b 693 set_interrupt(cpu, 0);
d7e28ffe
RR
694 return HRTIMER_NORESTART;
695}
696
e1e72965 697/* This sets up the timer for this Guest. */
ad8d8f3b 698void init_clockdev(struct lg_cpu *cpu)
d7e28ffe 699{
ad8d8f3b
GOC
700 hrtimer_init(&cpu->hrt, CLOCK_REALTIME, HRTIMER_MODE_ABS);
701 cpu->hrt.function = clockdev_fn;
d7e28ffe 702}
This page took 0.627946 seconds and 5 git commands to generate.