<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/kvm/vmx.c, branch linux-2.6.23.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.23.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.23.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2007-12-14T17:50:57Z</updated>
<entry>
<title>KVM: VMX: Reset mmu context when entering real mode</title>
<updated>2007-12-14T17:50:57Z</updated>
<author>
<name>Eddie Dong</name>
</author>
<published>2007-12-02T11:18:47Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=0fe8f9b280a5f7a65aebc51ab6b5200a8bf05e13'/>
<id>urn:sha1:0fe8f9b280a5f7a65aebc51ab6b5200a8bf05e13</id>
<content type='text'>
patch 8668a3c468ed55d19514117a5a959d91d3d03823 in mainline.

Resetting an SMP guest will force AP enter real mode (RESET) with
paging enabled in protected mode. While current enter_rmode() can
only handle mode switch from nonpaging mode to real mode which leads
to SMP reboot failure.

Fix by reloading the mmu context on entering real mode.

Signed-off-by: Yaozu (Eddie) Dong &lt;eddie.dong@intel.com&gt;
Signed-off-by: Qing He &lt;qing.he@intel.com&gt;
Signed-off-by: Avi Kivity &lt;avi@qumranet.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>KVM: VMX: Force vm86 mode if setting flags during real mode</title>
<updated>2007-12-14T17:50:57Z</updated>
<author>
<name>Avi Kivity</name>
</author>
<published>2007-12-02T11:18:46Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=9ec0e2f614c0b29e87ff0b451aa1201498309bd7'/>
<id>urn:sha1:9ec0e2f614c0b29e87ff0b451aa1201498309bd7</id>
<content type='text'>
patch 78f7826868da8e27d097802139a3fec39f47f3b8 in mainline.

When resetting from userspace, we need to handle the flags being cleared
even after we are in real mode.

Signed-off-by: Avi Kivity &lt;avi@qumranet.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>KVM: Clean up #includes</title>
<updated>2007-07-16T09:05:49Z</updated>
<author>
<name>Avi Kivity</name>
</author>
<published>2007-06-28T18:15:57Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e495606dd09d79f9fa496334ac3958f6ff179d82'/>
<id>urn:sha1:e495606dd09d79f9fa496334ac3958f6ff179d82</id>
<content type='text'>
Remove unnecessary ones, and rearange the remaining in the standard order.

Signed-off-by: Avi Kivity &lt;avi@qumranet.com&gt;
</content>
</entry>
<entry>
<title>KVM: VMX: Remove unnecessary code in vmx_tlb_flush()</title>
<updated>2007-07-16T09:05:49Z</updated>
<author>
<name>Avi Kivity</name>
</author>
<published>2007-06-21T08:54:45Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=796fd1b23e463e98b3e2fc86ed571db06dc945bb'/>
<id>urn:sha1:796fd1b23e463e98b3e2fc86ed571db06dc945bb</id>
<content type='text'>
A vmexit implicitly flushes the tlb; the code is bogus.

Noted by Shaohua Li.

Signed-off-by: Avi Kivity &lt;avi@qumranet.com&gt;
</content>
</entry>
<entry>
<title>KVM: VMX: Reinitialize the real-mode tss when entering real mode</title>
<updated>2007-07-16T09:05:48Z</updated>
<author>
<name>Avi Kivity</name>
</author>
<published>2007-06-20T08:20:04Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=75880a01124c6aa5d428bdc14163039a87618be1'/>
<id>urn:sha1:75880a01124c6aa5d428bdc14163039a87618be1</id>
<content type='text'>
Protected mode code may have corrupted the real-mode tss, so re-initialize
it when switching to real mode.

Signed-off-by: Avi Kivity &lt;avi@qumranet.com&gt;
</content>
</entry>
<entry>
<title>KVM: VMX: Fix interrupt checking on lightweight exit</title>
<updated>2007-07-16T09:05:48Z</updated>
<author>
<name>Gregory Haskins</name>
</author>
<published>2007-05-31T18:08:58Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ff1dc7942ba8fa4a86619bcb37ed68afae1f69ca'/>
<id>urn:sha1:ff1dc7942ba8fa4a86619bcb37ed68afae1f69ca</id>
<content type='text'>
With kernel-injected interrupts, we need to check for interrupts on
lightweight exits too.

Signed-off-by: Gregory Haskins &lt;ghaskins@novell.com&gt;
Signed-off-by: Avi Kivity &lt;avi@qumranet.com&gt;
</content>
</entry>
<entry>
<title>KVM: VMX: Ensure vcpu time stamp counter is monotonous</title>
<updated>2007-07-16T09:05:47Z</updated>
<author>
<name>Avi Kivity</name>
</author>
<published>2007-06-13T16:55:28Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=7700270ee3c1324c18f5b7c36ee5ba1a4165919a'/>
<id>urn:sha1:7700270ee3c1324c18f5b7c36ee5ba1a4165919a</id>
<content type='text'>
If the time stamp counter goes backwards, a guest delay loop can become
infinite.  This can happen if a vcpu is migrated to another cpu, where
the counter has a lower value than the first cpu.

Since we're doing an IPI to the first cpu anyway, we can use that to pick
up the old tsc, and use that to calculate the adjustment we need to make
to the tsc offset.

Signed-off-by: Avi Kivity &lt;avi@qumranet.com&gt;
</content>
</entry>
<entry>
<title>KVM: Initialize the BSP bit in the APIC_BASE msr correctly</title>
<updated>2007-07-16T09:05:47Z</updated>
<author>
<name>Avi Kivity</name>
</author>
<published>2007-06-13T16:43:19Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=94cea1bb9d050c3200b36420cc03ba744dfd4338'/>
<id>urn:sha1:94cea1bb9d050c3200b36420cc03ba744dfd4338</id>
<content type='text'>
Needs to be set on vcpu 0 only.

Signed-off-by: Avi Kivity &lt;avi@qumranet.com&gt;
</content>
</entry>
<entry>
<title>KVM: VMX: Replace memset(&lt;addr&gt;, 0, PAGESIZE) with clear_page(&lt;addr&gt;)</title>
<updated>2007-07-16T09:05:47Z</updated>
<author>
<name>Shani Moideen</name>
</author>
<published>2007-06-11T04:01:33Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a3870c47891629dae1765358fbaba3c49460f47a'/>
<id>urn:sha1:a3870c47891629dae1765358fbaba3c49460f47a</id>
<content type='text'>
Signed-off-by: Shani Moideen &lt;shani.moideen@wipro.com&gt;
Signed-off-by: Avi Kivity &lt;avi@qumranet.com&gt;
</content>
</entry>
<entry>
<title>KVM: Flush remote tlbs when reducing shadow pte permissions</title>
<updated>2007-07-16T09:05:46Z</updated>
<author>
<name>Avi Kivity</name>
</author>
<published>2007-06-07T16:18:30Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d9e368d61263055eceac2966bb7ea31b89da3425'/>
<id>urn:sha1:d9e368d61263055eceac2966bb7ea31b89da3425</id>
<content type='text'>
When a vcpu causes a shadow tlb entry to have reduced permissions, it
must also clear the tlb on remote vcpus.  We do that by:

- setting a bit on the vcpu that requests a tlb flush before the next entry
- if the vcpu is currently executing, we send an ipi to make sure it
  exits before we continue

Signed-off-by: Avi Kivity &lt;avi@qumranet.com&gt;
</content>
</entry>
</feed>
