On 01.08.14 06:50, Madhavan Srinivasan wrote:
This patch adds kernel side support for software breakpoint.
Design is that, by using an illegal instruction, we trap to hypervisor
via Emulation Assistance interrupt, where we check for the illegal instruction
and accordingly we return to Host or
hi,
In kvm_write_tsc() func of kvm, The TSCs will be synchronized unless the time
diff of creating vcpus small than one second.
However, In my enviroment, stress is large, the vcpu creating time is delay,
sometimes the diff time between vcpu creating
is more than one second. In this case, TSCs
On Mon, 2014-08-11 at 09:26 +0200, Alexander Graf wrote:
diff --git a/arch/powerpc/kvm/emulate.c b/arch/powerpc/kvm/emulate.c
index da86d9b..d95014e 100644
--- a/arch/powerpc/kvm/emulate.c
+++ b/arch/powerpc/kvm/emulate.c
This should be book3s_emulate.c.
Any reason we can't make that
On 11.08.14 10:51, Benjamin Herrenschmidt wrote:
On Mon, 2014-08-11 at 09:26 +0200, Alexander Graf wrote:
diff --git a/arch/powerpc/kvm/emulate.c b/arch/powerpc/kvm/emulate.c
index da86d9b..d95014e 100644
--- a/arch/powerpc/kvm/emulate.c
+++ b/arch/powerpc/kvm/emulate.c
This should be
Hi
Please, send any topic that you are interested in covering.
People have complained on the past that I don't cancel the call until
the very last minute. So, what do you think that deadline for
submitting topics is 23:00UTC on Monday?
Call details:
15:00 CEST
13:00 UTC
09:00 EDT
Every
On 06.08.14 18:33, Mihai Caraman wrote:
ePAPR represents hardware threads as cpu node properties in device tree.
So with existing QEMU, hardware threads are simply exposed as vcpus with
one hardware thread.
The e6500 core shares TLBs between hardware threads. Without tlb write
conditional
From: Ulrich Obergfell uober...@redhat.com
Use watchdog_enable_hardlockup_detector() to set hard lockup detection's
default value to false. It's risky to run this detection in a guest, as
false positives are easy to trigger, especially if the host is
overcommitted.
Signed-off-by: Ulrich
From: Ulrich Obergfell uober...@redhat.com
This patch avoids printing the message 'enabled on all CPUs, ...'
multiple times. For example, the issue can occur in the following
scenario:
1) watchdog_nmi_enable() fails to enable PMU counters and sets
cpu0_err.
2) 'echo [0|1]
From: chai wen chaiw.f...@cn.fujitsu.com
For now, soft lockup detector warns once for each case of process softlockup.
But the thread 'watchdog/n' may not always get the cpu at the time slot between
the task switch of two processes hogging that cpu to reset soft_watchdog_warn.
An example would
From: chai wen chaiw.f...@cn.fujitsu.com
Signed-off-by: chai wen chaiw.f...@cn.fujitsu.com
Signed-off-by: Don Zickus dzic...@redhat.com
---
kernel/watchdog.c |5 -
1 files changed, 0 insertions(+), 5 deletions(-)
diff --git a/kernel/watchdog.c b/kernel/watchdog.c
index c3319bd..4c2e11c
From: Ulrich Obergfell uober...@redhat.com
In some cases we don't want hard lockup detection enabled by default.
An example is when running as a guest. Introduce
watchdog_enable_hardlockup_detector(bool)
allowing those cases to disable hard lockup detection. This must be
executed early by the
Just respinning these patches with my sign-off. I keep forgetting which is
easier for Andrew to digest (this way or just me replying with an ack).
Ulrich Obergfell (3):
watchdog: fix print-once on enable
watchdog: control hard lockup detection default
kvm: ensure hard lockup detection is
Thanks for the detailed review.
the last case would be case 5 and the default case would be a BUG().
I agree with the case, but rather than do a BUG() I'm going to print an
error and return -EINVAL. Not worth stopping the host kernel just
because kvm is messed up when we can gracefully exit from
On 08/11/2014 08:09 AM, Juan Quintela wrote:
Hi
Please, send any topic that you are interested in covering.
People have complained on the past that I don't cancel the call until
the very last minute. So, what do you think that deadline for
submitting topics is 23:00UTC on Monday?
I like
The khwrngd thread is started when a hwrng device of sufficient
quality is registered. The virtio-rng device is backed by the
hypervisor, and we trust the hypervisor to provide real entropy. A
malicious hypervisor is a scenario that's ruled out, so we are certain
the quality of randomness we
On Thu, Jul 24, 2014 at 05:56:05PM -0700, Mario Smarduch wrote:
Patch adds HYP interface for global VM TLB invalidation without address
parameter. Generic VM TLB flush calls ARMv7 arch defined TLB flush function.
Signed-off-by: Mario Smarduch m.smard...@samsung.com
---
Remove the parenthesis from the subject line.
On Thu, Jul 24, 2014 at 05:56:06PM -0700, Mario Smarduch wrote:
Patch adds support for initial write protection VM memlsot. This patch series
^^^
stray whitespace of
On Thu, Jul 24, 2014 at 05:56:08PM -0700, Mario Smarduch wrote:
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 will be used again.
On Thu, Jul 24, 2014 at 05:56:07PM -0700, Mario Smarduch wrote:
This patch adds support for keeping track of VM dirty pages. As dirty page log
is retrieved, the pages that have been written are write protected again for
next write and log read.
The dirty log read function is generic for
On Mon, Aug 11, 2014 at 10:20:41AM -0500, Joel Schopp wrote:
Thanks for the detailed review.
the last case would be case 5 and the default case would be a BUG().
I agree with the case, but rather than do a BUG() I'm going to print an
error and return -EINVAL. Not worth stopping the host
From: Michael S. Tsirkin m...@redhat.com
Date: Sun, 10 Aug 2014 21:45:59 +0200
On Sun, Aug 10, 2014 at 11:30:35AM +0300, Razya Ladelsky wrote:
...
And, did your tests actually produce 100% load on both host CPUs?
...
Michael, please do not quote an entire patch just to ask a one line
That said, I don't think this is doing the right thing. I think you
want to refuse running the VM and avoid any stage-2 entried being
created if this is not the case (actually, we may want to check this
after set_vttbr_baddr_mask() or right aftert allocating the stage-2
pgd), because
The current VTTBR_BADDR_MASK only masks 39 bits, which is broken on current
systems. Rather than just add a bit it seems like a good time to also set
things at run-time instead of compile time to accomodate more hardware.
This patch sets TCR_EL2.PS, VTCR_EL2.T0SZ and vttbr_baddr_mask in runtime,
On 08/11/2014 11:49 AM, Amit Shah wrote:
The khwrngd thread is started when a hwrng device of sufficient
quality is registered. The virtio-rng device is backed by the
hypervisor, and we trust the hypervisor to provide real entropy. A
malicious hypervisor is a scenario that's ruled out, so we
Depends on Eric Auger's ARM: KVM: add irqfd support patch.
Enable vfio of platform devices for ARM64. This patch fixes the ARM64 compile.
However this patch has only been compile tested. It seemed worth sharing as it
will allow us to carry both the ARM and ARM64 patches together as we do more
On Wed, 2014-08-06 at 19:33 +0300, Mihai Caraman wrote:
@@ -390,19 +400,30 @@ static void kvmppc_core_vcpu_free_e500mc(struct
kvm_vcpu *vcpu)
static int kvmppc_core_init_vm_e500mc(struct kvm *kvm)
{
- int lpid;
+ int i, lpid;
- lpid = kvmppc_alloc_lpid();
- if
Am 12.08.2014 um 01:36 schrieb Scott Wood scottw...@freescale.com:
On Wed, 2014-08-06 at 19:33 +0300, Mihai Caraman wrote:
@@ -390,19 +400,30 @@ static void kvmppc_core_vcpu_free_e500mc(struct
kvm_vcpu *vcpu)
static int kvmppc_core_init_vm_e500mc(struct kvm *kvm)
{
-int lpid;
+
On 08/11/2014 12:12 PM, Christoffer Dall wrote:
On Thu, Jul 24, 2014 at 05:56:05PM -0700, Mario Smarduch wrote:
Patch adds HYP interface for global VM TLB invalidation without address
parameter. Generic VM TLB flush calls ARMv7 arch defined TLB flush function.
Signed-off-by: Mario Smarduch
On Tue, 2014-08-12 at 01:53 +0200, Alexander Graf wrote:
Am 12.08.2014 um 01:36 schrieb Scott Wood scottw...@freescale.com:
On Wed, 2014-08-06 at 19:33 +0300, Mihai Caraman wrote:
@@ -390,19 +400,30 @@ static void kvmppc_core_vcpu_free_e500mc(struct
kvm_vcpu *vcpu)
static int
On Wed, 2014-08-06 at 12:08 +0530, Bharat Bhushan wrote:
@@ -1249,6 +1284,7 @@ int kvmppc_subarch_vcpu_init(struct kvm_vcpu *vcpu)
setup_timer(vcpu-arch.wdt_timer, kvmppc_watchdog_func,
(unsigned long)vcpu);
+ kvmppc_clear_dbsr();
return 0;
This could use
On 08/11/2014 12:12 PM, Christoffer Dall wrote:
Remove the parenthesis from the subject line.
Hmmm have to check this don't see it my patch file.
On Thu, Jul 24, 2014 at 05:56:06PM -0700, Mario Smarduch wrote:
Patch adds support for initial write protection VM memlsot. This patch
series
On 08/11/2014 12:13 PM, Christoffer Dall wrote:
On Thu, Jul 24, 2014 at 05:56:07PM -0700, Mario Smarduch wrote:
This patch adds support for keeping track of VM dirty pages. As dirty page
log
is retrieved, the pages that have been written are write protected again for
next write and log read.
On 08/11/2014 12:13 PM, Christoffer Dall wrote:
On Thu, Jul 24, 2014 at 05:56:08PM -0700, Mario Smarduch wrote:
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
On 08/11/2014 12:12 PM, Christoffer Dall wrote:
Remove the parenthesis from the subject line.
On Thu, Jul 24, 2014 at 05:56:06PM -0700, Mario Smarduch wrote:
Patch adds support for initial write protection VM memlsot. This patch
series
^^^
Hi all,
Is anyone there can tell the current status of vhost-net on kvm-arm?
Half a year has passed from Isa Ansharullah asked this question:
http://www.spinics.net/lists/kvm-arm/msg08152.html
I have found two patches which have provided the kvm-arm support of
eventfd and irqfd:
1) [RFC PATCH
We may cache the current mmio generation number and stale memslot info
into spte, like this scenarioļ¼
CPU 0 CPU 1
page fault:add a new memslot
read memslot and detecting its a mmio access
From: David Matlack dmatl...@google.com
The following events can lead to an incorrect KVM_EXIT_MMIO bubbling
up to userspace:
(1) Guest accesses gpa X without a memory slot. The gfn is cached in
struct kvm_vcpu_arch (mmio_gfn). On Intel EPT-enabled hosts, KVM sets
the SPTE write-execute-noread
On Monday 11 August 2014 02:45 PM, Alexander Graf wrote:
On 11.08.14 10:51, Benjamin Herrenschmidt wrote:
On Mon, 2014-08-11 at 09:26 +0200, Alexander Graf wrote:
diff --git a/arch/powerpc/kvm/emulate.c b/arch/powerpc/kvm/emulate.c
index da86d9b..d95014e 100644
---
On (Mon) 11 Aug 2014 [15:11:03], H. Peter Anvin wrote:
On 08/11/2014 11:49 AM, Amit Shah wrote:
The khwrngd thread is started when a hwrng device of sufficient
quality is registered. The virtio-rng device is backed by the
hypervisor, and we trust the hypervisor to provide real entropy. A
On 01.08.14 06:50, Madhavan Srinivasan wrote:
This patch adds kernel side support for software breakpoint.
Design is that, by using an illegal instruction, we trap to hypervisor
via Emulation Assistance interrupt, where we check for the illegal instruction
and accordingly we return to Host or
On Mon, 2014-08-11 at 09:26 +0200, Alexander Graf wrote:
diff --git a/arch/powerpc/kvm/emulate.c b/arch/powerpc/kvm/emulate.c
index da86d9b..d95014e 100644
--- a/arch/powerpc/kvm/emulate.c
+++ b/arch/powerpc/kvm/emulate.c
This should be book3s_emulate.c.
Any reason we can't make that
On 11.08.14 10:51, Benjamin Herrenschmidt wrote:
On Mon, 2014-08-11 at 09:26 +0200, Alexander Graf wrote:
diff --git a/arch/powerpc/kvm/emulate.c b/arch/powerpc/kvm/emulate.c
index da86d9b..d95014e 100644
--- a/arch/powerpc/kvm/emulate.c
+++ b/arch/powerpc/kvm/emulate.c
This should be
On 06.08.14 18:33, Mihai Caraman wrote:
ePAPR represents hardware threads as cpu node properties in device tree.
So with existing QEMU, hardware threads are simply exposed as vcpus with
one hardware thread.
The e6500 core shares TLBs between hardware threads. Without tlb write
conditional
On Wed, 2014-08-06 at 11:39 +0300, Mihai Caraman wrote:
SPE exception handlers are now defined for 32-bit e500mc cores even though
SPE unit is not present and CONFIG_SPE is undefined.
Restrict SPE exception handlers to e200/e500 cores adding CONFIG_SPE_POSSIBLE
and consequently guard
On Wed, 2014-08-06 at 19:33 +0300, Mihai Caraman wrote:
@@ -390,19 +400,30 @@ static void kvmppc_core_vcpu_free_e500mc(struct
kvm_vcpu *vcpu)
static int kvmppc_core_init_vm_e500mc(struct kvm *kvm)
{
- int lpid;
+ int i, lpid;
- lpid = kvmppc_alloc_lpid();
- if
Am 12.08.2014 um 01:36 schrieb Scott Wood scottw...@freescale.com:
On Wed, 2014-08-06 at 19:33 +0300, Mihai Caraman wrote:
@@ -390,19 +400,30 @@ static void kvmppc_core_vcpu_free_e500mc(struct
kvm_vcpu *vcpu)
static int kvmppc_core_init_vm_e500mc(struct kvm *kvm)
{
-int lpid;
+
On Tue, 2014-08-12 at 01:53 +0200, Alexander Graf wrote:
Am 12.08.2014 um 01:36 schrieb Scott Wood scottw...@freescale.com:
On Wed, 2014-08-06 at 19:33 +0300, Mihai Caraman wrote:
@@ -390,19 +400,30 @@ static void kvmppc_core_vcpu_free_e500mc(struct
kvm_vcpu *vcpu)
static int
On Wed, 2014-08-06 at 12:08 +0530, Bharat Bhushan wrote:
@@ -1249,6 +1284,7 @@ int kvmppc_subarch_vcpu_init(struct kvm_vcpu *vcpu)
setup_timer(vcpu-arch.wdt_timer, kvmppc_watchdog_func,
(unsigned long)vcpu);
+ kvmppc_clear_dbsr();
return 0;
This could use
48 matches
Mail list logo
