On 27/01/2015 07:35, Nicholas A. Bellinger wrote:
Hi MST Paolo,
So I'm currently working on vhost-scsi support for ANY_LAYOUT, and
wanted to verify some assumptions based upon your earlier emails..
*) When ANY_LAYOUT is negotiated by vhost-scsi, it's expected that
virtio-scsi request +
On 27/01/15 13:17, Christoffer Dall wrote:
On Tue, Jan 27, 2015 at 11:21:38AM +, Marc Zyngier wrote:
On 26/01/15 22:58, Christoffer Dall wrote:
On Wed, Jan 21, 2015 at 06:39:46PM +, Marc Zyngier wrote:
Trying to emulate the behaviour of set/way cache ops is fairly
pointless, as there
Hi all,
I've posted the bolow mail to the qemu-dev mailing list, but I've got no
response there.
That's why I decided to re-post it here as well, and besides that I
think this could be a kvm-specific issue as well.
Some additional thing to note:
I can reproduce the issue on my Debian 7 with
On Tue, Jan 27, 2015 at 10:06:44AM +, David Vrabel wrote:
On 27/01/15 08:35, Jan Beulich wrote:
On 27.01.15 at 02:51, mcg...@do-not-panic.com wrote:
Even if David told you this would be acceptable, I have to question
an abstract model of fixing issues on only 64-bit kernels - this
On Fri, Jan 23, 2015 at 03:19:25PM +, Stefano Stabellini wrote:
On Fri, 23 Jan 2015, Luis R. Rodriguez wrote:
On Wed, Jan 14, 2015 at 11:33:45AM -0800, Luis R. Rodriguez wrote:
From: Luis R. Rodriguez mcg...@suse.com
This v3 addresses Stefano's feedback from the v2 series, namely
On Tue, Jan 27, 2015 at 09:42:22AM +0100, Paolo Bonzini wrote:
On 27/01/2015 07:35, Nicholas A. Bellinger wrote:
Hi MST Paolo,
So I'm currently working on vhost-scsi support for ANY_LAYOUT, and
wanted to verify some assumptions based upon your earlier emails..
*) When
On 27/01/2015 09:42, Paolo Bonzini wrote:
*) When ANY_LAYOUT is negotiated by vhost-scsi, it's expected that
virtio-scsi request + response headers may be (but not always..?)
combined with data-out + data-in payloads into a single iovec.
Note that request and data-out can be combined, and
On 27/01/15 08:35, Jan Beulich wrote:
On 27.01.15 at 02:51, mcg...@do-not-panic.com wrote:
Even if David told you this would be acceptable, I have to question
an abstract model of fixing issues on only 64-bit kernels - this may
be acceptable for distro purposes, but seems hardly the right
On 27.01.15 at 02:51, mcg...@do-not-panic.com wrote:
Even if David told you this would be acceptable, I have to question
an abstract model of fixing issues on only 64-bit kernels - this may
be acceptable for distro purposes, but seems hardly the right
approach for upstream. If 32-bit ones are to
On 27/01/15 08:35, Jan Beulich wrote:
On 27.01.15 at 02:51, mcg...@do-not-panic.com wrote:
Even if David told you this would be acceptable, I have to question
an abstract model of fixing issues on only 64-bit kernels - this may
be acceptable for distro purposes, but seems hardly the right
On Mon, Jan 26, 2015 at 10:35:17PM -0800, Nicholas A. Bellinger wrote:
Hi MST Paolo,
So I'm currently working on vhost-scsi support for ANY_LAYOUT, and
wanted to verify some assumptions based upon your earlier emails..
*) When ANY_LAYOUT is negotiated by vhost-scsi, it's expected that
On Sat, Jan 24, 2015 at 03:02:33AM +0200, Nikolay Nikolaev wrote:
On Mon, Jan 12, 2015 at 7:09 PM, Eric Auger eric.au...@linaro.org wrote:
Hi Nikolay,
On 12/07/2014 10:37 AM, Nikolay Nikolaev wrote:
On IO memory abort, try to handle the MMIO access thorugh the KVM
registered read/write
On 24/01/2015 11:21, Wincy Van wrote:
+ memset(vmx_msr_bitmap_nested, 0xff, PAGE_SIZE);
Most bytes are always 0xff. It's better to initialize it to 0xff once,
and set the bit here if !nested_cpu_has_virt_x2apic_mode(vmcs12).
+ if (nested_cpu_has_virt_x2apic_mode(vmcs12))
Please
On 24/01/2015 11:18, Wincy Van wrote:
v2 --- v3:
1. Add a new field in nested_vmx to avoid the spin lock in v2.
2. Drop send eoi to L1 when doing nested interrupt delivery.
3. Use hardware MSR bitmap to enable nested virtualize x2apic
mode.
I think the patches are mostly okay.
On 27/01/2015 11:57, Joerg Roedel wrote:
From: Joerg Roedel jroe...@suse.de
When assigning devices to large memory guests (=128GB guest
memory in the failure case) the functions to create the
IOMMU page-tables for the whole guest might run for a very
long time. On non-preemptible kernels
On 24/01/2015 11:21, Wincy Van wrote:
+static void nested_vmx_disable_intercept_for_msr(unsigned long
*msr_bitmap_l1,
+ unsigned long
*msr_bitmap_nested,
+ u32 msr, int type)
+{
+ int f =
There is a failure to build on 32-bit hosts:
x86/hypercall.c: In function ‘test_edge’:
x86/hypercall.c:42:2: error: ‘test_rip’ undeclared (first use in this function)
test_rip = 0;
^
This patch fixes this issue.
Signed-off-by: Chris J Arges chris.j.ar...@canonical.com
---
x86/hypercall.c |
On 27/01/2015 21:23, Chris J Arges wrote:
There is a failure to build on 32-bit hosts:
x86/hypercall.c: In function ‘test_edge’:
x86/hypercall.c:42:2: error: ‘test_rip’ undeclared (first use in this
function)
test_rip = 0;
^
This patch fixes this issue.
Signed-off-by: Chris J
The last patch moves the ifdef in a way that causes a compiler warning.
Here fix the ifdefs to isloate x86_64 functions and variables for the test.
Signed-off-by: Chris J Arges chris.j.ar...@canonical.com
---
x86/hypercall.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
On 24/01/2015 11:24, Wincy Van wrote:
if (!nested_cpu_has_virt_x2apic_mode(vmcs12)
!nested_cpu_has_apic_reg_virt(vmcs12)
- !nested_cpu_has_vid(vmcs12))
+ !nested_cpu_has_vid(vmcs12)
+ !nested_cpu_has_posted_intr(vmcs12))
On 09/01/2015 09:29, Tiejun Chen wrote:
Indeed, any invalid memslots should be new-npages = 0,
new-base_gfn = 0 and new-flags = 0 at the same time.
Signed-off-by: Tiejun Chen tiejun.c...@intel.com
---
Paolo,
This is just a small cleanup to follow-up commit, efbeec7098ee, fix
sorting
On Tue, Jan 27, 2015 at 5:55 AM, Mikhail Sennikovskii
mikhail.sennikovs...@profitbricks.com wrote:
Hi all,
I've posted the bolow mail to the qemu-dev mailing list, but I've got no
response there.
That's why I decided to re-post it here as well, and besides that I think
this could be a
On 26/01/15 22:58, Christoffer Dall wrote:
On Wed, Jan 21, 2015 at 06:39:46PM +, Marc Zyngier wrote:
Trying to emulate the behaviour of set/way cache ops is fairly
pointless, as there are too many ways we can end-up missing stuff.
Also, there is some system caches out there that simply
From: Joerg Roedel jroe...@suse.de
When assigning devices to large memory guests (=128GB guest
memory in the failure case) the functions to create the
IOMMU page-tables for the whole guest might run for a very
long time. On non-preemptible kernels this might cause
Soft-Lockup warnings. Fix these
This patch avoids unnecessary dirty GPA logging to PML buffer in EPT violation
path by setting D-bit manually prior to the occurrence of the write from guest.
We only set D-bit manually in set_spte, and leave fast_page_fault path
unchanged, as fast_page_fault is very unlikely to happen in case of
We don't have to write protect guest memory for dirty logging if architecture
supports hardware dirty logging, such as PML on VMX, so rename it to be more
generic.
Signed-off-by: Kai Huang kai.hu...@linux.intel.com
---
arch/arm/kvm/mmu.c | 18 --
arch/x86/kvm/mmu.c |
This patch adds new kvm_x86_ops dirty logging hooks to enable/disable dirty
logging for particular memory slot, and to flush potentially logged dirty GPAs
before reporting slot-dirty_bitmap to userspace.
kvm x86 common code calls these hooks when they are available so PML logic can
be hidden to
This patch adds new mmu layer functions to clear/set D-bit for memory slot, and
to write protect superpages for memory slot.
In case of PML, CPU logs the dirty GPA automatically to PML buffer when CPU
updates D-bit from 0 to 1, therefore we don't have to write protect 4K pages,
instead, we only
This patch changes the second parameter of kvm_mmu_slot_remove_write_access from
'slot id' to 'struct kvm_memory_slot *' to align with kvm_x86_ops dirty logging
hooks, which will be introduced in further patch.
Better way is to change second parameter of kvm_arch_commit_memory_region from
'struct
This patch adds PML support in VMX. A new module parameter 'enable_pml' is added
to allow user to enable/disable it manually.
Signed-off-by: Kai Huang kai.hu...@linux.intel.com
---
arch/x86/include/asm/vmx.h | 4 +
arch/x86/include/uapi/asm/vmx.h | 1 +
arch/x86/kvm/trace.h|
-Original Message-
From: Alex Williamson [mailto:alex.william...@redhat.com]
Sent: Wednesday, January 28, 2015 11:44 AM
To: Wu, Feng
Cc: t...@linutronix.de; mi...@redhat.com; h...@zytor.com; x...@kernel.org;
g...@kernel.org; pbonz...@redhat.com; dw...@infradead.org;
On 2015-01-28 03:10:23, Jidong Xiao wrote:
On Tue, Jan 27, 2015 at 5:55 AM, Mikhail Sennikovskii
mikhail.sennikovs...@profitbricks.com wrote:
Hi all,
I've posted the bolow mail to the qemu-dev mailing list, but I've got no
response there.
That's why I decided to re-post it here as
On Wed, Jan 28, 2015 at 5:37 AM, Paolo Bonzini pbonz...@redhat.com wrote:
On 24/01/2015 11:21, Wincy Van wrote:
+ memset(vmx_msr_bitmap_nested, 0xff, PAGE_SIZE);
Most bytes are always 0xff. It's better to initialize it to 0xff once,
and set the bit here if
On Wed, Jan 28, 2015 at 6:06 AM, Paolo Bonzini pbonz...@redhat.com wrote:
On 24/01/2015 11:18, Wincy Van wrote:
v2 --- v3:
1. Add a new field in nested_vmx to avoid the spin lock in v2.
2. Drop send eoi to L1 when doing nested interrupt delivery.
3. Use hardware MSR bitmap to enable
On Wed, Jan 28, 2015 at 5:39 AM, Paolo Bonzini pbonz...@redhat.com wrote:
On 24/01/2015 11:21, Wincy Van wrote:
+static void nested_vmx_disable_intercept_for_msr(unsigned long
*msr_bitmap_l1,
+ unsigned long
*msr_bitmap_nested,
+
On Wed, Jan 28, 2015 at 5:55 AM, Paolo Bonzini pbonz...@redhat.com wrote:
On 24/01/2015 11:24, Wincy Van wrote:
if (!nested_cpu_has_virt_x2apic_mode(vmcs12)
!nested_cpu_has_apic_reg_virt(vmcs12)
- !nested_cpu_has_vid(vmcs12))
+
Hi Andre,
On Tue, Jan 27, 2015 at 3:31 PM, Andre Przywara andre.przyw...@arm.com wrote:
Hi Nikolay,
On 24/01/15 11:59, Nikolay Nikolaev wrote:
In io_mem_abort remove the call to vgic_handle_mmio. The target is to have
a single MMIO handling path - that is through the kvm_io_bus_ API.
On Tue, Jan 27, 2015 at 11:21:38AM +, Marc Zyngier wrote:
On 26/01/15 22:58, Christoffer Dall wrote:
On Wed, Jan 21, 2015 at 06:39:46PM +, Marc Zyngier wrote:
Trying to emulate the behaviour of set/way cache ops is fairly
pointless, as there are too many ways we can end-up missing
Hi Nikolay,
On 24/01/15 11:59, Nikolay Nikolaev wrote:
In io_mem_abort remove the call to vgic_handle_mmio. The target is to have
a single MMIO handling path - that is through the kvm_io_bus_ API.
Register a kvm_io_device in kvm_vgic_init on the whole vGIC MMIO region.
Both read and write
Hi
Please, send any topic that you are interested in covering.
Thanks, Juan.
Call details:
By popular demand, a google calendar public entry with it
https://www.google.com/calendar/embed?src=dG9iMXRqcXAzN3Y4ZXZwNzRoMHE4a3BqcXNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ
(Let me know if you
Hi,
On 27/01/15 17:26, Eric Auger wrote:
On 01/27/2015 05:51 PM, Nikolay Nikolaev wrote:
Hi Andre,
On Tue, Jan 27, 2015 at 3:31 PM, Andre Przywara andre.przyw...@arm.com
wrote:
Hi Nikolay,
On 24/01/15 11:59, Nikolay Nikolaev wrote:
In io_mem_abort remove the call to vgic_handle_mmio.
-Original Message-
From: Wu, Feng
Sent: Wednesday, January 21, 2015 10:26 AM
To: t...@linutronix.de; mi...@redhat.com; h...@zytor.com; x...@kernel.org;
g...@kernel.org; pbonz...@redhat.com; dw...@infradead.org;
j...@8bytes.org; alex.william...@redhat.com; jiang@linux.intel.com
This patch series adds Page Modification Logging (PML) support in VMX.
1) Introduction
PML is a new feature on Intel's Boardwell server platfrom targeted to reduce
overhead of dirty logging mechanism.
The specification can be found at:
On Wed, 2015-01-28 at 03:01 +, Wu, Feng wrote:
-Original Message-
From: Wu, Feng
Sent: Wednesday, January 21, 2015 10:26 AM
To: t...@linutronix.de; mi...@redhat.com; h...@zytor.com; x...@kernel.org;
g...@kernel.org; pbonz...@redhat.com; dw...@infradead.org;
44 matches
Mail list logo
