Hi, all
I use a qemu-1.4.1/qemu-2.0.0 to run win7 guest, and encounter e1000 NIC
interrupt storm,
because if (!ent-fields.mask (ioapic-irr (1 i))) is always true
in __kvm_ioapic_update_eoi().
Any ideas?
We meet this several times: search the autoneg patches for an example of
On 08/25/2014 03:17 PM, Zhang Haoyu wrote:
Hi, all
I use a qemu-1.4.1/qemu-2.0.0 to run win7 guest, and encounter e1000 NIC
interrupt storm,
because if (!ent-fields.mask (ioapic-irr (1 i))) is always true
in __kvm_ioapic_update_eoi().
Any ideas?
We meet this several times: search
On 08/25/2014 03:17 PM, Zhang Haoyu wrote:
Hi, all
I use a qemu-1.4.1/qemu-2.0.0 to run win7 guest, and encounter e1000 NIC
interrupt storm,
because if (!ent-fields.mask (ioapic-irr (1 i))) is always
true in __kvm_ioapic_update_eoi().
Any ideas?
We meet this several times:
This patch fix bug https://bugzilla.kernel.org/show_bug.cgi?id=82211
(XEN) ..MP-BIOS bug: 8254 timer not connected to IO-APIC
(XEN) ...trying to set up timer (IRQ0) through the 8259A ... failed.
(XEN) ...trying to set up timer as Virtual Wire IRQ... failed.
(XEN) ...trying to set up timer as
On 19/08/14 16:45, Christian Borntraeger wrote:
We dont have to wait for a grace period if there is no oldpid that
we are going to free. putpid also checks for NULL, so this patch
only fences synchronize_rcu.
Signed-off-by: Christian Borntraeger borntrae...@de.ibm.com
---
On 25/08/14 10:24, Christian Borntraeger wrote:
On 19/08/14 16:45, Christian Borntraeger wrote:
We dont have to wait for a grace period if there is no oldpid that
we are going to free. putpid also checks for NULL, so this patch
only fences synchronize_rcu.
Signed-off-by: Christian
Hi, all
I use a qemu-1.4.1/qemu-2.0.0 to run win7 guest, and encounter e1000 NIC
interrupt storm,
because if (!ent-fields.mask (ioapic-irr (1 i))) is always
true in __kvm_ioapic_update_eoi().
Any ideas?
We meet this several times: search the autoneg patches for an example of
Il 25/08/2014 09:58, Wanpeng Li ha scritto:
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index c10408e..b7c0073 100644
--- a/arch/x86/kvm/x86.c
+++ b/arch/x86/kvm/x86.c
@@ -4928,6 +4928,8 @@ static void toggle_interruptibility(struct kvm_vcpu
*vcpu, u32 mask)
if
Hi Paolo,
On Mon, Aug 25, 2014 at 11:01:07AM +0200, Paolo Bonzini wrote:
Il 25/08/2014 09:58, Wanpeng Li ha scritto:
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index c10408e..b7c0073 100644
--- a/arch/x86/kvm/x86.c
+++ b/arch/x86/kvm/x86.c
@@ -4928,6 +4928,8 @@ static void
Il 25/08/2014 11:08, Wanpeng Li ha scritto:
Hi Paolo,
On Mon, Aug 25, 2014 at 11:01:07AM +0200, Paolo Bonzini wrote:
Il 25/08/2014 09:58, Wanpeng Li ha scritto:
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index c10408e..b7c0073 100644
--- a/arch/x86/kvm/x86.c
+++
Hi Paolo,
On Mon, Aug 25, 2014 at 11:16:16AM +0200, Paolo Bonzini wrote:
Il 25/08/2014 11:08, Wanpeng Li ha scritto:
Hi Paolo,
On Mon, Aug 25, 2014 at 11:01:07AM +0200, Paolo Bonzini wrote:
Il 25/08/2014 09:58, Wanpeng Li ha scritto:
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index
On Thu, Aug 21, 2014 at 09:06:39PM +0100, Stefan Hajnoczi wrote:
Dear mentors and core contributors,
Outreach Program for Women is starting the next round in October 2014.
OPW funds women to work on open source software for 12 weeks with the
help of mentors:
s/drity/dirty
Signed-off-by: Tiejun Chen tiejun.c...@intel.com
---
arch/x86/kvm/mmu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
index 9314678..09b9f05 100644
--- a/arch/x86/kvm/mmu.c
+++ b/arch/x86/kvm/mmu.c
@@ -1180,7 +1180,7 @@
This patch serie enables irqfd on ARM.
irqfd framework enables to inject a virtual IRQ into a guest upon an
eventfd trigger. User-side uses KVM_IRQFD VM ioctl to provide KVM with
a kvm_irqfd struct that associates a VM, an eventfd, an IRQ number
(aka. the gsi). When an actor signals the eventfd
This patch enables irqfd on ARM.
irqfd framework enables to inject a virtual IRQ into a guest upon an
eventfd trigger. User-side uses KVM_IRQFD VM ioctl to provide KVM with
a kvm_irqfd struct that associates a VM, an eventfd, an IRQ number
(aka. the gsi). When an actor signals the eventfd
No more needed. Also irq.h is not used on ARM.
Signed-off-by: Eric Auger eric.au...@linaro.org
---
virt/kvm/eventfd.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/virt/kvm/eventfd.c b/virt/kvm/eventfd.c
index 3c5981c..0c712a7 100644
--- a/virt/kvm/eventfd.c
+++ b/virt/kvm/eventfd.c
@@
The PFMF instruction handler blindly wrote the storage key even if
the page was mapped R/O in the host. Lets try a COW before continuing
and bail out in case of errors.
Signed-off-by: Christian Borntraeger borntrae...@de.ibm.com
Reviewed-by: Dominik Dingel din...@linux.vnet.ibm.com
Cc:
Paolo,
the following changes since commit 7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9:
Linux 3.17-rc1 (2014-08-16 10:40:26 -0600)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git
tags/kvm-s390-20140825
for you to fetch changes up
In the early days, we had some special handling for the
KVM_EXIT_S390_SIEIC exit, but this was gone in 2009 with commit
d7b0b5eb3000 (KVM: s390: Make psw available on all exits, not
just a subset).
Now this switch statement is just a sanity check for userspace
not messing with the kvm_run
Implements ARM specific KVM-VFIO device group commands:
- KVM_DEV_VFIO_DEVICE_ASSIGN_IRQ
- KVM_DEV_VFIO_DEVICE_DEASSIGN_IRQ
capability can be queried using KVM_HAS_DEVICE_ATTR.
The new commands enable to set IRQ forwarding on/off for a given
IRQ index of a VFIO platform device.
as soon as a
In case the IRQ is forwarded, the VFIO platform IRQ handler does not
need to disable the IRQ anymore. In that mode, when the handler completes
the IRQ is not deactivated but only its priority is lowered.
Some other actor (typically a guest) is supposed to deactivate the IRQ,
allowing at that time
add a lock related to the rb tree manipulation. The rb tree can be
searched in one thread (irqfd handler for instance) and map/unmap
happen in another.
Signed-off-by: Eric Auger eric.au...@linaro.org
---
virt/kvm/arm/vgic.c | 46 +-
1 file changed, 37
This RFC proposes an integration of ARM: Forwarding physical
interrupts to a guest VM (http://lwn.net/Articles/603514/) in
KVM.
It enables to transform a VFIO platform driver IRQ into a forwarded
IRQ. The direct benefit is that, for a level sensitive IRQ, a VM
switch can be avoided on guest
add a pointer to architecture specific data in kvm_vfio struct
add accessors to keep kvm_vfio private
Signed-off-by: Eric Auger eric.au...@linaro.org
---
arch/arm/include/asm/kvm_host.h | 8
virt/kvm/vfio.c | 21 +
2 files changed, 29 insertions(+)
Fix multiple injection of level sensitive forwarded IRQs.
With current code, the second injection fails since the state bitmaps
are not reset (process_maintenance is not called anymore).
New implementation consists in fully bypassing the vgic state
management for forwarded IRQ (checks are ignored
add functions that implement the gateway to the extended
external VFIO API:
- kvm_vfio_device_get_external_user
- kvm_vfio_device_put_external_user
- kvm_vfio_external_get_type
- kvm_vfio_external_get_base_device
Signed-off-by: Eric Auger eric.au...@linaro.org
---
arch/arm/include/asm/kvm_host.h
New functions are added to be called from ARM KVM-VFIO device.
- vfio_device_get_external_user enables to get a vfio device from
its fd
- vfio_device_put_external_user puts the vfio device
- vfio_external_get_type enables to retrieve the type of the device
(PCI or platform)
-
introduce a new option __KVM_HAVE_ARCH_KVM_VFIO option.
When set the generic KVM-VFIO code calls architecture dependent
code.
the architecture dependent hooks are
- kvm_arch_vfio_has_attr
- kvm_arch_vfio_set_attr
- kvm_arch_vfio_init
- kvm_arch_vfio_destroy
Signed-off-by: Eric Auger
add new device group commands:
- KVM_DEV_VFIO_DEVICE_ASSIGN_IRQ and
KVM_DEV_VFIO_DEVICE_DEASSIGN_IRQ
which enable to turn forwarded IRQ mode on/off.
Signed-off-by: Eric Auger eric.au...@linaro.org
---
Documentation/virtual/kvm/devices/vfio.txt | 25 +
/linux.git
tags/kvm-s390-20140825
for you to fetch changes up to ab3f285f227fec62868037e9b1b1fd18294a83b8:
KVM: s390/mm: try a cow on read only pages for key ops (2014-08-25 14:35:28
+0200)
Here are two fixes for s390 KVM
/pub/scm/linux/kernel/git/kvms390/linux.git
tags/kvm-s390-20140825
for you to fetch changes up to ab3f285f227fec62868037e9b1b1fd18294a83b8:
KVM: s390/mm: try a cow on read only pages for key ops (2014-08-25
14:35:28 +0200
Hello,
2014-08-21, 18:08:09 +0200, Radim Krčmář wrote:
Tracepoint for dynamic PLE window, fired on every potential change.
Signed-off-by: Radim Krčmář rkrc...@redhat.com
---
arch/x86/kvm/trace.h | 30 ++
arch/x86/kvm/vmx.c | 10 --
arch/x86/kvm/x86.c
On Mon, Aug 25, 2014 at 11:16:34AM +0800, Dennis Chen wrote:
On Sun, Aug 24, 2014 at 5:38 PM, Gleb Natapov g...@kernel.org wrote:
On Sun, Aug 24, 2014 at 11:54:32AM +0800, Dennis Chen wrote:
This patch is used to construct the eptp in vmx mode with values
readed from MSR according to the
2014-08-25 15:53+0200, Sabrina Dubroca:
Hello,
2014-08-21, 18:08:09 +0200, Radim Krčmář wrote:
Tracepoint for dynamic PLE window, fired on every potential change.
+#define trace_kvm_ple_window_grow(vcpu_id, new, old) \
+ trace_kvm_ple_window(true, vcpu_id, new, old)
+#define
Il 25/08/2014 16:32, Radim Krčmář ha scritto:
Paolo, can you still fix this just by rebasing?
Maybe I could, but I just pushed the fix to kvm/next as a separate commit.
Paolo
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
2014-08-22 12:45+0800, Wanpeng Li:
Hi Radim,
On Thu, Aug 21, 2014 at 06:50:03PM +0200, Radim Krčmář wrote:
2014-08-21 18:30+0200, Paolo Bonzini:
Il 21/08/2014 18:08, Radim Krčmář ha scritto:
I'm not sure of the usefulness of patch 6, so I'm going to drop it.
I'll keep it in my local
On Mon, Aug 25, 2014 at 11:52 AM, Martin Kletzander mklet...@redhat.com wrote:
On Thu, Aug 21, 2014 at 09:06:39PM +0100, Stefan Hajnoczi wrote:
Regular code contributors to QEMU, KVM, and libvirt are eligible to
participate as mentors.
We also need project ideas that are achievable in 12
- Original Message -
From: Stefan Hajnoczi stefa...@gmail.com
To: Martin Kletzander mklet...@redhat.com
Cc: qemu-devel qemu-de...@nongnu.org, libvir-l...@redhat.com, kvm
kvm@vger.kernel.org, Marina
Zhurakhinskaya mari...@redhat.com
Sent: Monday, August 25, 2014 12:29:27 PM
Subject:
Il 14/08/2014 22:58, Chris J Arges ha scritto:
In the check_counters_many function measure was only being called on the last
counter, causing the pmu test to fail.
I don't understand. measure loops on all N counters and calls
start_event (which in turn calls global_enable) and stop_event
Il 14/08/2014 23:39, Alex Williamson ha scritto:
v3:
- Fix off-by-one identified by Laszlo in 2/3
- Add R-b in 1 3
It turns out that not only do we not follow the SDM guidelines for
reseting MTRR state on vCPU reset, but we really don't even attempt
to keep KVM MTRR state synchronized
On 08/25/2014 11:45 AM, Paolo Bonzini wrote:
Il 14/08/2014 22:58, Chris J Arges ha scritto:
In the check_counters_many function measure was only being called on the last
counter, causing the pmu test to fail.
I don't understand. measure loops on all N counters and calls
start_event
Ok I see now where this patch doesn't make sense.
With the latest kvm tree I get:
sudo ./x86-run x86/pmu.flat -smp 1 -cpu host | grep -v PASS
qemu-system-x86_64 -enable-kvm -device pc-testdev -device
isa-debug-exit,iobase=0xf4,iosize=0x4 -display none -serial stdio
-device pci-testdev
On 08/25/2014 02:32 PM, Paolo Bonzini wrote:
Ok I see now where this patch doesn't make sense.
With the latest kvm tree I get:
sudo ./x86-run x86/pmu.flat -smp 1 -cpu host | grep -v PASS
qemu-system-x86_64 -enable-kvm -device pc-testdev -device
isa-debug-exit,iobase=0xf4,iosize=0x4
Add feature names that are missing on the x86 CPU feature name tables. Both had
migration support implemented many months ago.
Changes v1 - v2:
* Commit message changes only. Added reference to migration support commit IDs.
Note that v1 was not sent as a series, but as separate individual
Migration support for MPX is already implemented (commit
79e9ebebbf2a00c46fcedb6dc7dd5e12bbd30216), so we can add it to the list
of known feature names.
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
---
target-i386/cpu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
tsc_adjust migration support is already implemented (commit
f28558d3d37ad3bc4e35e8ac93f7bf81a0d5622c), so we can add it to the list
of known feature names.
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
---
target-i386/cpu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Fri, 22 Aug 2014 11:01:24 +0200
Antonios Motakis a.mota...@virtualopensystems.com wrote:
As already demonstrated with PCI [1] and the platform bus [2], a
driver_override property in sysfs can be used to bypass the id matching
of a device to a AMBA driver. This can be used by VFIO to bind to
We will need new compat code for the 2.1 machine-types.
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
---
hw/i386/pc_piix.c | 13 -
hw/i386/pc_q35.c | 13 -
2 files changed, 24 insertions(+), 2 deletions(-)
diff --git a/hw/i386/pc_piix.c b/hw/i386/pc_piix.c
index
Changes v1 - v2:
* Commit message and comment changes.
* Update compat code to change pc-*-2.1, not pc-*-2.0.
* Added patch to disable SVM by default in KVM mode.
Most of the bits that make enforce breaks were introduced in 2010 by commit
8560efed6a72a816c0115f41ddb9d79f7ce63f28. The intention
The following CPU features were never supported by neither TCG or KVM,
so they are useless on the CPU model definitions, today:
* CPUID_DTS (DS)
* CPUID_HT
* CPUID_TM
* CPUID_PBE
* CPUID_EXT_DTES64
* CPUID_EXT_DSCPL
* CPUID_EXT_EST
* CPUID_EXT_TM2
* CPUID_EXT_XTPR
* CPUID_EXT_PDCM
*
TCG doesn't support VMX, and nested VMX is not enabled by default on the
KVM kernel module.
So, there's no reason to have VMX enabled by default on the core2duo and
coreduo CPU models, today. Even the newer Intel CPU model definitions
don't have it enabled.
In this case, we need machine-type
The x86_cpu_compat_disable_kvm_features() name was a bit confusing, as
it won't forcibly disable the feature for all CPU models (i.e. add it to
kvm_default_unset_features), but it will instead turn off the KVM
auto-enabling of the feature (i.e. remove it from kvm_default_features),
meaning the
Make SVM be disabled by default on all CPU models when in KVM mode.
Nested SVM is enabled by default in the KVM kernel module, but it is
probably less stable than nested VMX (which is already disabled by
default).
Add a new compat function, x86_cpu_compat_kvm_no_autodisable(), to keep
KVM never supported the CPUID_ACPI flag, so it doesn't make sense to
have it enabled by default when KVM is enabled.
The motivation here is exactly the same we had for the MONITOR flag
(disabled by commit 136a7e9a85d7047461f8153f7d12c514a3d68f69).
And like on the MONITOR flag case, we don't need
On Fri, 22 Aug 2014 11:01:23 +0200
Antonios Motakis a.mota...@virtualopensystems.com wrote:
This patch series depends on the VFIO for PLATFORM devices patch series,
and implements AMBA device support for VFIO.
...
drivers/amba/bus.c| 43 +++
On Mon, Aug 25, 2014 at 10:04 PM, Gleb Natapov g...@kernel.org wrote:
On Mon, Aug 25, 2014 at 11:16:34AM +0800, Dennis Chen wrote:
On Sun, Aug 24, 2014 at 5:38 PM, Gleb Natapov g...@kernel.org wrote:
On Sun, Aug 24, 2014 at 11:54:32AM +0800, Dennis Chen wrote:
This patch is used to construct
On Mon, Aug 25, 2014 at 11:16:16AM +0200, Paolo Bonzini wrote:
Il 25/08/2014 11:08, Wanpeng Li ha scritto:
Hi Paolo,
On Mon, Aug 25, 2014 at 11:01:07AM +0200, Paolo Bonzini wrote:
Il 25/08/2014 09:58, Wanpeng Li ha scritto:
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index
57 matches
Mail list logo
