From: Yang Zhang yang.z.zh...@intel.com
The two patches is adding the Posted Interrupt supporting to KVM:
The first patch enabls the feature 'acknowledge interrupt on vmexit'.Since
it is required by Posted interrupt, we need to enable it firstly.
And the second patch is adding the posted
From: Yang Zhang yang.z.zh...@intel.com
The acknowledge interrupt on exit feature controls processor behavior
for external interrupt acknowledgement. When this control is set, the
processor acknowledges the interrupt controller to acquire the
interrupt vector on VM exit.
After enabling this
From: Yang Zhang yang.z.zh...@intel.com
Posted Interrupt allows APIC interrupts to inject into guest directly
without any vmexit.
- When delivering a interrupt to guest, if target vcpu is running,
update Posted-interrupt requests bitmap and send a notification event
to the vcpu. Then the
Sorry for the late response.
Marcelo Tosatti wrote on 2013-02-04:
On Thu, Jan 31, 2013 at 03:55:56PM +0200, Gleb Natapov wrote:
On Thu, Jan 31, 2013 at 11:44:43AM -0200, Marcelo Tosatti wrote:
On Thu, Jan 31, 2013 at 03:38:37PM +0200, Gleb Natapov wrote:
On Thu, Jan 31, 2013 at 11:32:45AM
This patch is too old. Some issues you point out already fixed in v2 patch.
Please review v2 patch and give some comments.
Gleb Natapov wrote on 2013-01-31:
On Thu, Dec 13, 2012 at 03:29:40PM +0800, Yang Zhang wrote:
From: Yang Zhang yang.z.zh...@intel.com
Posted Interrupt allows APIC
On Sun, Feb 03, 2013 at 10:57:00PM -0200, Marcelo Tosatti wrote:
On Thu, Jan 31, 2013 at 03:55:56PM +0200, Gleb Natapov wrote:
On Thu, Jan 31, 2013 at 11:44:43AM -0200, Marcelo Tosatti wrote:
On Thu, Jan 31, 2013 at 03:38:37PM +0200, Gleb Natapov wrote:
On Thu, Jan 31, 2013 at 11:32:45AM
On Sat, 2 Feb 2013 01:37:07 +0100
Andreas Färber afaer...@suse.de wrote:
Move x86_def_t definition to header and embed into X86CPUClass.
Register types per built-in model definition.
Move version initialization from x86_cpudef_setup() to class_init.
Inline cpu_x86_register() into the
Hi!
I get the following error messages over and over again when using vfio in
qemu-kvm:
[ 1692.021403] dmar: DMAR:[DMA Read] Request device [00:02.0] fault addr
1a45aa9000
[ 1692.021403] DMAR:[fault reason 12] non-zero reserved fields in PTE
[ 1692.021416] dmar: DRHD: handling fault status
Commit 21692d1 (Beautify debug output) broke the powerpc build because
it changed the signature for kvm__dump_mem() but didn't update all callers.
Signed-off-by: Michael Ellerman mich...@ellerman.id.au
---
tools/kvm/powerpc/kvm-cpu.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
On Mon, Feb 04, 2013 at 05:05:14PM +0800, Yang Zhang wrote:
From: Yang Zhang yang.z.zh...@intel.com
Posted Interrupt allows APIC interrupts to inject into guest directly
without any vmexit.
- When delivering a interrupt to guest, if target vcpu is running,
update Posted-interrupt
On Mon, Feb 4, 2013 at 2:17 PM, Michael Ellerman mich...@ellerman.id.au wrote:
Commit 21692d1 (Beautify debug output) broke the powerpc build because
it changed the signature for kvm__dump_mem() but didn't update all callers.
Signed-off-by: Michael Ellerman mich...@ellerman.id.au
Applied,
Am 04.02.2013 12:08, schrieb Igor Mammedov:
On Sat, 2 Feb 2013 01:37:07 +0100
Andreas Färber afaer...@suse.de wrote:
Move x86_def_t definition to header and embed into X86CPUClass.
Register types per built-in model definition.
Move version initialization from x86_cpudef_setup() to
Hi
Please send in any agenda topics you are interested in.
Later, Juan.
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Mon, Feb 04, 2013 at 12:45:53PM +, Pekka Enberg wrote:
On Mon, Feb 4, 2013 at 2:17 PM, Michael Ellerman mich...@ellerman.id.au
wrote:
Commit 21692d1 (Beautify debug output) broke the powerpc build because
it changed the signature for kvm__dump_mem() but didn't update all callers.
On Wed, Jan 23, 2013 at 07:12:31PM +0900, Takuya Yoshikawa wrote:
This patch set mitigates another mmu_lock hold time issue. Although
this is not enough and I'm thinking of additional work already, this
alone can reduce the lock hold time to some extent.
Takuya Yoshikawa (8):
KVM: MMU:
On Wed, Jan 23, 2013 at 06:44:52PM +0800, Xiao Guangrong wrote:
On 01/23/2013 06:12 PM, Takuya Yoshikawa wrote:
This patch set mitigates another mmu_lock hold time issue. Although
this is not enough and I'm thinking of additional work already, this
alone can reduce the lock hold time to
When calculating hw_cr0 teh current code masks bits that should be always
on and re-adds them back immediately after. Cleanup the code by masking
only those bits that should be dropped from hw_cr0. This allow us to
get rid of some defines.
Signed-off-by: Gleb Natapov g...@redhat.com
diff --git
On Wed, Jan 23, 2013 at 07:18:11PM +0900, Takuya Yoshikawa wrote:
We noticed that kvm_mmu_zap_all() could take hundreds of milliseconds
for zapping mmu pages with mmu_lock held.
Although we need to do conditional rescheduling for completely
fixing this issue, we can reduce the hold time to
On Mon, Feb 4, 2013 at 3:37 PM, Will Deacon will.dea...@arm.com wrote:
D'oh! I was about to post a patch to fix this (arm is also broken)... I've
dropped the powerpc hunk from my patch (see below).
Applied, thanks Will!
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body
On Mon, Feb 04, 2013 at 11:55:53AM +0200, Gleb Natapov wrote:
On Sun, Feb 03, 2013 at 10:57:00PM -0200, Marcelo Tosatti wrote:
On Thu, Jan 31, 2013 at 03:55:56PM +0200, Gleb Natapov wrote:
On Thu, Jan 31, 2013 at 11:44:43AM -0200, Marcelo Tosatti wrote:
On Thu, Jan 31, 2013 at 03:38:37PM
On Mon, 2013-02-04 at 11:10 +0100, David Gstir wrote:
Hi!
I get the following error messages over and over again when using vfio
in qemu-kvm:
[ 1692.021403] dmar: DMAR:[DMA Read] Request device [00:02.0] fault addr
1a45aa9000
[ 1692.021403] DMAR:[fault reason 12] non-zero reserved
On Mon, 04 Feb 2013 13:52:32 +0100
Andreas Färber afaer...@suse.de wrote:
Am 04.02.2013 12:08, schrieb Igor Mammedov:
On Sat, 2 Feb 2013 01:37:07 +0100
Andreas Färber afaer...@suse.de wrote:
Move x86_def_t definition to header and embed into X86CPUClass.
Register types per built-in
On Sat, 2013-02-02 at 17:20 -0800, Tejun Heo wrote:
Convert to the much saner new idr interface.
Only compile tested.
Signed-off-by: Tejun Heo t...@kernel.org
Cc: Alex Williamson alex.william...@redhat.com
Cc: kvm@vger.kernel.org
---
This patch depends on an earlier idr changes and I
Convert to the much saner new idr interface.
Only compile tested.
v2: Restore accidentally dropped index 0 comment as suggested by
Alex.
Signed-off-by: Tejun Heo t...@kernel.org
Acked-by: Alex Williamson alex.william...@redhat.com
Cc: kvm@vger.kernel.org
---
drivers/vfio/vfio.c | 17
On Sun, 2013-02-03 at 14:10 +, Pandarathil, Vijaymohan R wrote:
- Added vfio_device_get_from_dev() as wrapper to get
reference to vfio_device from struct device.
- Added vfio_device_data() as a wrapper to get device_data from
vfio_device.
Signed-off-by:
On Sun, 2013-02-03 at 14:10 +, Pandarathil, Vijaymohan R wrote:
- New VFIO_SET_IRQ ioctl option to pass the eventfd that is signaled
when
an error occurs in the vfio_pci_device
- Register pci_error_handler for the vfio_pci driver
- When the device
On Sun, 2013-02-03 at 14:10 +, Pandarathil, Vijaymohan R wrote:
- Create eventfd per vfio device assigned to a guest and register an
event handler
- This fd is passed to the vfio_pci driver through the SET_IRQ ioctl
- When the device encounters an error, the
On Sun, 2013-02-03 at 14:10 +, Pandarathil, Vijaymohan R wrote:
Add support for error containment when a VFIO device assigned to a KVM
guest encounters an error. This is for PCIe devices/drivers that support AER
functionality. When the host OS is notified of an error in a device either
On Mon, Feb 04, 2013 at 12:43:45PM -0200, Marcelo Tosatti wrote:
Any example how software relies on such two-interrupts-queued-in-IRR/ISR
behaviour?
Don't know about guests, but KVM relies on it to detect interrupt
coalescing. So if interrupt is set in IRR but not in PIR interrupt will
On 02/03/2013 10:48:29 PM, Bhushan Bharat-R65777 wrote:
-Original Message-
From: Wood Scott-B07421
Sent: Saturday, February 02, 2013 4:09 AM
To: Alexander Graf
Cc: Bhushan Bharat-R65777; kvm-...@vger.kernel.org;
kvm@vger.kernel.org
Subject: Re: [PATCH 8/8] KVM:PPC:booke: Allow
On Mon, 4 Feb 2013 17:05:01 +0100
Igor Mammedov imamm...@redhat.com wrote:
On Mon, 04 Feb 2013 13:52:32 +0100
Andreas Färber afaer...@suse.de wrote:
Am 04.02.2013 12:08, schrieb Igor Mammedov:
On Sat, 2 Feb 2013 01:37:07 +0100
Andreas Färber afaer...@suse.de wrote:
[...]
@@
Hi Asias,
On Fri, 2013-02-01 at 16:16 +0800, Asias He wrote:
In order to take advantages of Paolo's multi-queue virito-scsi, we need
multi-target support in tcm_vhost first. Otherwise all the requests go
to one queue and other queues are idle.
This patch makes:
1. All the targets under
On Mon, Feb 04, 2013 at 07:13:01PM +0200, Gleb Natapov wrote:
On Mon, Feb 04, 2013 at 12:43:45PM -0200, Marcelo Tosatti wrote:
Any example how software relies on such
two-interrupts-queued-in-IRR/ISR behaviour?
Don't know about guests, but KVM relies on it to detect interrupt
On Mon, Feb 04, 2013 at 05:59:52PM -0200, Marcelo Tosatti wrote:
On Mon, Feb 04, 2013 at 07:13:01PM +0200, Gleb Natapov wrote:
On Mon, Feb 04, 2013 at 12:43:45PM -0200, Marcelo Tosatti wrote:
Any example how software relies on such
two-interrupts-queued-in-IRR/ISR behaviour?
Applied. Thanks.
Regards,
Anthony Liguori
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Applied. Thanks.
Regards,
Anthony Liguori
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi.
I'm seeing two issues with Windows7 running as a guest, maybe you can
point me to the right direction :)
1) Shutdown (selected from Windows itself) doesn't work, the system
reboots afterwards.
2) USB passthrough dosesn't work; I connect a camera to it (in order to
upgrade it's AGPS data
On Tue, Jan 29, 2013 at 11:00:07AM +0900, Takuya Yoshikawa wrote:
KVM_SET_USER_MEMORY_REGION forces __kvm_set_memory_region() to identify
what kind of change is being requested by checking the arguments. The
current code does this checking at various points in code and each
condition being
Nice!
- 'Steal time' is the amount of time taken while vcpu is able to run
but not runnable. Maybe 'vmexit latency' is a better name.
- Perhaps it would be good to subtract the time the thread was
involuntarily scheduled out due 'timeslice' expiration. Otherwise,
running a CPU
On Wed, Jan 30, 2013 at 04:45:05PM +0200, Gleb Natapov wrote:
This reverts commit bd4c86eaa6ff10abc4e00d0f45d2a28b10b09df4.
There is not user for kvm_mmu_isolate_page() any more.
Signed-off-by: Gleb Natapov g...@redhat.com
---
arch/x86/kvm/mmu.c | 21 +++--
Applied all
On Thu, Jan 31, 2013 at 12:15:01PM +0200, Gleb Natapov wrote:
On Wed, Jan 30, 2013 at 07:38:37PM +0900, Takuya Yoshikawa wrote:
Patch 1: just rebased for this series.
Patch 2: an API change, so please let me know if you notice any problems.
Takuya Yoshikawa (2):
KVM:
On Mon, 4 Feb 2013 22:01:33 -0200
Marcelo Tosatti mtosa...@redhat.com wrote:
Applied, thanks. It would be good to propagate the enum into
kvm_arch_prepare/commit memory region.
Yes, that's what I want to do after ARM-KVM gets merged.
Takuya
--
To unsubscribe from this list: send the
On Mon, 4 Feb 2013 23:24:01 -0200
Marcelo Tosatti mtosa...@redhat.com wrote:
On Wed, Jan 30, 2013 at 04:45:05PM +0200, Gleb Natapov wrote:
This reverts commit bd4c86eaa6ff10abc4e00d0f45d2a28b10b09df4.
There is not user for kvm_mmu_isolate_page() any more.
Signed-off-by: Gleb Natapov
On Mon, 4 Feb 2013 11:50:00 -0200
Marcelo Tosatti mtosa...@redhat.com wrote:
On Wed, Jan 23, 2013 at 07:18:11PM +0900, Takuya Yoshikawa wrote:
We noticed that kvm_mmu_zap_all() could take hundreds of milliseconds
for zapping mmu pages with mmu_lock held.
Although we need to do
Gleb Natapov wrote on 2013-02-04:
On Mon, Feb 04, 2013 at 05:05:14PM +0800, Yang Zhang wrote:
From: Yang Zhang yang.z.zh...@intel.com
Posted Interrupt allows APIC interrupts to inject into guest directly
without any vmexit.
- When delivering a interrupt to guest, if target vcpu is
On 02/05/2013 04:48 AM, Nicholas A. Bellinger wrote:
Hi Asias,
On Fri, 2013-02-01 at 16:16 +0800, Asias He wrote:
In order to take advantages of Paolo's multi-queue virito-scsi, we need
multi-target support in tcm_vhost first. Otherwise all the requests go
to one queue and other queues are
In order to take advantages of Paolo's multi-queue virito-scsi, we need
multi-target support in tcm_vhost first. Otherwise all the requests go
to one queue and other queues are idle.
This patch makes:
1. All the targets under the wwpn is seen and can be used by guest.
2. No need to pass the tpgt
On 02/04/2013 09:42 PM, Marcelo Tosatti wrote:
On Wed, Jan 23, 2013 at 06:44:52PM +0800, Xiao Guangrong wrote:
On 01/23/2013 06:12 PM, Takuya Yoshikawa wrote:
This patch set mitigates another mmu_lock hold time issue. Although
this is not enough and I'm thinking of additional work already,
Marcelo Tosatti wrote on 2013-02-05:
On Mon, Feb 04, 2013 at 05:59:52PM -0200, Marcelo Tosatti wrote:
On Mon, Feb 04, 2013 at 07:13:01PM +0200, Gleb Natapov wrote:
On Mon, Feb 04, 2013 at 12:43:45PM -0200, Marcelo Tosatti wrote:
Any example how software relies on such
I use the following cmd on rhel6.2 kernel 2.6.32-220.17.1:
x86_64-softmmu/qemu-system-x86_64 -hda win8.img -cdrom
window_8_pro.iso -m 2048 -L pc-bios -cpu host, it will display the
following error:
Your PC needs to restart.
Please hold down the power button.
Error Code: 0x005D
Parameters:
Currently, kvm zaps the large spte if write-protected is needed, the later
read can fault on that spte. Actually, we can make the large spte readonly
instead of making them un-present, the page fault caused by read access can
be avoid
The idea is from Avi:
| As I mentioned before,
There are the simple cleanups for MMU, no function / logic changed.
Marcelo, Gleb, please apply them after applying
[PATCH v3] KVM: MMU: lazily drop large spte
Changelog:
no change, just split them from the previous patchset for good review.
Thanks!
--
To unsubscribe from this list: send the
Use min() to cleanup mapping_level
Signed-off-by: Xiao Guangrong xiaoguangr...@linux.vnet.ibm.com
---
arch/x86/kvm/mmu.c |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
index ff2fc80..fe877da 100644
--- a/arch/x86/kvm/mmu.c
+++
It is only used in debug code, so drop it
Signed-off-by: Xiao Guangrong xiaoguangr...@linux.vnet.ibm.com
---
arch/x86/kvm/mmu.c | 17 +++--
arch/x86/kvm/paging_tmpl.h |9 -
2 files changed, 11 insertions(+), 15 deletions(-)
diff --git a/arch/x86/kvm/mmu.c
Use link_shadow_page to link the sp to the spte in __direct_map
Signed-off-by: Xiao Guangrong xiaoguangr...@linux.vnet.ibm.com
---
arch/x86/kvm/mmu.c | 12
1 files changed, 4 insertions(+), 8 deletions(-)
diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
index 2112c1b..8041454
On Mon, Feb 04, 2013 at 06:47:30PM -0200, Marcelo Tosatti wrote:
On Mon, Feb 04, 2013 at 05:59:52PM -0200, Marcelo Tosatti wrote:
On Mon, Feb 04, 2013 at 07:13:01PM +0200, Gleb Natapov wrote:
On Mon, Feb 04, 2013 at 12:43:45PM -0200, Marcelo Tosatti wrote:
Any example how software
On Tue, Feb 05, 2013 at 03:13:52AM +, Zhang, Yang Z wrote:
Gleb Natapov wrote on 2013-02-04:
On Mon, Feb 04, 2013 at 05:05:14PM +0800, Yang Zhang wrote:
From: Yang Zhang yang.z.zh...@intel.com
Posted Interrupt allows APIC interrupts to inject into guest directly
without any vmexit.
On Tue, Feb 05, 2013 at 08:45:01AM +0200, Gleb Natapov wrote:
+/* Posted interrupt descriptor */
+struct pi_desc *pi;
+
You haven't answered on my previous review why are you trying save 46
bytes here.
Sorry. I cannot get your point. It's just a pointer and only
On 02/03/2013 10:48:29 PM, Bhushan Bharat-R65777 wrote:
-Original Message-
From: Wood Scott-B07421
Sent: Saturday, February 02, 2013 4:09 AM
To: Alexander Graf
Cc: Bhushan Bharat-R65777; kvm-ppc@vger.kernel.org;
k...@vger.kernel.org
Subject: Re: [PATCH 8/8] KVM:PPC:booke: Allow
The Cell processor doesn't support relocation-on interrupts, so we
don't need relocation-on versions of the interrupt vectors that are
purely Cell-specific. This removes them.
Signed-off-by: Paul Mackerras pau...@samba.org
---
arch/powerpc/kernel/exceptions-64s.S | 10 --
1 file
The CFAR (Come From Address Register) is useful for debugging; it
records the address of the most recent taken branch or rfid
instructions. At present, KVM doesn't even try to context switch it,
and the first-level interrupt handlers for some interrupts have a
branch before it gets saved, which
The CFAR (Come-From Address Register) is a useful debugging aid that
exists on POWER7 processors. Currently HV KVM doesn't save or restore
the CFAR register for guest vcpus, making the CFAR of limited use in
guests.
This adds the necessary code to capture the CFAR value saved in the
early
Some of the interrupt vectors on 64-bit POWER server processors are
only 32 bytes long, which is not enough for the full first-level
interrupt handler. For these we currently just have a branch to an
out-of-line handler. However, this means that we corrupt the CFAR
(come-from address register)
63 matches
Mail list logo
