- 24 Oct, 2010 40 commits
-
-
Alexander Graf authored
While running in hooked code we need to store register contents out because we must not clobber any registers. So let's add some fields to the shared page we can just happily write to. Signed-off-by:
Alexander Graf <agraf@suse.de> Signed-off-by:
Avi Kivity <avi@redhat.com>
-
Alexander Graf authored
When running in hooked code we need a way to disable interrupts without clobbering any interrupts or exiting out to the hypervisor. To achieve this, we have an additional critical field in the shared page. If that field is equal to the r1 register of the guest, it tells the hypervisor that we're in such a critical section and thus may not receive any interrupts. Signed-off-by:
-
Alexander Graf authored
To communicate with KVM directly we need to plumb some sort of interface between the guest and KVM. Usually those interfaces use hypercalls. This hypercall implementation is described in the last patch of the series in a special documentation file. Please read that for further information. This patch implements stubs to handle KVM PPC hypercalls on the host and guest side alike. Signed-off-by:
-
Alexander Graf authored
When in kernel mode there are 4 additional registers available that are simple data storage. Instead of exiting to the hypervisor to read and write those, we can just share them with the guest using the page. This patch converts all users of the current field to the shared page. Signed-off-by:
-
Alexander Graf authored
The SRR0 and SRR1 registers contain cached values of the PC and MSR respectively. They get written to by the hypervisor when an interrupt occurs or directly by the kernel. They are also used to tell the rfi(d) instruction where to jump to. Because it only gets touched on defined events that, it's very simple to share with the guest. Hypervisor and guest both have full r/w access. This patch converts all users of the current field to the shared page. Signed-off-by:
-
Alexander Graf authored
The DAR register contains the address a data page fault occured at. This register behaves pretty much like a simple data storage register that gets written to on data faults. There is no hypervisor interaction required on read or write. This patch converts all users of the current field to the shared page. Signed-off-by:
-
Alexander Graf authored
The DSISR register contains information about a data page fault. It is fully read/write from inside the guest context and we don't need to worry about interacting based on writes of this register. This patch converts all users of the current field to the shared page. Signed-off-by:
-
Alexander Graf authored
One of the most obvious registers to share with the guest directly is the MSR. The MSR contains the "interrupts enabled" flag which the guest has to toggle in critical sections. So in order to bring the overhead of interrupt en- and disabling down, let's put msr into the shared page. Keep in mind that even though you can fully read its contents, writing to it doesn't always update all state. There are a few safe fields that don't require hypervisor interaction. See the documentation for a list of MSR bits that are safe to be set from inside the guest. Signed-off-by:
-
Alexander Graf authored
For transparent variable sharing between the hypervisor and guest, I introduce a shared page. This shared page will contain all the registers the guest can read and write safely without exiting guest context. This patch only implements the stubs required for the basic structure of the shared page. The actual register moving follows. Signed-off-by:
-
Mohammed Gamal authored
If a nop instruction is encountered, we jump directly to the done label. This skip updating rip. Break from the switch case instead Signed-off-by:
Mohammed Gamal <m.gamal005@gmail.com> Signed-off-by:
-
Avi Kivity authored
Since modrm operand can be either register or memory, decoding it into a 'struct operand', which can represent both, is simpler. Signed-off-by: -
Avi Kivity authored
Instead of using modrm_ea, which will soon be gone. Signed-off-by: -
Avi Kivity authored
The NoAccess flag will prevent memory from being accessed. Signed-off-by: -
Avi Kivity authored
Use for INVLPG, which accesses the tlb, not memory. Signed-off-by: -
Avi Kivity authored
This is an ordinary modrm source or destination; use the standard structure representing it. Signed-off-by: -
Avi Kivity authored
This is an ordinary modrm source or destination; use the standard structure representing it. Signed-off-by: -
Avi Kivity authored
Signed-off-by: -
Avi Kivity authored
The operands for these instructions are 32 bits or 64 bits, depending on long mode, and ignoring REX prefixes, or the operand size prefix. Signed-off-by: -
Avi Kivity authored
(x && (x & y)) == (x & y) Signed-off-by: -
Avi Kivity authored
Unused (and has never been). Signed-off-by: -
Avi Kivity authored
The code is repeated three times, put it into fetch_register_operand() Signed-off-by: -
Avi Kivity authored
Signed-off-by: -
Avi Kivity authored
Use X8() to avoid repetition. Signed-off-by: -
Avi Kivity authored
Currently we use a void pointer for memory addresses. That's wrong since these are guest virtual addresses which are not directly dereferencable by the host. Use the correct type, unsigned long. Signed-off-by: -
Avi Kivity authored
Let it compute modrm_seg instead, and have the caller apply it. Signed-off-by: -
Joerg Roedel authored
This patch lets a nested vmrun fail if the L1 hypervisor left the asid zero. This fixes the asid_zero unit test. Signed-off-by:
Joerg Roedel <joerg.roedel@amd.com> Signed-off-by:
-
Joerg Roedel authored
This patch lets the nested vmrun fail if the L1 hypervisor has not intercepted vmrun. This fixes the "vmrun intercept check" unit test. Signed-off-by:
-
Xiao Guangrong authored
Mark page dirty only when this page is really written, it's more exacter, and also can fix dirty page marking in speculation path Signed-off-by:
Xiao Guangrong <xiaoguangrong@cn.fujitsu.com> Signed-off-by:
-
Xiao Guangrong authored
Introduce spte_has_volatile_bits() function to judge whether spte bits will miss, it's more readable and can help us to cleanup code later Signed-off-by:
-
Xiao Guangrong authored
It's a small cleanup that using using kvm_set_pfn_accessed() instead of mark_page_accessed() Signed-off-by:
-
Gleb Natapov authored
Do not recheck io permission on every iteration. Signed-off-by:
Gleb Natapov <gleb@redhat.com> Signed-off-by:
-
Avi Kivity authored
LMSW is documented not to be able to clear cr0.pe; make it so. Signed-off-by: -
Gleb Natapov authored
No need to update vcpu state since instruction is in the middle of the emulation. Signed-off-by:
Marcelo Tosatti <mtosatti@redhat.com>
-
Avi Kivity authored
Signed-off-by:
-
Avi Kivity authored
Needed for repeating instructions with execution functions. Signed-off-by:
-
Avi Kivity authored
So they can reference execution functions. Signed-off-by:
-
Avi Kivity authored
No code changes. Signed-off-by:
-
Avi Kivity authored
Instead of looking up the opcode twice (once for decode flags, once for the big execution switch) look up both flags and function in the decode tables. Signed-off-by:
-
Avi Kivity authored
It doesn't ever change, so we don't need to pass it around everywhere. Signed-off-by:
-
Avi Kivity authored
Now that the group index no longer exists, the space is free. Signed-off-by:
-
