On Tue, Sep 02, 2014 at 05:13:49PM +0200, Paolo Bonzini wrote:
This is required for the following patch to work correctly. If a nested page
fault happens during emulation, we must inject a vmexit, not a page fault.
Luckily we already have the required machinery: it is enough to return
On 2014/8/21 21:06, Andre Przywara wrote:
Currently we only need to deal with one MMIO region for the GIC
emulation, but we soon need to extend this. Refactor the existing
code to allow easier addition of different ranges without code
duplication.
Signed-off-by: Andre Przywara
If virtio-blk and virtio-serial share an IRQ, the guest operating system
has to check each virtqueue for activity. Maybe there is some
inefficiency doing that.
AFAIK virtio-serial registers 64 virtqueues (on 31 ports + console) even
if everything is unused.
That could be the
Il 03/09/2014 20:25, Chris J Arges ha scritto:
snip
I'm not sure about the reason for the warp, but indeed the offset and
uptime match (I'll check them against the trace tomorrow) so it's just
that the VM's TSC base is not taken into account correctly.
Can you gather another trace with the
From: Frank Blaschka frank.blasc...@de.ibm.com
This patch adds GISA (Guest Interrupt State Area) support
to s390 kvm. GISA can be used for exitless interrupts. The
patch provides a set of functions for GISA related operations
like accessing GISA fields or registering ISCs for alert.
Exploiters of
From: Frank Blaschka frank.blasc...@de.ibm.com
This patch implements a pci bus for s390x together with some infrastructure
to generate and handle hotplug events. It also provides device
configuration/unconfiguration via sclp instruction interception.
Signed-off-by: Frank Blaschka
From: Frank Blaschka frank.blasc...@de.ibm.com
This patch implemets PCI pass-through kernel support for s390.
Design approach is very similar to the x86 device assignment.
User space executes the KVM_ASSIGN_PCI_DEVICE ioctl to create
a proxy instance in the kernel KVM and connect this instance to
From: Frank Blaschka frank.blasc...@de.ibm.com
This patch exports a couple of zPCI functions. The new pci
pass-through driver for KVM will use this functions to enable the
device with virtualization information and update the device dma
translation table on the host. We add a new interface to
From: Frank Blaschka frank.blasc...@de.ibm.com
This patch adds a new device class handling s390 pci pass-through device
assignment. The approach is very similar to the x86 device assignment.
The device executes the KVM_ASSIGN_PCI_DEVICE ioctl to create a proxy instance
in the kernel KVM and
This set of patches implements pci pass-through support for qemu/KVM on s390.
PCI support on s390 is very different from other platforms.
Major differences are:
1) all PCI operations are driven by special s390 instructions
2) all s390 PCI instructions are privileged
3) PCI config and memory
From: Frank Blaschka frank.blasc...@de.ibm.com
This patch provides a new chsc function to register/unregister
a GIB (Guest Information Block).
Signed-off-by: Frank Blaschka frank.blasc...@de.ibm.com
---
arch/s390/include/asm/cio.h |1
drivers/s390/cio/chsc.c | 50
Il 04/09/2014 11:53, Paolo Bonzini ha scritto:
Il 03/09/2014 20:25, Chris J Arges ha scritto:
snip
I'm not sure about the reason for the warp, but indeed the offset and
uptime match (I'll check them against the trace tomorrow) so it's just
that the VM's TSC base is not taken into account
On Thu, Sep 04, 2014 at 01:33:10PM +0200, Paolo Bonzini wrote:
Il 04/09/2014 11:53, Paolo Bonzini ha scritto:
Il 03/09/2014 20:25, Chris J Arges ha scritto:
snip
I'm not sure about the reason for the warp, but indeed the offset and
uptime match (I'll check them against the trace tomorrow) so
Here is a patchset containing an update on ivshmem specs documentation and
importing ivshmem server and client tools.
These tools have been written from scratch and are not related to what is
available in nahanni repository.
I put them in contrib/ directory as the qemu-doc.texi was already telling
Send a protocol version as the first message from server, clients must close
communication if they don't support this protocol version.
Older QEMUs should be fine with this change in the protocol since they overrides
their own vm_id on reception of an id associated to no eventfd.
Signed-off-by:
When using ivshmem devices, notifications between guests can be sent as
interrupts using a ivshmem-server (typical use described in documentation).
The client is provided as a debug tool.
Signed-off-by: Olivier Matz olivier.m...@6wind.com
Signed-off-by: David Marchand david.march...@6wind.com
---
Add some notes on the parts needed to use ivshmem devices: more specifically,
explain the purpose of an ivshmem server and the basic concept to use the
ivshmem devices in guests.
Move some parts of the documentation and re-organise it.
Signed-off-by: David Marchand david.march...@6wind.com
Commit cbcf2dd3b3d4 (x86: kvm: Make kvm_get_time_and_clockread() nanoseconds
based, 2014-07-16) forgot to add tk-xtime_sec, thus breaking kvmclock on
hosts that have a reliable TSC. Add it back; and since the field boot_ns
is not anymore related to the host boot-based clock, rename
Il 04/09/2014 14:24, Wanpeng Li ha scritto:
On Thu, Sep 04, 2014 at 01:33:10PM +0200, Paolo Bonzini wrote:
Il 04/09/2014 11:53, Paolo Bonzini ha scritto:
Il 03/09/2014 20:25, Chris J Arges ha scritto:
snip
I'm not sure about the reason for the warp, but indeed the offset and
uptime match
On Thu, 2014-09-04 at 12:52 +0200, frank.blasc...@de.ibm.com wrote:
This set of patches implements pci pass-through support for qemu/KVM on s390.
PCI support on s390 is very different from other platforms.
Major differences are:
1) all PCI operations are driven by special s390 instructions
Il 04/09/2014 09:02, Gleb Natapov ha scritto:
On Tue, Sep 02, 2014 at 05:13:49PM +0200, Paolo Bonzini wrote:
This is required for the following patch to work correctly. If a nested
page
fault happens during emulation, we must inject a vmexit, not a page fault.
Luckily we already have
On Thu, Sep 04, 2014 at 12:52:26PM +0200, frank.blasc...@de.ibm.com wrote:
+void kvm_s390_gisa_register_alert(struct kvm *kvm, u32 gisc)
+{
+ int bito = BITS_PER_BYTE * 7 + gisc;
+
+ set_bit(bito ^ (BITS_PER_LONG - 1), kvm-arch.iam);
+}
Just a very minor nit: you could also use
On Thu, Sep 04, 2014 at 04:12:19PM +0200, Paolo Bonzini wrote:
Il 04/09/2014 09:02, Gleb Natapov ha scritto:
On Tue, Sep 02, 2014 at 05:13:49PM +0200, Paolo Bonzini wrote:
This is required for the following patch to work correctly. If a nested
page
fault happens during emulation, we
On Thu, Sep 04, 2014 at 02:50:58PM +0200, David Marchand wrote:
Here is a patchset containing an update on ivshmem specs documentation and
importing ivshmem server and client tools.
These tools have been written from scratch and are not related to what is
available in nahanni repository.
I
On Thu, Sep 04, 2014 at 02:50:59PM +0200, David Marchand wrote:
When using ivshmem devices, notifications between guests can be sent as
interrupts using a ivshmem-server (typical use described in documentation).
The client is provided as a debug tool.
Signed-off-by: Olivier Matz
On Thu, Sep 04, 2014 at 02:50:59PM +0200, David Marchand wrote:
When using ivshmem devices, notifications between guests can be sent as
interrupts using a ivshmem-server (typical use described in documentation).
The client is provided as a debug tool.
Signed-off-by: Olivier Matz
On 09/04/2014 07:58 AM, Paolo Bonzini wrote:
Commit cbcf2dd3b3d4 (x86: kvm: Make kvm_get_time_and_clockread() nanoseconds
based, 2014-07-16) forgot to add tk-xtime_sec, thus breaking kvmclock on
hosts that have a reliable TSC. Add it back; and since the field boot_ns
is not anymore related
Il 04/09/2014 18:00, Chris J Arges ha scritto:
Uptime:
15:58:02 up 1:00, 1 user, load average: 0.59, 0.60, 0.31
Here is the output:
./x86-run x86/kvmclock_test.flat -smp 2 --append 1000 `date +%s`
qemu-system-x86_64 -enable-kvm -device pc-testdev -device
Il 04/09/2014 17:05, Gleb Natapov ha scritto:
if (ctxt-have_exception) {
inject_emulated_exception(vcpu);
- r = EMULATE_DONE;
+ return EMULATE_DONE;
If there was no vmexit we still want to writeback. Perhaps:
writeback =
Il 04/09/2014 17:05, Gleb Natapov ha scritto:
If you do that, KVM gets down to the if (writeback) and writes the
ctxt-eip from L2 into the L1 EIP.
Heh, that's a bummer. We should not write back if an instruction caused a
vmexit.
You're right, that works.
Paolo
-- 8
Il 04/09/2014 14:58, Paolo Bonzini ha scritto:
Commit cbcf2dd3b3d4 (x86: kvm: Make kvm_get_time_and_clockread() nanoseconds
based, 2014-07-16) forgot to add tk-xtime_sec, thus breaking kvmclock on
hosts that have a reliable TSC. Add it back; and since the field boot_ns
is not anymore related
On 09/04/2014 12:14 PM, Paolo Bonzini wrote:
Il 04/09/2014 18:00, Chris J Arges ha scritto:
Uptime:
15:58:02 up 1:00, 1 user, load average: 0.59, 0.60, 0.31
Here is the output:
./x86-run x86/kvmclock_test.flat -smp 2 --append 1000 `date +%s`
qemu-system-x86_64 -enable-kvm -device
On Thu, Sep 4, 2014 at 9:00 AM, Chris J Arges
chris.j.ar...@canonical.com wrote:
On 09/04/2014 07:58 AM, Paolo Bonzini wrote:
Commit cbcf2dd3b3d4 (x86: kvm: Make kvm_get_time_and_clockread() nanoseconds
based, 2014-07-16) forgot to add tk-xtime_sec, thus breaking kvmclock on
hosts that have
The first statement of kvm_dev_ioctl is
long r = -EINVAL;
No need to reassign the same value.
Signed-off-by: Christian Borntraeger borntrae...@de.ibm.com
---
virt/kvm/kvm_main.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
index
The expression `vcpu-spin_loop.in_spin_loop' is always true,
because it is evaluated only when the condition
`!vcpu-spin_loop.in_spin_loop' is false.
Signed-off-by: Christian Borntraeger borntrae...@de.ibm.com
---
virt/kvm/kvm_main.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff
Paolo,
I was playing with some static code checkers. Here is some fallout
from the kvm common code. Only minor things that are not real error,
just redundant statements.
One could argue here and there that these statement make the code easier
to understand. So, please have a look and either drop
__kvm_set_memory_region sets r to EINVAL very early.
Doing it again is not necessary. The same is true later on, where
r is assigned -ENOMEM twice.
Signed-off-by: Christian Borntraeger borntrae...@de.ibm.com
---
virt/kvm/kvm_main.c | 3 ---
1 file changed, 3 deletions(-)
diff --git
Il 04/09/2014 21:00, John Stultz ha scritto:
Hey, thanks for reporting the issue and sending an initial patch (even
if its not quite all sorted yet).
Is the test you're using here available somewhere? Are there any
special requirements to run it?
You need KVM on a machine with
Il 04/09/2014 20:16, Chris J Arges ha scritto:
+boot_ns = timespec_to_ns(tk-total_sleep_time)
++ tk-wall_to_monotonic.tv_sec * (u64)NSEC_PER_SEC
++ tk-wall_to_monotonic.tv_nsec
++ tk-xtime_sec * (u64)NSEC_PER_SEC;
So this means that the above 3.16-based
Il 04/09/2014 21:15, Paolo Bonzini ha scritto:
Il 04/09/2014 20:16, Chris J Arges ha scritto:
+ boot_ns = timespec_to_ns(tk-total_sleep_time)
+ + tk-wall_to_monotonic.tv_sec * (u64)NSEC_PER_SEC
+ + tk-wall_to_monotonic.tv_nsec
+ + tk-xtime_sec *
On 09/04/2014 02:42 PM, Paolo Bonzini wrote:
Il 04/09/2014 21:15, Paolo Bonzini ha scritto:
Il 04/09/2014 20:16, Chris J Arges ha scritto:
+ boot_ns = timespec_to_ns(tk-total_sleep_time)
+ + tk-wall_to_monotonic.tv_sec * (u64)NSEC_PER_SEC
+ + tk-wall_to_monotonic.tv_nsec
Il 04/09/2014 21:13, Christian Borntraeger ha scritto:
Paolo,
I was playing with some static code checkers. Here is some fallout
from the kvm common code. Only minor things that are not real error,
just redundant statements.
One could argue here and there that these statement make the
Il 04/09/2014 22:37, Chris J Arges ha scritto:
- boot_ns = ktime_to_ns(ktime_add(tk-tkr.base_mono, tk-offs_boot));
+ boot_ns = ktime_to_ns(ktime_sub(tk-offs_real, tk-offs_boot));
write_seqcount_begin(vdata-seq);
If it doesn't work, then commit
On 09/04/2014 03:40 PM, Paolo Bonzini wrote:
Il 04/09/2014 22:37, Chris J Arges ha scritto:
- boot_ns = ktime_to_ns(ktime_add(tk-tkr.base_mono, tk-offs_boot));
+ boot_ns = ktime_to_ns(ktime_sub(tk-offs_real, tk-offs_boot));
write_seqcount_begin(vdata-seq);
If it doesn't work, then
On Thu, 4 Sep 2014, Paolo Bonzini wrote:
Commit cbcf2dd3b3d4 (x86: kvm: Make kvm_get_time_and_clockread() nanoseconds
based, 2014-07-16) forgot to add tk-xtime_sec, thus breaking kvmclock on
Errm. How is boottime related to xtime_sec?
hosts that have a reliable TSC. Add it back; and since
Commit cbcf2dd3b3d4 (x86: kvm: Make kvm_get_time_and_clockread() nanoseconds
based, 2014-07-16) used the wrong formula for boot_ns, thus breaking kvmclock on
hosts that have a reliable TSC.
To find the right formula, let's first backport the switch to nanoseconds
to 3.16-era timekeeping logic.
Il 04/09/2014 22:58, Thomas Gleixner ha scritto:
This is simply wrong.
It is.
Now I have no idea why you think it needs to add xtime_sec. If the
result is wrong, then we need to figure out which one of the supplied
values is wrong and not blindly add xtime_sec just because that makes
it
On Thu, 4 Sep 2014, Paolo Bonzini wrote:
Commit cbcf2dd3b3d4 (x86: kvm: Make kvm_get_time_and_clockread() nanoseconds
based, 2014-07-16) used the wrong formula for boot_ns, thus breaking kvmclock
on
hosts that have a reliable TSC.
To find the right formula, let's first backport the switch
On Thu, 4 Sep 2014, Paolo Bonzini wrote:
Il 04/09/2014 22:58, Thomas Gleixner ha scritto:
This is simply wrong.
It is.
Now I have no idea why you think it needs to add xtime_sec. If the
result is wrong, then we need to figure out which one of the supplied
values is wrong and not
On Mon, May 19, 2014 at 01:01:07PM +1000, Gavin Shan wrote:
The patch exports 2 MSI message relevant functions, which will be
used by VFIO PCI driver. The VFIO PCI driver would be built as
a module.
Signed-off-by: Gavin Shan gws...@linux.vnet.ibm.com
Acked-by: Bjorn Helgaas
https://bugzilla.kernel.org/show_bug.cgi?id=83381
Wanpeng Li wanpeng...@linux.intel.com changed:
What|Removed |Added
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=83381
Wanpeng Li wanpeng...@linux.intel.com changed:
What|Removed |Added
CC|
On Thu, Sep 04, 2014 at 04:57:36PM -0600, Bjorn Helgaas wrote:
On Mon, May 19, 2014 at 01:01:07PM +1000, Gavin Shan wrote:
The patch exports 2 MSI message relevant functions, which will be
used by VFIO PCI driver. The VFIO PCI driver would be built as
a module.
Signed-off-by: Gavin Shan
https://bugzilla.kernel.org/show_bug.cgi?id=83381
--- Comment #9 from Alex Williamson alex.william...@redhat.com ---
Is this a regression?
Has it ever worked?
Why is this filed against kvm since it appears to have no relation to qemu or
kvm?
--
You are receiving this mail because:
You are
On 2014/8/21 21:06, Andre Przywara wrote:
+void vgic_v3_dispatch_sgi(struct kvm_vcpu *vcpu, u64 reg)
+{
+ struct kvm *kvm = vcpu-kvm;
+ struct kvm_vcpu *c_vcpu;
+ struct vgic_dist *dist = kvm-arch.vgic;
+ u16 target_cpus;
+ u64 mpidr, mpidr_h, mpidr_l;
+ int sgi,
Hi, all
I encounter below error during git clone kvm.git,
# git clone git://git.kernel.org/pub/scm/virt/kvm/kvm.git kvm_0905
Cloning into 'kvm_0905'...
remote: Counting objects: 3819711, done.
remote: Compressing objects: 100% (575699/575699), done.
remote: Total 3819711 (delta 3219203), reused
Is There specific any reason not to copy extra handler IOVR 35 for e500?
--- a/arch/powerpc/kvm/e500.c
+++ b/arch/powerpc/kvm/e500.c
@@ -527,7 +527,7 @@ static struct kvmppc_ops kvm_ops_e500 = {
static int __init kvmppc_e500_init(void)
{
int r, i;
- unsigned long ivor[3];
+
-Original Message-
From: kvm-ppc-ow...@vger.kernel.org [mailto:kvm-ppc-ow...@vger.kernel.org] On
Behalf Of Amit Tomar
Sent: Thursday, September 04, 2014 8:34 PM
To: ag...@suse.de; kvm-ppc@vger.kernel.org; Caraman Mihai Claudiu-B02008;
pbonz...@redhat.com
Subject: Patch - support
58 matches
Mail list logo
