/*1* Copyright (C) 2006, Rusty Russell <[email protected]> IBM Corporation.2* Copyright (C) 2007, Jes Sorensen <[email protected]> SGI.3*4* This program is free software; you can redistribute it and/or modify5* it under the terms of the GNU General Public License as published by6* the Free Software Foundation; either version 2 of the License, or7* (at your option) any later version.8*9* This program is distributed in the hope that it will be useful, but10* WITHOUT ANY WARRANTY; without even the implied warranty of11* MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, GOOD TITLE or12* NON INFRINGEMENT. See the GNU General Public License for more13* details.14*15* You should have received a copy of the GNU General Public License16* along with this program; if not, write to the Free Software17* Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.18*/19/*P:45020* This file contains the x86-specific lguest code. It used to be all21* mixed in with drivers/lguest/core.c but several foolhardy code slashers22* wrestled most of the dependencies out to here in preparation for porting23* lguest to other architectures (see what I mean by foolhardy?).24*25* This also contains a couple of non-obvious setup and teardown pieces which26* were implemented after days of debugging pain.27:*/28#include <linux/kernel.h>29#include <linux/start_kernel.h>30#include <linux/string.h>31#include <linux/console.h>32#include <linux/screen_info.h>33#include <linux/irq.h>34#include <linux/interrupt.h>35#include <linux/clocksource.h>36#include <linux/clockchips.h>37#include <linux/cpu.h>38#include <linux/lguest.h>39#include <linux/lguest_launcher.h>40#include <asm/paravirt.h>41#include <asm/param.h>42#include <asm/page.h>43#include <asm/pgtable.h>44#include <asm/desc.h>45#include <asm/setup.h>46#include <asm/lguest.h>47#include <asm/uaccess.h>48#include <asm/i387.h>49#include "../lg.h"5051static int cpu_had_pge;5253static struct {54unsigned long offset;55unsigned short segment;56} lguest_entry;5758/* Offset from where switcher.S was compiled to where we've copied it */59static unsigned long switcher_offset(void)60{61return SWITCHER_ADDR - (unsigned long)start_switcher_text;62}6364/* This cpu's struct lguest_pages. */65static struct lguest_pages *lguest_pages(unsigned int cpu)66{67return &(((struct lguest_pages *)68(SWITCHER_ADDR + SHARED_SWITCHER_PAGES*PAGE_SIZE))[cpu]);69}7071static DEFINE_PER_CPU(struct lg_cpu *, lg_last_cpu);7273/*S:01074* We approach the Switcher.75*76* Remember that each CPU has two pages which are visible to the Guest when it77* runs on that CPU. This has to contain the state for that Guest: we copy the78* state in just before we run the Guest.79*80* Each Guest has "changed" flags which indicate what has changed in the Guest81* since it last ran. We saw this set in interrupts_and_traps.c and82* segments.c.83*/84static void copy_in_guest_info(struct lg_cpu *cpu, struct lguest_pages *pages)85{86/*87* Copying all this data can be quite expensive. We usually run the88* same Guest we ran last time (and that Guest hasn't run anywhere else89* meanwhile). If that's not the case, we pretend everything in the90* Guest has changed.91*/92if (__this_cpu_read(lg_last_cpu) != cpu || cpu->last_pages != pages) {93__this_cpu_write(lg_last_cpu, cpu);94cpu->last_pages = pages;95cpu->changed = CHANGED_ALL;96}9798/*99* These copies are pretty cheap, so we do them unconditionally: */100/* Save the current Host top-level page directory.101*/102pages->state.host_cr3 = __pa(current->mm->pgd);103/*104* Set up the Guest's page tables to see this CPU's pages (and no105* other CPU's pages).106*/107map_switcher_in_guest(cpu, pages);108/*109* Set up the two "TSS" members which tell the CPU what stack to use110* for traps which do directly into the Guest (ie. traps at privilege111* level 1).112*/113pages->state.guest_tss.sp1 = cpu->esp1;114pages->state.guest_tss.ss1 = cpu->ss1;115116/* Copy direct-to-Guest trap entries. */117if (cpu->changed & CHANGED_IDT)118copy_traps(cpu, pages->state.guest_idt, default_idt_entries);119120/* Copy all GDT entries which the Guest can change. */121if (cpu->changed & CHANGED_GDT)122copy_gdt(cpu, pages->state.guest_gdt);123/* If only the TLS entries have changed, copy them. */124else if (cpu->changed & CHANGED_GDT_TLS)125copy_gdt_tls(cpu, pages->state.guest_gdt);126127/* Mark the Guest as unchanged for next time. */128cpu->changed = 0;129}130131/* Finally: the code to actually call into the Switcher to run the Guest. */132static void run_guest_once(struct lg_cpu *cpu, struct lguest_pages *pages)133{134/* This is a dummy value we need for GCC's sake. */135unsigned int clobber;136137/*138* Copy the guest-specific information into this CPU's "struct139* lguest_pages".140*/141copy_in_guest_info(cpu, pages);142143/*144* Set the trap number to 256 (impossible value). If we fault while145* switching to the Guest (bad segment registers or bug), this will146* cause us to abort the Guest.147*/148cpu->regs->trapnum = 256;149150/*151* Now: we push the "eflags" register on the stack, then do an "lcall".152* This is how we change from using the kernel code segment to using153* the dedicated lguest code segment, as well as jumping into the154* Switcher.155*156* The lcall also pushes the old code segment (KERNEL_CS) onto the157* stack, then the address of this call. This stack layout happens to158* exactly match the stack layout created by an interrupt...159*/160asm volatile("pushf; lcall *lguest_entry"161/*162* This is how we tell GCC that %eax ("a") and %ebx ("b")163* are changed by this routine. The "=" means output.164*/165: "=a"(clobber), "=b"(clobber)166/*167* %eax contains the pages pointer. ("0" refers to the168* 0-th argument above, ie "a"). %ebx contains the169* physical address of the Guest's top-level page170* directory.171*/172: "0"(pages), "1"(__pa(cpu->lg->pgdirs[cpu->cpu_pgd].pgdir))173/*174* We tell gcc that all these registers could change,175* which means we don't have to save and restore them in176* the Switcher.177*/178: "memory", "%edx", "%ecx", "%edi", "%esi");179}180/*:*/181182/*M:002183* There are hooks in the scheduler which we can register to tell when we184* get kicked off the CPU (preempt_notifier_register()). This would allow us185* to lazily disable SYSENTER which would regain some performance, and should186* also simplify copy_in_guest_info(). Note that we'd still need to restore187* things when we exit to Launcher userspace, but that's fairly easy.188*189* We could also try using these hooks for PGE, but that might be too expensive.190*191* The hooks were designed for KVM, but we can also put them to good use.192:*/193194/*H:040195* This is the i386-specific code to setup and run the Guest. Interrupts196* are disabled: we own the CPU.197*/198void lguest_arch_run_guest(struct lg_cpu *cpu)199{200/*201* Remember the awfully-named TS bit? If the Guest has asked to set it202* we set it now, so we can trap and pass that trap to the Guest if it203* uses the FPU.204*/205if (cpu->ts)206unlazy_fpu(current);207208/*209* SYSENTER is an optimized way of doing system calls. We can't allow210* it because it always jumps to privilege level 0. A normal Guest211* won't try it because we don't advertise it in CPUID, but a malicious212* Guest (or malicious Guest userspace program) could, so we tell the213* CPU to disable it before running the Guest.214*/215if (boot_cpu_has(X86_FEATURE_SEP))216wrmsr(MSR_IA32_SYSENTER_CS, 0, 0);217218/*219* Now we actually run the Guest. It will return when something220* interesting happens, and we can examine its registers to see what it221* was doing.222*/223run_guest_once(cpu, lguest_pages(raw_smp_processor_id()));224225/*226* Note that the "regs" structure contains two extra entries which are227* not really registers: a trap number which says what interrupt or228* trap made the switcher code come back, and an error code which some229* traps set.230*/231232/* Restore SYSENTER if it's supposed to be on. */233if (boot_cpu_has(X86_FEATURE_SEP))234wrmsr(MSR_IA32_SYSENTER_CS, __KERNEL_CS, 0);235236/*237* If the Guest page faulted, then the cr2 register will tell us the238* bad virtual address. We have to grab this now, because once we239* re-enable interrupts an interrupt could fault and thus overwrite240* cr2, or we could even move off to a different CPU.241*/242if (cpu->regs->trapnum == 14)243cpu->arch.last_pagefault = read_cr2();244/*245* Similarly, if we took a trap because the Guest used the FPU,246* we have to restore the FPU it expects to see.247* math_state_restore() may sleep and we may even move off to248* a different CPU. So all the critical stuff should be done249* before this.250*/251else if (cpu->regs->trapnum == 7)252math_state_restore();253}254255/*H:130256* Now we've examined the hypercall code; our Guest can make requests.257* Our Guest is usually so well behaved; it never tries to do things it isn't258* allowed to, and uses hypercalls instead. Unfortunately, Linux's paravirtual259* infrastructure isn't quite complete, because it doesn't contain replacements260* for the Intel I/O instructions. As a result, the Guest sometimes fumbles261* across one during the boot process as it probes for various things which are262* usually attached to a PC.263*264* When the Guest uses one of these instructions, we get a trap (General265* Protection Fault) and come here. We see if it's one of those troublesome266* instructions and skip over it. We return true if we did.267*/268static int emulate_insn(struct lg_cpu *cpu)269{270u8 insn;271unsigned int insnlen = 0, in = 0, shift = 0;272/*273* The eip contains the *virtual* address of the Guest's instruction:274* guest_pa just subtracts the Guest's page_offset.275*/276unsigned long physaddr = guest_pa(cpu, cpu->regs->eip);277278/*279* This must be the Guest kernel trying to do something, not userspace!280* The bottom two bits of the CS segment register are the privilege281* level.282*/283if ((cpu->regs->cs & 3) != GUEST_PL)284return 0;285286/* Decoding x86 instructions is icky. */287insn = lgread(cpu, physaddr, u8);288289/*290* Around 2.6.33, the kernel started using an emulation for the291* cmpxchg8b instruction in early boot on many configurations. This292* code isn't paravirtualized, and it tries to disable interrupts.293* Ignore it, which will Mostly Work.294*/295if (insn == 0xfa) {296/* "cli", or Clear Interrupt Enable instruction. Skip it. */297cpu->regs->eip++;298return 1;299}300301/*302* 0x66 is an "operand prefix". It means it's using the upper 16 bits303* of the eax register.304*/305if (insn == 0x66) {306shift = 16;307/* The instruction is 1 byte so far, read the next byte. */308insnlen = 1;309insn = lgread(cpu, physaddr + insnlen, u8);310}311312/*313* We can ignore the lower bit for the moment and decode the 4 opcodes314* we need to emulate.315*/316switch (insn & 0xFE) {317case 0xE4: /* in <next byte>,%al */318insnlen += 2;319in = 1;320break;321case 0xEC: /* in (%dx),%al */322insnlen += 1;323in = 1;324break;325case 0xE6: /* out %al,<next byte> */326insnlen += 2;327break;328case 0xEE: /* out %al,(%dx) */329insnlen += 1;330break;331default:332/* OK, we don't know what this is, can't emulate. */333return 0;334}335336/*337* If it was an "IN" instruction, they expect the result to be read338* into %eax, so we change %eax. We always return all-ones, which339* traditionally means "there's nothing there".340*/341if (in) {342/* Lower bit tells is whether it's a 16 or 32 bit access */343if (insn & 0x1)344cpu->regs->eax = 0xFFFFFFFF;345else346cpu->regs->eax |= (0xFFFF << shift);347}348/* Finally, we've "done" the instruction, so move past it. */349cpu->regs->eip += insnlen;350/* Success! */351return 1;352}353354/*355* Our hypercalls mechanism used to be based on direct software interrupts.356* After Anthony's "Refactor hypercall infrastructure" kvm patch, we decided to357* change over to using kvm hypercalls.358*359* KVM_HYPERCALL is actually a "vmcall" instruction, which generates an invalid360* opcode fault (fault 6) on non-VT cpus, so the easiest solution seemed to be361* an *emulation approach*: if the fault was really produced by an hypercall362* (is_hypercall() does exactly this check), we can just call the corresponding363* hypercall host implementation function.364*365* But these invalid opcode faults are notably slower than software interrupts.366* So we implemented the *patching (or rewriting) approach*: every time we hit367* the KVM_HYPERCALL opcode in Guest code, we patch it to the old "int 0x1f"368* opcode, so next time the Guest calls this hypercall it will use the369* faster trap mechanism.370*371* Matias even benchmarked it to convince you: this shows the average cycle372* cost of a hypercall. For each alternative solution mentioned above we've373* made 5 runs of the benchmark:374*375* 1) direct software interrupt: 2915, 2789, 2764, 2721, 2898376* 2) emulation technique: 3410, 3681, 3466, 3392, 3780377* 3) patching (rewrite) technique: 2977, 2975, 2891, 2637, 2884378*379* One two-line function is worth a 20% hypercall speed boost!380*/381static void rewrite_hypercall(struct lg_cpu *cpu)382{383/*384* This are the opcodes we use to patch the Guest. The opcode for "int385* $0x1f" is "0xcd 0x1f" but vmcall instruction is 3 bytes long, so we386* complete the sequence with a NOP (0x90).387*/388u8 insn[3] = {0xcd, 0x1f, 0x90};389390__lgwrite(cpu, guest_pa(cpu, cpu->regs->eip), insn, sizeof(insn));391/*392* The above write might have caused a copy of that page to be made393* (if it was read-only). We need to make sure the Guest has394* up-to-date pagetables. As this doesn't happen often, we can just395* drop them all.396*/397guest_pagetable_clear_all(cpu);398}399400static bool is_hypercall(struct lg_cpu *cpu)401{402u8 insn[3];403404/*405* This must be the Guest kernel trying to do something.406* The bottom two bits of the CS segment register are the privilege407* level.408*/409if ((cpu->regs->cs & 3) != GUEST_PL)410return false;411412/* Is it a vmcall? */413__lgread(cpu, insn, guest_pa(cpu, cpu->regs->eip), sizeof(insn));414return insn[0] == 0x0f && insn[1] == 0x01 && insn[2] == 0xc1;415}416417/*H:050 Once we've re-enabled interrupts, we look at why the Guest exited. */418void lguest_arch_handle_trap(struct lg_cpu *cpu)419{420switch (cpu->regs->trapnum) {421case 13: /* We've intercepted a General Protection Fault. */422/*423* Check if this was one of those annoying IN or OUT424* instructions which we need to emulate. If so, we just go425* back into the Guest after we've done it.426*/427if (cpu->regs->errcode == 0) {428if (emulate_insn(cpu))429return;430}431/*432* If KVM is active, the vmcall instruction triggers a General433* Protection Fault. Normally it triggers an invalid opcode434* fault (6):435*/436case 6:437/*438* We need to check if ring == GUEST_PL and faulting439* instruction == vmcall.440*/441if (is_hypercall(cpu)) {442rewrite_hypercall(cpu);443return;444}445break;446case 14: /* We've intercepted a Page Fault. */447/*448* The Guest accessed a virtual address that wasn't mapped.449* This happens a lot: we don't actually set up most of the page450* tables for the Guest at all when we start: as it runs it asks451* for more and more, and we set them up as required. In this452* case, we don't even tell the Guest that the fault happened.453*454* The errcode tells whether this was a read or a write, and455* whether kernel or userspace code.456*/457if (demand_page(cpu, cpu->arch.last_pagefault,458cpu->regs->errcode))459return;460461/*462* OK, it's really not there (or not OK): the Guest needs to463* know. We write out the cr2 value so it knows where the464* fault occurred.465*466* Note that if the Guest were really messed up, this could467* happen before it's done the LHCALL_LGUEST_INIT hypercall, so468* lg->lguest_data could be NULL469*/470if (cpu->lg->lguest_data &&471put_user(cpu->arch.last_pagefault,472&cpu->lg->lguest_data->cr2))473kill_guest(cpu, "Writing cr2");474break;475case 7: /* We've intercepted a Device Not Available fault. */476/*477* If the Guest doesn't want to know, we already restored the478* Floating Point Unit, so we just continue without telling it.479*/480if (!cpu->ts)481return;482break;483case 32 ... 255:484/*485* These values mean a real interrupt occurred, in which case486* the Host handler has already been run. We just do a487* friendly check if another process should now be run, then488* return to run the Guest again489*/490cond_resched();491return;492case LGUEST_TRAP_ENTRY:493/*494* Our 'struct hcall_args' maps directly over our regs: we set495* up the pointer now to indicate a hypercall is pending.496*/497cpu->hcall = (struct hcall_args *)cpu->regs;498return;499}500501/* We didn't handle the trap, so it needs to go to the Guest. */502if (!deliver_trap(cpu, cpu->regs->trapnum))503/*504* If the Guest doesn't have a handler (either it hasn't505* registered any yet, or it's one of the faults we don't let506* it handle), it dies with this cryptic error message.507*/508kill_guest(cpu, "unhandled trap %li at %#lx (%#lx)",509cpu->regs->trapnum, cpu->regs->eip,510cpu->regs->trapnum == 14 ? cpu->arch.last_pagefault511: cpu->regs->errcode);512}513514/*515* Now we can look at each of the routines this calls, in increasing order of516* complexity: do_hypercalls(), emulate_insn(), maybe_do_interrupt(),517* deliver_trap() and demand_page(). After all those, we'll be ready to518* examine the Switcher, and our philosophical understanding of the Host/Guest519* duality will be complete.520:*/521static void adjust_pge(void *on)522{523if (on)524write_cr4(read_cr4() | X86_CR4_PGE);525else526write_cr4(read_cr4() & ~X86_CR4_PGE);527}528529/*H:020530* Now the Switcher is mapped and every thing else is ready, we need to do531* some more i386-specific initialization.532*/533void __init lguest_arch_host_init(void)534{535int i;536537/*538* Most of the i386/switcher.S doesn't care that it's been moved; on539* Intel, jumps are relative, and it doesn't access any references to540* external code or data.541*542* The only exception is the interrupt handlers in switcher.S: their543* addresses are placed in a table (default_idt_entries), so we need to544* update the table with the new addresses. switcher_offset() is a545* convenience function which returns the distance between the546* compiled-in switcher code and the high-mapped copy we just made.547*/548for (i = 0; i < IDT_ENTRIES; i++)549default_idt_entries[i] += switcher_offset();550551/*552* Set up the Switcher's per-cpu areas.553*554* Each CPU gets two pages of its own within the high-mapped region555* (aka. "struct lguest_pages"). Much of this can be initialized now,556* but some depends on what Guest we are running (which is set up in557* copy_in_guest_info()).558*/559for_each_possible_cpu(i) {560/* lguest_pages() returns this CPU's two pages. */561struct lguest_pages *pages = lguest_pages(i);562/* This is a convenience pointer to make the code neater. */563struct lguest_ro_state *state = &pages->state;564565/*566* The Global Descriptor Table: the Host has a different one567* for each CPU. We keep a descriptor for the GDT which says568* where it is and how big it is (the size is actually the last569* byte, not the size, hence the "-1").570*/571state->host_gdt_desc.size = GDT_SIZE-1;572state->host_gdt_desc.address = (long)get_cpu_gdt_table(i);573574/*575* All CPUs on the Host use the same Interrupt Descriptor576* Table, so we just use store_idt(), which gets this CPU's IDT577* descriptor.578*/579store_idt(&state->host_idt_desc);580581/*582* The descriptors for the Guest's GDT and IDT can be filled583* out now, too. We copy the GDT & IDT into ->guest_gdt and584* ->guest_idt before actually running the Guest.585*/586state->guest_idt_desc.size = sizeof(state->guest_idt)-1;587state->guest_idt_desc.address = (long)&state->guest_idt;588state->guest_gdt_desc.size = sizeof(state->guest_gdt)-1;589state->guest_gdt_desc.address = (long)&state->guest_gdt;590591/*592* We know where we want the stack to be when the Guest enters593* the Switcher: in pages->regs. The stack grows upwards, so594* we start it at the end of that structure.595*/596state->guest_tss.sp0 = (long)(&pages->regs + 1);597/*598* And this is the GDT entry to use for the stack: we keep a599* couple of special LGUEST entries.600*/601state->guest_tss.ss0 = LGUEST_DS;602603/*604* x86 can have a finegrained bitmap which indicates what I/O605* ports the process can use. We set it to the end of our606* structure, meaning "none".607*/608state->guest_tss.io_bitmap_base = sizeof(state->guest_tss);609610/*611* Some GDT entries are the same across all Guests, so we can612* set them up now.613*/614setup_default_gdt_entries(state);615/* Most IDT entries are the same for all Guests, too.*/616setup_default_idt_entries(state, default_idt_entries);617618/*619* The Host needs to be able to use the LGUEST segments on this620* CPU, too, so put them in the Host GDT.621*/622get_cpu_gdt_table(i)[GDT_ENTRY_LGUEST_CS] = FULL_EXEC_SEGMENT;623get_cpu_gdt_table(i)[GDT_ENTRY_LGUEST_DS] = FULL_SEGMENT;624}625626/*627* In the Switcher, we want the %cs segment register to use the628* LGUEST_CS GDT entry: we've put that in the Host and Guest GDTs, so629* it will be undisturbed when we switch. To change %cs and jump we630* need this structure to feed to Intel's "lcall" instruction.631*/632lguest_entry.offset = (long)switch_to_guest + switcher_offset();633lguest_entry.segment = LGUEST_CS;634635/*636* Finally, we need to turn off "Page Global Enable". PGE is an637* optimization where page table entries are specially marked to show638* they never change. The Host kernel marks all the kernel pages this639* way because it's always present, even when userspace is running.640*641* Lguest breaks this: unbeknownst to the rest of the Host kernel, we642* switch to the Guest kernel. If you don't disable this on all CPUs,643* you'll get really weird bugs that you'll chase for two days.644*645* I used to turn PGE off every time we switched to the Guest and back646* on when we return, but that slowed the Switcher down noticibly.647*/648649/*650* We don't need the complexity of CPUs coming and going while we're651* doing this.652*/653get_online_cpus();654if (cpu_has_pge) { /* We have a broader idea of "global". */655/* Remember that this was originally set (for cleanup). */656cpu_had_pge = 1;657/*658* adjust_pge is a helper function which sets or unsets the PGE659* bit on its CPU, depending on the argument (0 == unset).660*/661on_each_cpu(adjust_pge, (void *)0, 1);662/* Turn off the feature in the global feature set. */663clear_cpu_cap(&boot_cpu_data, X86_FEATURE_PGE);664}665put_online_cpus();666};667/*:*/668669void __exit lguest_arch_host_fini(void)670{671/* If we had PGE before we started, turn it back on now. */672get_online_cpus();673if (cpu_had_pge) {674set_cpu_cap(&boot_cpu_data, X86_FEATURE_PGE);675/* adjust_pge's argument "1" means set PGE. */676on_each_cpu(adjust_pge, (void *)1, 1);677}678put_online_cpus();679}680681682/*H:122 The i386-specific hypercalls simply farm out to the right functions. */683int lguest_arch_do_hcall(struct lg_cpu *cpu, struct hcall_args *args)684{685switch (args->arg0) {686case LHCALL_LOAD_GDT_ENTRY:687load_guest_gdt_entry(cpu, args->arg1, args->arg2, args->arg3);688break;689case LHCALL_LOAD_IDT_ENTRY:690load_guest_idt_entry(cpu, args->arg1, args->arg2, args->arg3);691break;692case LHCALL_LOAD_TLS:693guest_load_tls(cpu, args->arg1);694break;695default:696/* Bad Guest. Bad! */697return -EIO;698}699return 0;700}701702/*H:126 i386-specific hypercall initialization: */703int lguest_arch_init_hypercalls(struct lg_cpu *cpu)704{705u32 tsc_speed;706707/*708* The pointer to the Guest's "struct lguest_data" is the only argument.709* We check that address now.710*/711if (!lguest_address_ok(cpu->lg, cpu->hcall->arg1,712sizeof(*cpu->lg->lguest_data)))713return -EFAULT;714715/*716* Having checked it, we simply set lg->lguest_data to point straight717* into the Launcher's memory at the right place and then use718* copy_to_user/from_user from now on, instead of lgread/write. I put719* this in to show that I'm not immune to writing stupid720* optimizations.721*/722cpu->lg->lguest_data = cpu->lg->mem_base + cpu->hcall->arg1;723724/*725* We insist that the Time Stamp Counter exist and doesn't change with726* cpu frequency. Some devious chip manufacturers decided that TSC727* changes could be handled in software. I decided that time going728* backwards might be good for benchmarks, but it's bad for users.729*730* We also insist that the TSC be stable: the kernel detects unreliable731* TSCs for its own purposes, and we use that here.732*/733if (boot_cpu_has(X86_FEATURE_CONSTANT_TSC) && !check_tsc_unstable())734tsc_speed = tsc_khz;735else736tsc_speed = 0;737if (put_user(tsc_speed, &cpu->lg->lguest_data->tsc_khz))738return -EFAULT;739740/* The interrupt code might not like the system call vector. */741if (!check_syscall_vector(cpu->lg))742kill_guest(cpu, "bad syscall vector");743744return 0;745}746/*:*/747748/*L:030749* lguest_arch_setup_regs()750*751* Most of the Guest's registers are left alone: we used get_zeroed_page() to752* allocate the structure, so they will be 0.753*/754void lguest_arch_setup_regs(struct lg_cpu *cpu, unsigned long start)755{756struct lguest_regs *regs = cpu->regs;757758/*759* There are four "segment" registers which the Guest needs to boot:760* The "code segment" register (cs) refers to the kernel code segment761* __KERNEL_CS, and the "data", "extra" and "stack" segment registers762* refer to the kernel data segment __KERNEL_DS.763*764* The privilege level is packed into the lower bits. The Guest runs765* at privilege level 1 (GUEST_PL).766*/767regs->ds = regs->es = regs->ss = __KERNEL_DS|GUEST_PL;768regs->cs = __KERNEL_CS|GUEST_PL;769770/*771* The "eflags" register contains miscellaneous flags. Bit 1 (0x002)772* is supposed to always be "1". Bit 9 (0x200) controls whether773* interrupts are enabled. We always leave interrupts enabled while774* running the Guest.775*/776regs->eflags = X86_EFLAGS_IF | 0x2;777778/*779* The "Extended Instruction Pointer" register says where the Guest is780* running.781*/782regs->eip = start;783784/*785* %esi points to our boot information, at physical address 0, so don't786* touch it.787*/788789/* There are a couple of GDT entries the Guest expects at boot. */790setup_guest_gdt(cpu);791}792793794