<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/include/linux/kvm.h, branch linux-2.6.30.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.30.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.30.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2009-04-22T10:52:09Z</updated>
<entry>
<title>KVM: Fix overlapping check for memory slots</title>
<updated>2009-04-22T10:52:09Z</updated>
<author>
<name>Jan Kiszka</name>
</author>
<published>2009-04-13T09:59:32Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=4cd481f68dde99ac416003b825c835f71e364393'/>
<id>urn:sha1:4cd481f68dde99ac416003b825c835f71e364393</id>
<content type='text'>
When checking for overlapping slots on registration of a new one, kvm
currently also considers zero-length (ie. deleted) slots and rejects
requests incorrectly. This finally denies user space from joining slots.
Fix the check by skipping deleted slots and advertise this via a
KVM_CAP_JOIN_MEMORY_REGIONS_WORKS.

Cc: stable@kernel.org
Signed-off-by: Jan Kiszka &lt;jan.kiszka@siemens.com&gt;
Signed-off-by: Avi Kivity &lt;avi@redhat.com&gt;
</content>
</entry>
<entry>
<title>KVM: Correct deassign device ioctl to IOW</title>
<updated>2009-03-24T09:03:15Z</updated>
<author>
<name>Sheng Yang</name>
</author>
<published>2009-03-17T11:27:19Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=bc7a8660df62da3fb5cad025322eda75fbee8731'/>
<id>urn:sha1:bc7a8660df62da3fb5cad025322eda75fbee8731</id>
<content type='text'>
It's IOR by mistake, so fix it before release.

Signed-off-by: Sheng Yang &lt;sheng@linux.intel.com&gt;
Signed-off-by: Avi Kivity &lt;avi@redhat.com&gt;
</content>
</entry>
<entry>
<title>KVM: define KVM_CAP_DEVICE_DEASSIGNMENT</title>
<updated>2009-03-24T09:03:12Z</updated>
<author>
<name>Weidong Han</name>
</author>
<published>2009-02-13T02:50:56Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2df8a40bccf5999261d0d3a82eac5a77678e61bd'/>
<id>urn:sha1:2df8a40bccf5999261d0d3a82eac5a77678e61bd</id>
<content type='text'>
define KVM_CAP_DEVICE_DEASSIGNMENT and KVM_DEASSIGN_PCI_DEVICE
for device deassignment.

the ioctl has been already implemented in the
commit: 0a920356748df4fb06e86c21c23d2ed6d31d37ad

Acked-by: Mark McLoughlin &lt;markmc@redhat.com&gt;
Signed-off-by: Weidong Han &lt;weidong.han@intel.com&gt;
Signed-off-by: Avi Kivity &lt;avi@redhat.com&gt;
</content>
</entry>
<entry>
<title>KVM: Report IRQ injection status to userspace.</title>
<updated>2009-03-24T09:03:11Z</updated>
<author>
<name>Gleb Natapov</name>
</author>
<published>2009-02-04T15:28:14Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=4925663a079c77d95d8685228ad6675fc5639c8e'/>
<id>urn:sha1:4925663a079c77d95d8685228ad6675fc5639c8e</id>
<content type='text'>
IRQ injection status is either -1 (if there was no CPU found
that should except the interrupt because IRQ was masked or
ioapic was misconfigured or ...) or &gt;= 0 in that case the
number indicates to how many CPUs interrupt was injected.
If the value is 0 it means that the interrupt was coalesced
and probably should be reinjected.

Signed-off-by: Gleb Natapov &lt;gleb@redhat.com&gt;
Signed-off-by: Avi Kivity &lt;avi@redhat.com&gt;
</content>
</entry>
<entry>
<title>KVM: Use irq routing API for MSI</title>
<updated>2009-03-24T09:03:09Z</updated>
<author>
<name>Sheng Yang</name>
</author>
<published>2009-02-10T05:57:06Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=79950e1073150909619b7c0f9a39a2fea83a42d8'/>
<id>urn:sha1:79950e1073150909619b7c0f9a39a2fea83a42d8</id>
<content type='text'>
Merge MSI userspace interface with IRQ routing table. Notice the API have been
changed, and using IRQ routing table would be the only interface kvm-userspace
supported.

