Add support for initial write protection of VM memslots. This patch
series assumes that huge PUDs will not be used in 2nd stage tables, which is
always valid on ARMv7
Acked-by: Christoffer Dall christoffer.d...@linaro.org
Signed-off-by: Mario Smarduch m.smard...@samsung.com
---
Patch series adds support for armv7/8 dirty page logging. As we move
towards generic dirty page logging interface we move some common code to
generic layer shared by x86, armv7 and armv8.
armv7/8 Dirty page logging implementation overivew-
- initially write protects memory region 2nd stage page
Allow architectures to override the generic kvm_flush_remote_tlbs()
function via HAVE_KVM_ARCH_TLB_FLUSH_ALL. ARMv7 will need this to
provide its own TLB flush interface.
Reviewed-by: Christoffer Dall christoffer.d...@linaro.org
Reviewed-by: Marc Zyngier marc.zyng...@arm.com
Reviewed-by: Paolo
This patch enables ARMv8 ditry page logging support. Plugs ARMv8 into generic
layer through Kconfig symbol, and drops earlier ARM64 constraints to enable
logging at architecture layer.
Reviewed-by: Christoffer Dall christoffer.d...@linaro.org
Signed-off-by: Mario Smarduch m.smard...@samsung.com
From: Paolo Bonzini pbonz...@redhat.com
We now have a generic function that does most of the work of
kvm_vm_ioctl_get_dirty_log, now use it.
Acked-by: Christoffer Dall christoffer.d...@linaro.org
Signed-off-by: Mario Smarduch m.smard...@samsung.com
---
arch/x86/include/asm/kvm_host.h |3 --
kvm_get_dirty_log() provides generic handling of dirty bitmap, currently reused
by several architectures. Building on that we intrdoduce
kvm_get_dirty_log_protect() adding write protection to mark these pages dirty
for future write access, before next KVM_GET_DIRTY_LOG ioctl call from user
space.
On 01/15, Christian Borntraeger wrote:
--- a/arch/x86/include/asm/spinlock.h
+++ b/arch/x86/include/asm/spinlock.h
@@ -186,7 +186,7 @@ static inline void arch_spin_unlock_wait(arch_spinlock_t
*lock)
__ticket_t head = ACCESS_ONCE(lock-tickets.head);
for (;;) {
-
Folks,
fyi, this is my current patch queue for the next merge window. It
does contain a patch that will disallow ACCESS_ONCE on non-scalar
types.
The tree is part of linux-next and can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/borntraeger/linux.git linux-next
Christian
On 01/15/2015 09:58 AM, Christian Borntraeger wrote:
ACCESS_ONCE does not work reliably on non-scalar types. For
example gcc 4.6 and 4.7 might remove the volatile tag for such
accesses during the SRA (scalar replacement of aggregates) step
(https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58145)
On 15/01/15 08:58, Christian Borntraeger wrote:
ACCESS_ONCE does not work reliably on non-scalar types. For
example gcc 4.6 and 4.7 might remove the volatile tag for such
accesses during the SRA (scalar replacement of aggregates) step
(https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58145)
Am 15.01.2015 um 11:43 schrieb David Vrabel:
On 15/01/15 08:58, Christian Borntraeger wrote:
ACCESS_ONCE does not work reliably on non-scalar types. For
example gcc 4.6 and 4.7 might remove the volatile tag for such
accesses during the SRA (scalar replacement of aggregates) step
ACCESS_ONCE does not work reliably on non-scalar types. For
example gcc 4.6 and 4.7 might remove the volatile tag for such
accesses during the SRA (scalar replacement of aggregates) step
(https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58145)
Change the ppc/kvm code to replace ACCESS_ONCE with
ACCESS_ONCE does not work reliably on non-scalar types. For
example gcc 4.6 and 4.7 might remove the volatile tag for such
accesses during the SRA (scalar replacement of aggregates) step
(https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58145)
Change the p2m code to replace ACCESS_ONCE with
Commit a91ed664749c (kernel: tighten rules for ACCESS ONCE) results in
sparse warnings like Using plain integer as NULL pointer - Let's add a
type cast to the dummy assignment.
To avoid warnings lik sparse: warning: cast to restricted __hc32 we also
use __force on that cast.
Fixes: a91ed664749c
ACCESS_ONCE does not work reliably on non-scalar types. For
example gcc 4.6 and 4.7 might remove the volatile tag for such
accesses during the SRA (scalar replacement of aggregates) step
(https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58145)
Change the ppc/hugetlbfs code to replace ACCESS_ONCE with
ACCESS_ONCE does not work reliably on non-scalar types. For
example gcc 4.6 and 4.7 might remove the volatile tag for such
accesses during the SRA (scalar replacement of aggregates) step
(https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58145)
Fixup gup_pmd_range.
Signed-off-by: Christian
Now that all non-scalar users of ACCESS_ONCE have been converted
to READ_ONCE or ASSIGN once, lets tighten ACCESS_ONCE to only
work on scalar types.
This variant was proposed by Alexei Starovoitov.
Signed-off-by: Christian Borntraeger borntrae...@de.ibm.com
Reviewed-by: Paul E. McKenney
From: Guenter Roeck li...@roeck-us.net
Commit a91ed664749c (kernel: tighten rules for ACCESS ONCE) results in a
compile failure for sh builds with CONFIG_X2TLB enabled.
arch/sh/mm/gup.c: In function 'gup_get_pte':
arch/sh/mm/gup.c:20:2: error: invalid initializer
make[1]: *** [arch/sh/mm/gup.o]
commit 78bff1c8684f (x86/ticketlock: Fix spin_unlock_wait() livelock)
introduced another ACCESS_ONCE case in x86 spinlock.h.
Change that as well.
Signed-off-by: Christian Borntraeger borntrae...@de.ibm.com
Cc: Oleg Nesterov o...@redhat.com
---
arch/x86/include/asm/spinlock.h | 2 +-
1 file
Hi,
Any update on this patch. We could drop patch 3. Any feedback on 1 and 2
?.
-aneesh
Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com writes:
This patch adds helper routine for lock and unlock hpte and use
the same for rest of the code. We don't change any locking rules in this
patch.
On Wed, Jan 07, 2015 at 07:01:10PM -0800, Mario Smarduch wrote:
On 01/07/2015 05:05 AM, Christoffer Dall wrote:
On Sun, Dec 14, 2014 at 11:28:08PM -0800, Mario Smarduch wrote:
This patch adds the same support for PUD huge page as for PMD. Huge PUD is
write protected for initial memory
On 01/08/2015 03:32 AM, Christoffer Dall wrote:
On Wed, Jan 07, 2015 at 07:01:10PM -0800, Mario Smarduch wrote:
On 01/07/2015 05:05 AM, Christoffer Dall wrote:
On Sun, Dec 14, 2014 at 11:28:08PM -0800, Mario Smarduch wrote:
This patch adds the same support for PUD huge page as for PMD. Huge
On Sun, Dec 14, 2014 at 11:28:07PM -0800, Mario Smarduch wrote:
This patch enables ARMv8 ditry page logging support. Plugs ARMv8 into generic
dirty
layer through Kconfig symbol, and drops earlier ARM64 constraints to enable
logging at architecture layer.
On 01/07/2015 05:05 AM, Christoffer Dall wrote:
On Sun, Dec 14, 2014 at 11:28:08PM -0800, Mario Smarduch wrote:
This patch adds the same support for PUD huge page as for PMD. Huge PUD is
write protected for initial memory region write protection. Code to dissolve
huge PUD is supported in
On 01/07/2015 04:47 AM, Christoffer Dall wrote:
On Sun, Dec 14, 2014 at 11:28:07PM -0800, Mario Smarduch wrote:
This patch enables ARMv8 ditry page logging support. Plugs ARMv8 into generic
dirty
yeah.
layer through Kconfig symbol, and drops earlier ARM64
On Sun, Dec 14, 2014 at 11:28:03PM -0800, Mario Smarduch wrote:
Add support to track dirty pages between user space KVM_GET_DIRTY_LOG ioctl
calls. We call kvm_get_dirty_log_protect() function to do most of the work.
Reviewed-by: Marc Zyngier marc.zyng...@arm.com
Signed-off-by: Mario Smarduch
On Sun, Dec 14, 2014 at 11:28:08PM -0800, Mario Smarduch wrote:
This patch adds the same support for PUD huge page as for PMD. Huge PUD is
write protected for initial memory region write protection. Code to dissolve
huge PUD is supported in user_mem_abort(). At this time this code has not
On Sun, Dec 14, 2014 at 11:28:02PM -0800, Mario Smarduch wrote:
Add support for initial write protection of VM memslots. This patch
series assumes that huge PUDs will not be used in 2nd stage tables, which is
always valid on ARMv7
Signed-off-by: Mario Smarduch m.smard...@samsung.com
arch/powerpc/kvm/built-in.o: In function `kvm_no_guest':
arch/powerpc/kvm/book3s_hv_rmhandlers.o:(.text+0x724): undefined reference to
`power7_wakeup_loss'
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
And now for
On Sun, 2014-12-21 at 23:56 +0100, Alexander Graf wrote:
On 21.12.14 15:13, Andreas Schwab wrote:
arch/powerpc/kvm/built-in.o: In function `kvm_no_guest':
arch/powerpc/kvm/book3s_hv_rmhandlers.o:(.text+0x724): undefined reference
to `power7_wakeup_loss'
Ugh. We just removed support for
On 18/12/2014 01:46, Alexander Graf wrote:
Hi Paolo,
This is my current patch queue for ppc. Please pull.
After the merge with Linus' tree, e500v2 compilation will be broken because
commit 69111bac42f5 broke it upstream. Could you please take care to apply the
fix I CC'ed you on for
On 07.12.14 23:29, Rickard Strandqvist wrote:
Remove the function inst_set_field() that is not used anywhere.
This was partially found by using a static code analysis program called
cppcheck.
Signed-off-by: Rickard Strandqvist rickard_strandqv...@spectrumdigital.se
Thanks, applied all
On 04.12.14 06:43, Paul Mackerras wrote:
Currently the calculations of stolen time for PPC Book3S HV guests
uses fields in both the vcpu struct and the kvmppc_vcore struct. The
fields in the kvmppc_vcore struct are protected by the
vcpu-arch.tbacct_lock of the vcpu that has taken
On 04.12.14 01:48, Suresh E. Warrier wrote:
This patch adds trace points in the guest entry and exit code and also
for exceptions handled by the host in kernel mode - hypercalls and page
faults. The new events are added to /sys/kernel/debug/tracing/events
under a new subsystem called kvm_hv.
On 03.12.14 04:48, Paul Mackerras wrote:
When a secondary hardware thread has finished running a KVM guest, we
currently put that thread into nap mode using a nap instruction in
the KVM code. This changes the code so that instead of doing a nap
instruction directly, we instead cause the
On 03.12.14 03:30, Paul Mackerras wrote:
This series of patches is based on Alex Graf's kvm-ppc-queue branch
and is intended for the 3.19 merge window. It starts by removing the
code to support HV KVM on PPC970 processors. This code is hardly used
now since there are not many HV-capable
On 03.12.14 03:30, Paul Mackerras wrote:
From: Michael Ellerman mich...@ellerman.id.au
Some PowerNV systems include a hardware random-number generator.
This HWRNG is present on POWER7+ and POWER8 chips and is capable of
generating one 64-bit random number every microsecond. The random
When injecting an IRQ, we only document which IRQ priority (which translates
to IRQ type) gets injected. However, when reading traces you don't necessarily
have all the numbers in your head to know which IRQ really is meant.
This patch converts the IRQ number field to a symbolic name that is in
From: Paul Mackerras pau...@samba.org
The B (segment size) field in the RB operand for the tlbie
instruction is two bits, which we get from the top two bits of
the first doubleword of the HPT entry to be invalidated. These
bits go in bits 8 and 9 of the RB operand (bits 54 and 55 in IBM
bit
From: Suresh E. Warrier warr...@linux.vnet.ibm.com
This fixes some inaccuracies in the state machine for the virtualized
ICP when implementing the H_IPI hcall (Set_MFFR and related states):
1. The old code wipes out any pending interrupts when the new MFRR is
more favored than the CPPR but
From: Cédric Le Goater c...@fr.ibm.com
When being restored from qemu, the kvm_get_htab_header are in native
endian, but the ptes are big endian.
This patch fixes restore on a KVM LE host. Qemu also needs a fix for
this :
http://lists.nongnu.org/archive/html/qemu-ppc/2014-11/msg8.html
From: Suresh E. Warrier warr...@linux.vnet.ibm.com
The kvmppc_vcore_blocked() code does not check for the wait condition
after putting the process on the wait queue. This means that it is
possible for an external interrupt to become pending, but the vcpu to
remain asleep until the next
From: Rickard Strandqvist rickard_strandqv...@spectrumdigital.se
Removes some functions that are not used anywhere:
kvmppc_core_load_guest_debugstate() kvmppc_core_load_host_debugstate()
This was partially found by using a static code analysis program called
cppcheck.
Signed-off-by: Rickard
From: Anton Blanchard an...@samba.org
The in-kernel XICS emulation is faster than doing it all in QEMU
and it has got a lot of testing, so enable it by default.
Signed-off-by: Anton Blanchard an...@samba.org
Signed-off-by: Paul Mackerras pau...@samba.org
Signed-off-by: Alexander Graf
From: Rickard Strandqvist rickard_strandqv...@spectrumdigital.se
Remove the function inst_set_field() that is not used anywhere.
This was partially found by using a static code analysis program called
cppcheck.
Signed-off-by: Rickard Strandqvist rickard_strandqv...@spectrumdigital.se
From: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
In kvm_test_clear_dirty(), if we find an invalid HPTE we move on to the
next HPTE without unlocking the invalid one. In fact we should never
find an invalid and unlocked HPTE in the rmap chain, but for robustness
we should unlock it. This
From: Mahesh Salgaonkar mah...@linux.vnet.ibm.com
When we get an HMI (hypervisor maintenance interrupt) while in a
guest, we see that guest enters into paused state. The reason is, in
kvmppc_handle_exit_hv it falls through default path and returns to
host instead of resuming guest. This causes
From: Paul Mackerras pau...@samba.org
Currently the calculations of stolen time for PPC Book3S HV guests
uses fields in both the vcpu struct and the kvmppc_vcore struct. The
fields in the kvmppc_vcore struct are protected by the
vcpu-arch.tbacct_lock of the vcpu that has taken responsibility for
From: Paul Mackerras pau...@samba.org
Testing with KSM active in the host showed occasional corruption of
guest memory. Typically a page that should have contained zeroes
would contain values that look like the contents of a user process
stack (values such as 0x_3fff__xxx).
Code
From: Sam Bobroff sam.bobr...@au1.ibm.com
Currently the H_CONFER hcall is implemented in kernel virtual mode,
meaning that whenever a guest thread does an H_CONFER, all the threads
in that virtual core have to exit the guest. This is bad for
performance because it interrupts the other threads
From: Rickard Strandqvist rickard_strandqv...@spectrumdigital.se
Remove the function get_fpr_index() that is not used anywhere.
This was partially found by using a static code analysis program called
cppcheck.
Signed-off-by: Rickard Strandqvist rickard_strandqv...@spectrumdigital.se
From: Rickard Strandqvist rickard_strandqv...@spectrumdigital.se
Remove the function sr_nx() that is not used anywhere.
This was partially found by using a static code analysis program called
cppcheck.
Signed-off-by: Rickard Strandqvist rickard_strandqv...@spectrumdigital.se
Signed-off-by:
From: Paul Mackerras pau...@samba.org
This removes the code that was added to enable HV KVM to work
on PPC970 processors. The PPC970 is an old CPU that doesn't
support virtualizing guest memory. Removing PPC970 support also
lets us remove the code for allocating and managing contiguous
From: Paul Mackerras pau...@samba.org
There are two ways in which a guest instruction can be obtained from
the guest in the guest exit code in book3s_hv_rmhandlers.S. If the
exit was caused by a Hypervisor Emulation interrupt (i.e. an illegal
instruction), the offending instruction is in the
Hi Paolo,
This is my current patch queue for ppc. Please pull.
After the merge with Linus' tree, e500v2 compilation will be broken because
commit 69111bac42f5 broke it upstream. Could you please take care to apply the
fix I CC'ed you on for it?
Thanks!
Alex
The following changes since
From: Suresh E. Warrier warr...@linux.vnet.ibm.com
This patch adds trace points in the guest entry and exit code and also
for exceptions handled by the host in kernel mode - hypercalls and page
faults. The new events are added to /sys/kernel/debug/tracing/events
under a new subsystem called
Allow architectures to override the generic kvm_flush_remote_tlbs()
function via HAVE_KVM_ARCH_TLB_FLUSH_ALL. ARMv7 will need this to
provide its own TLB flush interface.
Reviewed-by: Christoffer Dall christoffer.d...@linaro.org
Reviewed-by: Marc Zyngier marc.zyng...@arm.com
Reviewed-by: Paolo
Patch series adds support for armv7/8 dirty page logging. Also we move
towards generic dirty page logging interface and move some common code to
generic layer currently shared by x86, armv7 and armv8.
armv7/8 Dirty page logging implementation overivew-
- initially write protects memory region
From: Paolo Bonzini pbonz...@redhat.com
We now have a generic function that does most of the work of
kvm_vm_ioctl_get_dirty_log, now use it.
Acked-by: Christoffer Dall christoffer.d...@linaro.org
Signed-off-by: Mario Smarduch m.smard...@samsung.com
---
arch/x86/include/asm/kvm_host.h | 3 --
kvm_get_dirty_log() provides generic handling of dirty bitmap, currently reused
by several architectures. Building on that we intrdoduce
kvm_get_dirty_log_protect() adding write protection to mark these pages dirty
for future write access, before next KVM_GET_DIRTY_LOG ioctl call from user
space.
This patch adds ARMv7 architecture TLB Flush function.
Acked-by: Marc Zyngier marc.zyng...@arm.com
Acked-by: Christoffer Dall christoffer.d...@linaro.org
Signed-off-by: Mario Smarduch m.smard...@samsung.com
---
arch/arm/include/asm/kvm_asm.h | 1 +
arch/arm/include/asm/kvm_host.h | 12
Add support for initial write protection of VM memslots. This patch
series assumes that huge PUDs will not be used in 2nd stage tables, which is
always valid on ARMv7
Signed-off-by: Mario Smarduch m.smard...@samsung.com
---
arch/arm/include/asm/kvm_host.h | 2 +
Add support to track dirty pages between user space KVM_GET_DIRTY_LOG ioctl
calls. We call kvm_get_dirty_log_protect() function to do most of the work.
Reviewed-by: Marc Zyngier marc.zyng...@arm.com
Signed-off-by: Mario Smarduch m.smard...@samsung.com
---
arch/arm/kvm/Kconfig | 1 +
This patch adds support for handling 2nd stage page faults during migration,
it disables faulting in huge pages, and dissolves huge pages to page tables.
In case migration is canceled huge pages are used again.
Also since last version an issues was found on SMP host running SMP Guest
and
This patch adds arm64 helpers to write protect pmds/ptes and retrieve
permissions while logging dirty pages. Also adds prototype to write protect
a memory slot and adds a pmd define to check for read-only pmds.
Reviewed-by: Christoffer Dall christoffer.d...@linaro.org
Signed-off-by: Mario
This patch adds support for arm64 hyp interface to flush all TLBs associated
with VMID.
Reviewed-by: Christoffer Dall christoffer.d...@linaro.org
Signed-off-by: Mario Smarduch m.smard...@samsung.com
---
arch/arm64/kvm/hyp.S | 22 ++
1 file changed, 22 insertions(+)
diff
This patch enables ARMv8 ditry page logging support. Plugs ARMv8 into generic
layer through Kconfig symbol, and drops earlier ARM64 constraints to enable
logging at architecture layer.
Signed-off-by: Mario Smarduch m.smard...@samsung.com
---
arch/arm/include/asm/kvm_host.h | 12
This patch adds the same support for PUD huge page as for PMD. Huge PUD is
write protected for initial memory region write protection. Code to dissolve
huge PUD is supported in user_mem_abort(). At this time this code has not been
tested, but similar approach to current ARMv8 page logging test
Dear Sir
Did your website get hit by Google Penguin update on October 17th 2014? What
basically is Google Penguin Update? It is actually a code name for Google
algorithm which aims at decreasing your websites search engine rankings that
violate Googles guidelines by using black hat SEO
On 09/12/2014 00:12, Mario Smarduch wrote:
Hi Paolo,
I took a closer look at Christoffers comment,
the _log description in x86.c is a repeat of the
_protect description in kvm_main.c.
I'm wondering if description below would be acceptable, or
perhaps you had a reason leaving it as is.
Remove the function sr_nx() that is not used anywhere.
This was partially found by using a static code analysis program called
cppcheck.
Signed-off-by: Rickard Strandqvist rickard_strandqv...@spectrumdigital.se
---
arch/powerpc/kvm/book3s_32_mmu.c |5 -
1 file changed, 5 deletions(-)
Removes some functions that are not used anywhere:
kvmppc_core_load_guest_debugstate() kvmppc_core_load_host_debugstate()
This was partially found by using a static code analysis program called
cppcheck.
Signed-off-by: Rickard Strandqvist rickard_strandqv...@spectrumdigital.se
---
Remove the function get_fpr_index() that is not used anywhere.
This was partially found by using a static code analysis program called
cppcheck.
Signed-off-by: Rickard Strandqvist rickard_strandqv...@spectrumdigital.se
---
arch/powerpc/kvm/book3s_pr.c |5 -
1 file changed, 5
Remove the function inst_set_field() that is not used anywhere.
This was partially found by using a static code analysis program called
cppcheck.
Signed-off-by: Rickard Strandqvist rickard_strandqv...@spectrumdigital.se
---
arch/powerpc/kvm/book3s_paired_singles.c |8
1 file
This patch adds trace points in the guest entry and exit code and also
for exceptions handled by the host in kernel mode - hypercalls and page
faults. The new events are added to /sys/kernel/debug/tracing/events
under a new subsystem called kvm_hv.
Acked-by: Paul Mackerras pau...@samba.org
This series of patches is based on Alex Graf's kvm-ppc-queue branch
and is intended for the 3.19 merge window. It starts by removing the
code to support HV KVM on PPC970 processors. This code is hardly used
now since there are not many HV-capable PPC970 machines (Apple G5
machines are not
There are two ways in which a guest instruction can be obtained from
the guest in the guest exit code in book3s_hv_rmhandlers.S. If the
exit was caused by a Hypervisor Emulation interrupt (i.e. an illegal
instruction), the offending instruction is in the HEIR register
(Hypervisor Emulation
This removes the code that was added to enable HV KVM to work
on PPC970 processors. The PPC970 is an old CPU that doesn't
support virtualizing guest memory. Removing PPC970 support also
lets us remove the code for allocating and managing contiguous
real-mode areas, the code for the
From: Anton Blanchard an...@samba.org
The in-kernel XICS emulation is faster than doing it all in QEMU
and it has got a lot of testing, so enable it by default.
Signed-off-by: Anton Blanchard an...@samba.org
Signed-off-by: Paul Mackerras pau...@samba.org
---
arch/powerpc/kvm/Kconfig | 1 +
1
From: Sam Bobroff sam.bobr...@au1.ibm.com
Currently the H_CONFER hcall is implemented in kernel virtual mode,
meaning that whenever a guest thread does an H_CONFER, all the threads
in that virtual core have to exit the guest. This is bad for
performance because it interrupts the other threads
From: Michael Ellerman mich...@ellerman.id.au
Some PowerNV systems include a hardware random-number generator.
This HWRNG is present on POWER7+ and POWER8 chips and is capable of
generating one 64-bit random number every microsecond. The random
numbers are produced by sampling a set of 64
When a secondary hardware thread has finished running a KVM guest, we
currently put that thread into nap mode using a nap instruction in
the KVM code. This changes the code so that instead of doing a nap
instruction directly, we instead cause the call to power7_nap() that
put the thread into nap
On 11/20/2014 08:01 AM, Steven Rostedt wrote:
On Thu, 20 Nov 2014 13:10:12 +0100
Alexander Graf ag...@suse.de wrote:
On 20.11.14 11:40, Aneesh Kumar K.V wrote:
Suresh E. Warrier warr...@linux.vnet.ibm.com writes:
This patch adds trace points in the guest entry and exit code and also
On Mon, Oct 20, 2014 at 07:59:00PM +0530, Aneesh Kumar K.V wrote:
Minor cleanup
Signed-off-by: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
---
arch/powerpc/kvm/book3s_hv_rm_mmu.c | 25 +
1 file changed, 13 insertions(+), 12 deletions(-)
diff --git
Hi Mario,
On Thu, Nov 13, 2014 at 05:57:41PM -0800, Mario Smarduch wrote:
Patch series adds support for ARMv7 and generic dirty page logging support.
As we try to move towards generic dirty page logging additional logic is
moved
to generic code. Initially x86, armv7 KVM_GET_DIRTY_LOG
On 11/25/2014 02:22 AM, Christoffer Dall wrote:
Hi Mario,
On Thu, Nov 13, 2014 at 05:57:41PM -0800, Mario Smarduch wrote:
Patch series adds support for ARMv7 and generic dirty page logging support.
As we try to move towards generic dirty page logging additional logic is
moved
to generic
On 11/22/2014 11:19 AM, Christoffer Dall wrote:
On Thu, Nov 13, 2014 at 05:57:44PM -0800, Mario Smarduch wrote:
From: Paolo Bonzini pbonz...@redhat.com
We now have a generic function that does most of the work of
kvm_vm_ioctl_get_dirty_log, now use it.
Signed-off-by: Mario Smarduch
On 11/22/2014 11:40 AM, Christoffer Dall wrote:
On Thu, Nov 13, 2014 at 05:57:47PM -0800, Mario Smarduch wrote:
Add support to track dirty pages between user space KVM_GET_DIRTY_LOG ioctl
calls. We call kvm_get_dirty_log_protect() function to do most of the work.
Reviewed-by: Marc Zyngier
On 11/22/2014 11:33 AM, Christoffer Dall wrote:
On Thu, Nov 13, 2014 at 05:57:46PM -0800, Mario Smarduch wrote:
Add support for initial write protection of VM memslots. This patch
series assumes that huge PUDs will not be used in 2nd stage tables, which is
always valid on ARMv7.
On 23.11.14 10:03, Martin Kukac wrote:
Thanks for reply. Yes, module kvm-pr is loaded by modprobe, so that should
not be the problem.
Interesting. With MOL, 3.14 should already work IIRC. You only need 3.17
and above if you want to run Mac OS X in QEMU with KVM.
However if kernel version
On Thu, Nov 13, 2014 at 05:57:42PM -0800, Mario Smarduch wrote:
Allow architectures to override the generic kvm_flush_remote_tlbs()
function via HAVE_KVM_ARCH_TLB_FLUSH_ALL. ARMv7 will need this to
provide its own TLB flush interface.
Reviewed-by: Marc Zyngier marc.zyng...@arm.com
On Thu, Nov 13, 2014 at 05:57:43PM -0800, Mario Smarduch wrote:
kvm_get_dirty_log() provides generic handling of dirty bitmap, currently
reused
by several architectures. Building on that we intrdoduce
kvm_get_dirty_log_protect() adding write protection to mark these pages dirty
for future
On Thu, Nov 13, 2014 at 05:57:44PM -0800, Mario Smarduch wrote:
From: Paolo Bonzini pbonz...@redhat.com
We now have a generic function that does most of the work of
kvm_vm_ioctl_get_dirty_log, now use it.
Signed-off-by: Mario Smarduch m.smard...@samsung.com
---
Hello,
I'm new here, so I hope my question is not offtopic. I found out that
M-o-L now works with KVM-PR, so I wanted to try it myself. I have
PowerMac G5 (dual 970 CPU), Debian Wheezy and kernel 3.14.24 with
kvm-pr. When I load the module and try to start M-o-L 0.9.73 build from
SVN all I
Hello Martin,
Do you load the kernel module PR KVM with modprobe kvm-pr? By the way,
MoL/PR KVM needs the kernel 3.17 or higher.
Rgds,
Christian
On 22.11.2014, you wrote:
Hello,
I'm new here, so I hope my question is not offtopic. I found out that
M-o-L now works with KVM-PR, so I wanted
On 21.11.14 00:45, Cédric Le Goater wrote:
When being restored from qemu, the kvm_get_htab_header are in native
endian, but the ptes are big endian.
This patch fixes restore on a KVM LE host. Qemu also needs a fix for
this :
On 20.11.14 20:31, Suresh E. Warrier wrote:
On 11/20/2014 11:36 AM, Alexander Graf wrote:
On 03.11.14 05:52, Paul Mackerras wrote:
From: Suresh E. Warrier warr...@linux.vnet.ibm.com
The kvmppc_vcore_blocked() code does not check for the wait condition
after putting the process on the
Suresh E. Warrier warr...@linux.vnet.ibm.com writes:
This patch adds trace points in the guest entry and exit code and also
for exceptions handled by the host in kernel mode - hypercalls and page
faults. The new events are added to /sys/kernel/debug/tracing/events
under a new subsystem called
On 20.11.14 11:40, Aneesh Kumar K.V wrote:
Suresh E. Warrier warr...@linux.vnet.ibm.com writes:
This patch adds trace points in the guest entry and exit code and also
for exceptions handled by the host in kernel mode - hypercalls and page
faults. The new events are added to
On Thu, 20 Nov 2014 13:10:12 +0100
Alexander Graf ag...@suse.de wrote:
On 20.11.14 11:40, Aneesh Kumar K.V wrote:
Suresh E. Warrier warr...@linux.vnet.ibm.com writes:
This patch adds trace points in the guest entry and exit code and also
for exceptions handled by the host in kernel
601 - 700 of 8127 matches
Mail list logo
