On 08/05/2012 10:30 PM, Eric Northup wrote:
On Sun, Aug 5, 2012 at 5:58 AM, Gleb Natapov g...@redhat.com wrote:
APIC code has a lot of checks for apic presence and apic HW/SW enable
state. Most common configuration is when each vcpu has in kernel apic
and it is fully enabled. This path series
On 08/05/2012 10:00 PM, Stefan Priebe wrote:
Am 05.08.2012 17:52, schrieb Stefan Priebe:
Am 05.08.2012 12:29, schrieb Avi Kivity:
On 08/05/2012 01:08 PM, Stefan Priebe wrote:
Am 01.08.2012 11:53, schrieb Avi Kivity:
On 08/01/2012 12:42 PM, Stefan Priebe - Profihost AG wrote:
Am 01.08.2012
Am 06.08.2012 10:36, schrieb Avi Kivity:
On 08/05/2012 10:00 PM, Stefan Priebe wrote:
So here are 3 backtraces from booting the rescue system:
http://pastebin.com/raw.php?i=xCy2pEcP
To me they all look the same.
They are. What version of qemu are you using?
latest stable-1.1 branch
On 07/30/2012 05:38 PM, Gleb Natapov wrote:
Optimize rep ins by allowing emulator to write back more than one
datum at a time. Introduce new operand type OP_MEM_STR which tells
writeback() that dst contains pointer to an array that should be written
back as opposite to just one data element.
On Sun, Aug 05, 2012 at 12:30:49PM -0700, Eric Northup wrote:
On Sun, Aug 5, 2012 at 5:58 AM, Gleb Natapov g...@redhat.com wrote:
APIC code has a lot of checks for apic presence and apic HW/SW enable
state. Most common configuration is when each vcpu has in kernel apic
and it is fully
On Mon, Aug 06, 2012 at 11:50:20AM +0300, Avi Kivity wrote:
On 07/30/2012 05:38 PM, Gleb Natapov wrote:
Optimize rep ins by allowing emulator to write back more than one
datum at a time. Introduce new operand type OP_MEM_STR which tells
writeback() that dst contains pointer to an array that
On 08/06/2012 11:58 AM, Gleb Natapov wrote:
On Mon, Aug 06, 2012 at 11:50:20AM +0300, Avi Kivity wrote:
On 07/30/2012 05:38 PM, Gleb Natapov wrote:
Optimize rep ins by allowing emulator to write back more than one
datum at a time. Introduce new operand type OP_MEM_STR which tells
On 08/01/2012 11:59 AM, Takuya Yoshikawa wrote:
This has been already discussed on other threads and the concept itself
is not so controversial.
But since I know that the last patch of this series conflicts with
Paul's recent work, I want to find a way to synchronize with his work
at this
In handling the H_CEDE hypercall, if this vcpu has already been
prodded (with the H_PROD hypercall, which Linux guests don't in fact
use), we branch to a numeric label '1f'. Unfortunately there is
another '1:' label before the one that we want to jump to. This fixes
the problem by using a
The generic KVM code uses SRCU (sleeping RCU) to protect accesses
to the memslots data structures against updates due to userspace
adding, modifying or removing memory slots. We need to do that too,
both to avoid accessing stale copies of the memslots and to avoid
lockdep warnings. This
This series of 5 patches starts off with two fixes that I have posted
previously but not got any response to, and then has 3 patches to
improve our handling of memory slots on PPC. The first of those 3
makes HV-style KVM able to handle deletion and modification of memory
slots properly. The
This is printed once for every RMA or HPT region that get
preallocated. If one preallocates hundreds of such regions
(in order to run hundreds of KVM guests), that gets rather
painful, so make it a bit quieter.
Signed-off-by: Paul Mackerras pau...@samba.org
---
The generic KVM code uses SRCU (sleeping RCU) to protect accesses
to the memslots data structures against updates due to userspace
adding, modifying or removing memory slots. We need to do that too,
both to avoid accessing stale copies of the memslots and to avoid
lockdep warnings. This
From 44067a8ee15021583636bea4cc1d47e5370b8397 Mon Sep 17 00:00:00 2001
From: Paul Mackerras pau...@samba.org
Date: Mon, 30 Jul 2012 16:40:54 +1000
Subject:
At present the HV style of KVM doesn't handle deletion or modification
of memory slots correctly. Deletion occurs when userspace does the
On 07/24/2012 11:43 PM, Alex Williamson wrote:
This new ioctl enables an eventfd to be triggered when an EOI is
written for a specified irqchip pin. The first user of this will
be external device assignment through VFIO, using a level irqfd
for asserting a PCI INTx interrupt and this
On 08/06/2012 01:17 PM, Avi Kivity wrote:
+4.77 KVM_EOIFD
+
+Capability: KVM_CAP_EOIFD
+Architectures: x86
+Type: vm ioctl
+Parameters: struct kvm_eoifd (in)
+Returns: 0 on success, 0 on error
+
+KVM_EOIFD allows userspace to receive interrupt EOI notification
+through an eventfd.
On 08/06/2012 01:38 PM, Avi Kivity wrote:
Regarding the implementation, instead of a linked list, would an array
of counters parallel to the bitmap make it simpler?
Or even, replace the bitmap with an array of counters.
--
error compiling committee.c: too many arguments to function
--
To
On Mon, Aug 06, 2012 at 12:28:05PM +0300, Avi Kivity wrote:
On 08/06/2012 11:58 AM, Gleb Natapov wrote:
On Mon, Aug 06, 2012 at 11:50:20AM +0300, Avi Kivity wrote:
On 07/30/2012 05:38 PM, Gleb Natapov wrote:
Optimize rep ins by allowing emulator to write back more than one
datum at a
On 08/06/2012 02:05 PM, Gleb Natapov wrote:
On Mon, Aug 06, 2012 at 12:28:05PM +0300, Avi Kivity wrote:
On 08/06/2012 11:58 AM, Gleb Natapov wrote:
On Mon, Aug 06, 2012 at 11:50:20AM +0300, Avi Kivity wrote:
On 07/30/2012 05:38 PM, Gleb Natapov wrote:
Optimize rep ins by allowing emulator
Hello Hans
Am Donnerstag, den 19.07.2012, 01:47 +0200 schrieb Hans J. Koch:
You'll hear from me soon, thanks for your work! Comments and reviews
from others are welcome...
Is there any progress on this topic?
--
Gruß
Dominic
Frankfurt Institute for Advanced Studies (FIAS)
On Mon, Aug 06, 2012 at 02:39:52PM +0300, Avi Kivity wrote:
On 08/06/2012 02:05 PM, Gleb Natapov wrote:
On Mon, Aug 06, 2012 at 12:28:05PM +0300, Avi Kivity wrote:
On 08/06/2012 11:58 AM, Gleb Natapov wrote:
On Mon, Aug 06, 2012 at 11:50:20AM +0300, Avi Kivity wrote:
On 07/30/2012 05:38
On 08/06/2012 02:49 PM, Gleb Natapov wrote:
On Mon, Aug 06, 2012 at 02:39:52PM +0300, Avi Kivity wrote:
On 08/06/2012 02:05 PM, Gleb Natapov wrote:
On Mon, Aug 06, 2012 at 12:28:05PM +0300, Avi Kivity wrote:
On 08/06/2012 11:58 AM, Gleb Natapov wrote:
On Mon, Aug 06, 2012 at 11:50:20AM
On 08/06/2012 11:46 AM, Stefan Priebe - Profihost AG wrote:
But still i got the segfault and core dump - this is my main problem? I
mean qemu-kvm master isn't declared as stable. So i don't care about the
slowness here.
What can we do about the core dump and crash?
Okay, I reproduced it;
On Sun, Aug 05, 2012 at 05:16:24PM +0300, Avi Kivity wrote:
On 08/05/2012 03:58 PM, Gleb Natapov wrote:
CC: Jason Baron jba...@redhat.com
CC: Ingo Molnar mi...@elte.hu
CC: Peter Zijlstra a.p.zijls...@chello.nl
Signed-off-by: Gleb Natapov g...@redhat.com
---
kernel/jump_label.c |1
On 08/06/2012 03:12 PM, Avi Kivity wrote:
On 08/06/2012 11:46 AM, Stefan Priebe - Profihost AG wrote:
But still i got the segfault and core dump - this is my main problem? I
mean qemu-kvm master isn't declared as stable. So i don't care about the
slowness here.
What can we do about the
On 08/06/2012 03:37 PM, Avi Kivity wrote:
On 08/06/2012 03:12 PM, Avi Kivity wrote:
On 08/06/2012 11:46 AM, Stefan Priebe - Profihost AG wrote:
But still i got the segfault and core dump - this is my main problem? I
mean qemu-kvm master isn't declared as stable. So i don't care about the
On 08/03/2012 10:37 AM, Xiao Guangrong wrote:
After that, the exported and un-inline function, get_fault_pfn,
can be removed
+#define KVM_PFN_ERR_FAULT(-EFAULT)
+
IMO this symbol isn't needed, just use -EFAULT (and -EHWPOISON etc.)
directly. Just document it in hva_to_pfn(), since
On 08/06/2012 04:01 PM, Avi Kivity wrote:
On 08/03/2012 10:37 AM, Xiao Guangrong wrote:
After that, the exported and un-inline function, get_fault_pfn,
can be removed
+#define KVM_PFN_ERR_FAULT (-EFAULT)
+
IMO this symbol isn't needed, just use -EFAULT (and -EHWPOISON etc.)
On 08/03/2012 10:36 AM, Xiao Guangrong wrote:
There are two bugs:
- the 'error page' is forgot to be released
[ it is unneeded after commit a2766325cf9f9, for backport, we
still do kvm_release_pfn_clean for the error pfn ]
- guest pages are always released regardless of the unmapped
can confirm - this fixed it!
Am 06.08.2012 14:37, schrieb Avi Kivity:
On 08/06/2012 03:12 PM, Avi Kivity wrote:
On 08/06/2012 11:46 AM, Stefan Priebe - Profihost AG wrote:
But still i got the segfault and core dump - this is my main problem? I
mean qemu-kvm master isn't declared as stable. So
On 08/05/2012 03:58 PM, Gleb Natapov wrote:
APIC code has a lot of checks for apic presence and apic HW/SW enable
state. Most common configuration is when each vcpu has in kernel apic
and it is fully enabled. This path series uses jump labels to turn checks
to nops in the common case.
Okay,
Refactor exception prolog to get rid of mfspr srr1 duplicate. This was
introduced by KVM integration, with DO_KVM macro logic expecting srr1 value
earlier in r11.
Reserve r11 to hold srr1's value also required at the end of the prolog and
free up r10 to serve as spare in addition macros.
For
Hook DO_KVM macro into 64-bit booke for KVM integration. Extend interrupt
handlers' parameter list with interrupt vector numbers to accomodate the macro.
Only the bolted version of tlb miss handers is addressed now.
Signed-off-by: Mihai Caraman mihai.cara...@freescale.com
---
Machine check exception handler was using a wrong prolog. Hypervisors like
KVM which are called early from the exception handler rely on the interrupt
source.
Signed-off-by: Mihai Caraman mihai.cara...@freescale.com
---
arch/powerpc/kernel/exceptions-64e.S |2 +-
1 files changed, 1
Embedded.Hypervisor category defines GSPRG0..3 physical registers for guests.
Avoid SPRG4-7 usage as scratch in host exception handlers, otherwise guest
SPRG4-7 registers will be clobbered.
For bolted TLB miss exception handlers, which is the version currently
supported by KVM, use
Critical exception handler on 64-bit booke uses user-visible SPRG3 as scratch.
Restore VDSO information in SPRG3 on exception prolog.
Signed-off-by: Mihai Caraman mihai.cara...@freescale.com
---
arch/powerpc/include/asm/paca.h |3 +++
arch/powerpc/kernel/asm-offsets.c|1 +
Guest Doorbell interrupts use guest save and restore registers. Add a new
Guest Doorbell exception type to accommodate GSRR0/1 SPRs usage in exception
prolog and fix the exception handler.
Signed-off-by: Mihai Caraman mihai.cara...@freescale.com
---
arch/powerpc/include/asm/exception-64e.h |
These patches add core support for KVM on 64-bit Book3E PowerPC, mainly
integrating the DO_KVM macro. KVM arch specific patches will follow shortly.
Mihai Caraman (6):
powerpc/booke64: fix machine check handler to use the right prolog
powerpc/booke64: use GSRR registers in Guest Doorbell
On 05.08.2012 11:18, Avi Kivity wrote:
On 08/03/2012 01:57 PM, Stefan Bader wrote:
No, you're backporting the entire feature. All we need is to expose
RDPMC intercept to the guest.
Oh well, I thought that was the thing you asked for...
Sorry for being unclear.
It should be sufficient
On Thu, Jun 28, 2012 at 2:05 PM, Peter Lieven p...@dlhnet.de wrote:
i debugged my initial problem further and found out that the problem happens
to be that
the main thread is stuck in pause_all_vcpus() on reset or quit commands in
the monitor
if one cpu is stuck in the do-while loop
On Thu, Aug 02, 2012 at 02:43:04PM +0800, Asias He wrote:
Even if it has a payload waiting is highly suboptimal and it should
use a non-blocking sequencing like it is done in the request layer.
So, for REQ_FLUSH, what we need is that send out the VIRTIO_BLK_T_FLUSH and
not to wait.
If it's
Move the init of the irqchip_inject_ioctl field of KVMState out of
kvm_irqchip_create() and into kvm_init(), so that kvm_set_irq()
can be used even when no irqchip is created (for architectures
that support async interrupt notification even without an in
kernel irqchip).
Signed-off-by: Peter
On 3 July 2012 10:01, Christoffer Dall c.d...@virtualopensystems.com wrote:
From: Christoffer Dall cd...@cs.columbia.edu
Userspace can inject IRQs and FIQs through the KVM_IRQ_LINE VM ioctl.
This ioctl is used since the sematics are in fact two lines that can be
either raised or lowered on
On 08/05/2012 04:00 AM, Avi Kivity wrote:
On 08/04/2012 01:32 AM, Benjamin Herrenschmidt wrote:
On Fri, 2012-08-03 at 15:05 -0300, Marcelo Tosatti wrote:
See kvm_arch_process_async_events() call to qemu_system_reset_request()
in target-i386/kvm.c.
The whole thing is fragile, though: we rely
On Sun, 2012-08-05 at 12:00 +0300, Avi Kivity wrote:
So we'll need to test but it looks like we might be able to fix our
problem without a kernel or API change, just by changing qemu to
do the same exit_request trick for our reboot hypercall.
Long run however, I wonder whether we should
On Mon, 2012-08-06 at 13:13 +1000, David Gibson wrote:
So, I'm still trying to nut out the implications for H_CEDE, and think
if there are any other hypercalls that might want to block the guest
for a time. We were considering blocking H_PUT_TCE if qemu devices
had active dma maps on the
Hi
Please send in any agenda items you are interested in covering.
Thanks, 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 Tue, Aug 07, 2012 at 06:57:57AM +1000, Benjamin Herrenschmidt wrote:
On Mon, 2012-08-06 at 13:13 +1000, David Gibson wrote:
So, I'm still trying to nut out the implications for H_CEDE, and think
if there are any other hypercalls that might want to block the guest
for a time. We were
On 08/01/2012 11:59 AM, Takuya Yoshikawa wrote:
This has been already discussed on other threads and the concept itself
is not so controversial.
But since I know that the last patch of this series conflicts with
Paul's recent work, I want to find a way to synchronize with his work
at this
This series of 5 patches starts off with two fixes that I have posted
previously but not got any response to, and then has 3 patches to
improve our handling of memory slots on PPC. The first of those 3
makes HV-style KVM able to handle deletion and modification of memory
slots properly. The
The generic KVM code uses SRCU (sleeping RCU) to protect accesses
to the memslots data structures against updates due to userspace
adding, modifying or removing memory slots. We need to do that too,
both to avoid accessing stale copies of the memslots and to avoid
lockdep warnings. This
This is printed once for every RMA or HPT region that get
preallocated. If one preallocates hundreds of such regions
(in order to run hundreds of KVM guests), that gets rather
painful, so make it a bit quieter.
Signed-off-by: Paul Mackerras pau...@samba.org
---
The generic KVM code uses SRCU (sleeping RCU) to protect accesses
to the memslots data structures against updates due to userspace
adding, modifying or removing memory slots. We need to do that too,
both to avoid accessing stale copies of the memslots and to avoid
lockdep warnings. This
From 44067a8ee15021583636bea4cc1d47e5370b8397 Mon Sep 17 00:00:00 2001
From: Paul Mackerras pau...@samba.org
Date: Mon, 30 Jul 2012 16:40:54 +1000
Subject:
At present the HV style of KVM doesn't handle deletion or modification
of memory slots correctly. Deletion occurs when userspace does the
Refactor exception prolog to get rid of mfspr srr1 duplicate. This was
introduced by KVM integration, with DO_KVM macro logic expecting srr1 value
earlier in r11.
Reserve r11 to hold srr1's value also required at the end of the prolog and
free up r10 to serve as spare in addition macros.
For
Critical exception handler on 64-bit booke uses user-visible SPRG3 as scratch.
Restore VDSO information in SPRG3 on exception prolog.
Signed-off-by: Mihai Caraman mihai.cara...@freescale.com
---
arch/powerpc/include/asm/paca.h |3 +++
arch/powerpc/kernel/asm-offsets.c|1 +
Guest Doorbell interrupts use guest save and restore registers. Add a new
Guest Doorbell exception type to accommodate GSRR0/1 SPRs usage in exception
prolog and fix the exception handler.
Signed-off-by: Mihai Caraman mihai.cara...@freescale.com
---
arch/powerpc/include/asm/exception-64e.h |
These patches add core support for KVM on 64-bit Book3E PowerPC, mainly
integrating the DO_KVM macro. KVM arch specific patches will follow shortly.
Mihai Caraman (6):
powerpc/booke64: fix machine check handler to use the right prolog
powerpc/booke64: use GSRR registers in Guest Doorbell
-Original Message-
From: Kumar Gala [mailto:ga...@kernel.crashing.org]
Sent: Monday, August 06, 2012 9:28 PM
To: Sethi Varun-B16395
Cc: ag...@suse.de; b...@kernel.crashing.org; linuxppc-
d...@lists.ozlabs.org; kvm-ppc@vger.kernel.org
Subject: Re: [PATCH 2/4] powerpc/booke: Merge
On 08/05/2012 04:00 AM, Avi Kivity wrote:
On 08/04/2012 01:32 AM, Benjamin Herrenschmidt wrote:
On Fri, 2012-08-03 at 15:05 -0300, Marcelo Tosatti wrote:
See kvm_arch_process_async_events() call to qemu_system_reset_request()
in target-i386/kvm.c.
The whole thing is fragile, though: we rely
On Sun, 2012-08-05 at 12:00 +0300, Avi Kivity wrote:
So we'll need to test but it looks like we might be able to fix our
problem without a kernel or API change, just by changing qemu to
do the same exit_request trick for our reboot hypercall.
Long run however, I wonder whether we should
On Mon, 2012-08-06 at 13:13 +1000, David Gibson wrote:
So, I'm still trying to nut out the implications for H_CEDE, and think
if there are any other hypercalls that might want to block the guest
for a time. We were considering blocking H_PUT_TCE if qemu devices
had active dma maps on the
On Tue, Aug 07, 2012 at 06:57:57AM +1000, Benjamin Herrenschmidt wrote:
On Mon, 2012-08-06 at 13:13 +1000, David Gibson wrote:
So, I'm still trying to nut out the implications for H_CEDE, and think
if there are any other hypercalls that might want to block the guest
for a time. We were
63 matches
Mail list logo