Signed-off-by: Sheng Yang &lt;sheng@linux.intel.com&gt;
Signed-off-by: Avi Kivity &lt;avi@redhat.com&gt;
</content>
</entry>
<entry>
<title>KVM: Avoid using CONFIG_ in userspace visible headers</title>
<updated>2009-03-24T09:03:06Z</updated>
<author>
<name>Avi Kivity</name>
</author>
<published>2009-01-19T12:57:52Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=91b2ae773d3b168b763237fac33f75b13d891f20'/>
<id>urn:sha1:91b2ae773d3b168b763237fac33f75b13d891f20</id>
<content type='text'>
Kconfig symbols are not available in userspace, and are not stripped by
headers-install.  Avoid their use by adding #defines in &lt;asm/kvm.h&gt; to
suit each architecture.

Signed-off-by: Avi Kivity &lt;avi@redhat.com&gt;
</content>
</entry>
<entry>
<title>KVM: Userspace controlled irq routing</title>
<updated>2009-03-24T09:03:06Z</updated>
<author>
<name>Avi Kivity</name>
</author>
<published>2008-11-19T11:58:46Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=399ec807ddc38ecccf8c06dbde04531cbdc63e11'/>
<id>urn:sha1:399ec807ddc38ecccf8c06dbde04531cbdc63e11</id>
<content type='text'>
Currently KVM has a static routing from GSI numbers to interrupts (namely,
0-15 are mapped 1:1 to both PIC and IOAPIC, and 16:23 are mapped 1:1 to
the IOAPIC).  This is insufficient for several reasons:

- HPET requires non 1:1 mapping for the timer interrupt
- MSIs need a new method to assign interrupt numbers and dispatch them
- ACPI APIC mode needs to be able to reassign the PCI LINK interrupts to the
  ioapics

This patch implements an interrupt routing table (as a linked list, but this
can be easily changed) and a userspace interface to replace the table.  The
routing table is initialized according to the current hardwired mapping.

Signed-off-by: Avi Kivity &lt;avi@redhat.com&gt;
</content>
</entry>
<entry>
<title>KVM: Add support to disable MSI for assigned device</title>
<updated>2009-03-24T09:03:02Z</updated>
<author>
<name>Sheng Yang</name>
</author>
<published>2009-01-06T08:25:11Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=17071fe74fe0fbfdb03cd9b82f2490447cf1f986'/>
<id>urn:sha1:17071fe74fe0fbfdb03cd9b82f2490447cf1f986</id>
<content type='text'>
MSI is always enabled by default for msi2intx=1. But if msi2intx=0, we
have to disable MSI if guest require to do so.

The patch also discard unnecessary msi2intx judgment if guest want to update
MSI state.

Notice KVM_DEV_IRQ_ASSIGN_MSI_ACTION is a mask which should cover all MSI
related operations, though we only got one for now.

Signed-off-by: Sheng Yang &lt;sheng@linux.intel.com&gt;
Signed-off-by: Avi Kivity &lt;avi@redhat.com&gt;
</content>
</entry>
<entry>
<title>KVM: PIT: provide an option to disable interrupt reinjection</title>
<updated>2009-03-24T09:02:55Z</updated>
<author>
<name>Marcelo Tosatti</name>
</author>
<published>2008-12-30T17:55:06Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=52d939a0bf44081bc9f69b4fbdc9e7f416df27c7'/>
<id>urn:sha1:52d939a0bf44081bc9f69b4fbdc9e7f416df27c7</id>
<content type='text'>
Certain clocks (such as TSC) in older 2.6 guests overaccount for lost
ticks, causing severe time drift. Interrupt reinjection magnifies the
problem.

Provide an option to disable it.

[avi: allow room for expansion in case we want to disable reinjection
      of other timers]

Signed-off-by: Marcelo Tosatti &lt;mtosatti@redhat.com&gt;
Signed-off-by: Avi Kivity &lt;avi@redhat.com&gt;
</content>
</entry>
<entry>
<title>KVM: Advertise guest debug capability per-arch</title>
<updated>2009-03-24T09:02:52Z</updated>
<author>
<name>Jan Kiszka</name>
</author>
<published>2008-12-19T17:13:54Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=971cc3dcbc0e020b82f568e61a47b72be03307dd'/>
<id>urn:sha1:971cc3dcbc0e020b82f568e61a47b72be03307dd</id>
<content type='text'>
Limit KVM_CAP_SET_GUEST_DEBUG only to those archs (currently x86) that
support it. This simplifies user space stub implementations.

Signed-off-by: Jan Kiszka &lt;jan.kiszka@siemens.com&gt;
Signed-off-by: Avi Kivity &lt;avi@redhat.com&gt;
</content>
</entry>
</feed>
