On 2012-10-29 09:31, Xiao Guangrong wrote:
On 10/29/2012 03:44 PM, Jan Kiszka wrote:
On 2012-10-29 08:09, Xiao Guangrong wrote:
Jan,
On 10/26/2012 06:35 PM, Jan Kiszka wrote:
This has two problems: We know it breaks at least Win 95 that overwrites
its F-segment during boot. And it applies
On 10/30/2012 01:44 PM, Peter Zijlstra wrote:
On Tue, 2012-10-30 at 11:27 +0530, Raghavendra K T wrote:
Okay, now IIUC, usage of *any* global measure is bad?
Yep, people like to carve up their machines, esp. now that they're
somewhat bigger than they used to be. This can result in very
On 10/31/2012 02:03 PM, Jan Kiszka wrote:
On 2012-10-29 09:31, Xiao Guangrong wrote:
On 10/29/2012 03:44 PM, Jan Kiszka wrote:
On 2012-10-29 08:09, Xiao Guangrong wrote:
Jan,
On 10/26/2012 06:35 PM, Jan Kiszka wrote:
This has two problems: We know it breaks at least Win 95 that overwrites
On 10/30/2012 05:47 PM, Andrew Theurer wrote:
On Mon, 2012-10-29 at 19:36 +0530, Raghavendra K T wrote:
In some special scenarios like #vcpu = #pcpu, PLE handler may
prove very costly, because there is no need to iterate over vcpus
and do unsuccessful yield_to burning CPU.
Similarly, when we
On 2012-10-31 07:35, Xiao Guangrong wrote:
We can not do that for pflash is a RD device which can not be directly
written,
kvm can not emulate the instruction which implicitly write the memory.
(e.g:
using this area as stack).
Isn't enabling ROMD support for KVM that whole point of your
On 10/31/2012 02:46 PM, Jan Kiszka wrote:
Please allow me to clarify it more clearly.
The flash is ROMD device means guest can not write it, any kinds of guest
write
access on this device can cause vmexit to kvm and return to userspace.
We should pay more attention on it if we execute the
On 2012-10-31 08:01, Xiao Guangrong wrote:
On 10/31/2012 02:46 PM, Jan Kiszka wrote:
Please allow me to clarify it more clearly.
The flash is ROMD device means guest can not write it, any kinds of guest
write
access on this device can cause vmexit to kvm and return to userspace.
We
On Thu, 25 Oct 2012, Kirill A. Shutemov wrote:
vec is 0x in virtio_pci__specific_io_out() on crash.
Let's add proper bounds checking there. It doesn't not solves the issue
with booting crashkernel, but fix lkvm crash.
There's no sign-off for the patch. Kirill, care to update the patch
Il 31/10/2012 00:14, Marcelo Tosatti ha scritto:
Migrate 16 bytes for en/sts fields (which is the correct size),
increase version to 3, and document how to support incoming
migration from qemu-kvm 1.2.
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
diff --git a/hw/acpi_piix4.c
-Original Message-
From: kexec-boun...@lists.infradead.org
[mailto:kexec-boun...@lists.infradead.org] On Behalf Of zhangyanfei
Sent: Wednesday, October 31, 2012 12:34 PM
To: x...@kernel.org; ke...@lists.infradead.org; Avi Kivity; Marcelo
Tosatti
Cc: linux-ker...@vger.kernel.org;
From: Eduardo Habkost ehabk...@redhat.com
Rationale:
* -cpu host is available only when using KVM
* The current implementation of -cpu check/enforce
(check_features_against_host()) makes sense only when using KVM.
So this makes the functions check_features_against_host() and
From: Eduardo Habkost ehabk...@redhat.com
This way all the filtering by GET_SUPPORTED_CPUID is being done at the
same place in the code.
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
---
target-i386/kvm.c |5 +++--
1 files changed, 3
From: Jan Kiszka jan.kis...@siemens.com
Releases of qemu-kvm will be interrupted at qemu 1.3.0.
Users should switch to plain qemu releases.
To avoid breaking scenarios which are setup with command line
options specific to qemu-kvm, port these switches from qemu-kvm
to qemu.git.
Port
From: Jan Kiszka jan.kis...@siemens.com
Releases of qemu-kvm will be interrupted at qemu 1.3.0.
Users should switch to plain qemu releases.
To avoid breaking scenarios which are setup with command line
options specific to qemu-kvm, port these switches from qemu-kvm
to qemu.git.
Port -no-kvm
From: Eduardo Habkost ehabk...@redhat.com
The for loop will become a separate function, so clean it up so it can
become independent from the bit hacking for R_EDX.
No behavior change[1], just code movement.
[1] Well, only if the kernel returned CPUID leafs 1 or 0x8001 as
unsupported,
From: Jan Kiszka jan.kis...@siemens.com
Releases of qemu-kvm will be interrupted at qemu 1.3.0.
Users should switch to plain qemu releases.
To avoid breaking scenarios which are setup with command line
options specific to qemu-kvm, port these switches from qemu-kvm
to qemu.git.
Port
From: Eduardo Habkost ehabk...@redhat.com
This moves the CPUID_EXT_TSC_DEADLINE_TIMER CPUID flag hacking from
kvm_arch_init_vcpu() to kvm_arch_get_supported_cpuid().
Full git grep for kvm_arch_get_supported_cpuid:
kvm.h:uint32_t kvm_arch_get_supported_cpuid(KVMState *env, uint32_t function,
From: Jan Kiszka jan.kis...@siemens.com
Releases of qemu-kvm will be interrupted at qemu 1.3.0.
Users should switch to plain qemu releases.
To avoid breaking scenarios which are setup with command line
options specific to qemu-kvm, port these switches from qemu-kvm
to qemu.git.
Port -tdf option.
From: Peter Maydell peter.mayd...@linaro.org
Recent kernels have moved to keeping the userspace headers
in uapi/ subdirectories. This breaks the detection of whether an
architecture has KVM support in the kernel because kvm.h has
moved in the kernel source tree. Update the check to support
both
From: Eduardo Habkost ehabk...@redhat.com
Full grep for kvm_arch_get_supported_cpuid:
kvm.h:uint32_t kvm_arch_get_supported_cpuid(KVMState *env, uint32_t function,
target-i386/cpu.c:x86_cpu_def-cpuid_7_0_ebx_features =
kvm_arch_get_supported_cpuid(kvm_state, 0x7, 0, R_EBX);
From: Eduardo Habkost ehabk...@redhat.com
The reg switch will be moved to a separate function, so store the entry
pointer in a variable.
No behavior change, just code movement.
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
---
Allow RAM size to be configurable for cirrus, to allow migration
compatibility from qemu-kvm.
Acked-by: Gerd Hoffmann kra...@redhat.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
---
hw/cirrus_vga.c | 21 -
1 files changed, 16 insertions(+), 5 deletions(-)
diff
From: Eduardo Habkost ehabk...@redhat.com
Instead of a function-specific has_kvm_features variable, simply use a
found variable that will be checked in case we have to use the legacy
get_para_features() interface.
No behavior change, just code cleanup.
Signed-off-by: Eduardo Habkost
From: Eduardo Habkost ehabk...@redhat.com
cpu.c contains the code that will check if all requested CPU features
are available, so the filtering of KVM features must be there, so we can
implement check and enforce properly.
The only point where kvm_arch_init_vcpu() is called on i386 is:
-
From: Eduardo Habkost ehabk...@redhat.com
Additional fixups will be added, and making them a single 'if/else if'
chain makes it clearer than two nested switch statements.
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
---
target-i386/kvm.c
From: Jan Kiszka jan.kis...@siemens.com
Releases of qemu-kvm will be interrupted at qemu 1.3.0.
Users should switch to plain qemu releases.
To avoid breaking scenarios which are setup with command line
options specific to qemu-kvm, port these switches from qemu-kvm
to qemu.git.
Port drive boot
From: Eduardo Habkost ehabk...@redhat.com
This is necessary so that x2apic is not improperly enabled when the
in-kernel irqchip is disabled.
This won't generate a warning with -cpu ...,check because the current
check/enforce code is broken (it checks the host CPU data directly,
instead of using
From: Eduardo Habkost ehabk...@redhat.com
The return value of that function is always 0, and is always ignored.
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
---
target-i386/cpu.c |4 +---
1 files changed, 1 insertions(+), 3
From: Eduardo Habkost ehabk...@redhat.com
No behavior change, just code movement.
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
---
target-i386/kvm.c | 19 ++-
1 files changed, 14 insertions(+), 5 deletions(-)
diff --git
From: Eduardo Habkost ehabk...@redhat.com
No behavior change, just code movement.
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
---
target-i386/kvm.c | 30 ++
1 files changed, 22 insertions(+), 8 deletions(-)
From: Don Slutz d...@cloudswitch.com
Currently -cpu host,-kvmclock,-kvm_nopiodelay,-kvm_mmu does not
turn off all bits in CPUID 0x4001 EAX.
The missing ones is KVM_FEATURE_STEAL_TIME.
This adds the name kvm_steal_time.
Signed-off-by: Don Slutz d...@cloudswitch.com
Signed-off-by: Marcelo
From: Eduardo Habkost ehabk...@redhat.com
Instead of masking the KVM feature bits very late (while building the
KVM_SET_CPUID2 data), mask it out on env-cpuid_kvm_features, at the
same point where the other feature words are masked out.
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
From: Eduardo Habkost ehabk...@redhat.com
Cosmetic, but it will also help to make futher patches easier to review.
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
---
target-i386/cpu.c | 28 +---
1 files changed, 13
From: Jan Kiszka jan.kis...@siemens.com
Releases of qemu-kvm will be interrupted at qemu 1.3.0.
Users should switch to plain qemu releases.
To avoid breaking scenarios which are setup with command line
options specific to qemu-kvm, port these switches from qemu-kvm
to qemu.git.
Port -no-kvm-pit
From: Eduardo Habkost ehabk...@redhat.com
Now that CPUID leaf 7 features can be enabled/disabled on the
command-line, we need to filter them properly using GET_SUPPORTED_CPUID,
at the same place where other features are filtered out.
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
From: Eduardo Habkost ehabk...@redhat.com
No behavior change: just code movement.
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
---
target-i386/kvm.c | 37 +++--
1 files changed, 23 insertions(+), 14
The following changes since commit aee0bf7d8d7564f8f2c40e4501695c492b7dd8d1:
tap-win32: stubs to fix win32 build (2012-10-30 19:18:53 +)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git uq/master
Don Slutz (1):
target-i386: Add missing kvm
From: Eduardo Habkost ehabk...@redhat.com
This makes QEMU recognize the following CPU flag names:
Flags| Corresponding KVM kernel commit
-+
FSGSBASE | 176f61da82435eae09cc96f70b530d1ba0746b8b
AVX2, BMI1, BMI2 |
On 31.10.2012, at 02:32, Marcelo Tosatti mtosa...@redhat.com wrote:
On Tue, Oct 30, 2012 at 11:02:13AM +0100, Alexander Graf wrote:
Hi Avi / Marcelo,
This is my current patch queue for ppc. Please pull.
Headline changes are:
* Fix 440 target
* Fix uapi conflict
Can you
On 10/31/2012 12:22 PM, Alexander Graf wrote:
On 31.10.2012, at 02:32, Marcelo Tosatti mtosa...@redhat.com wrote:
On Tue, Oct 30, 2012 at 11:02:13AM +0100, Alexander Graf wrote:
Hi Avi / Marcelo,
This is my current patch queue for ppc. Please pull.
Headline changes are:
* Fix
tun supports zero copy transmit since 0690899b4d4501b3505be069b9a687e68ccbe15b,
however you can only enable this mode if you know your workload does not
trigger heavy guest to host/host to guest traffic - otherwise you
get a (minor) performance regression.
This patchset addresses this problem by
Orphaning frags for zero copy skbs needs to allocate data in atomic
context so is has a chance to fail. If it does we currently discard
the skb which is safe, but we don't report anything to the caller,
so it can not recover by e.g. disabling zero copy.
Add an API to free skb reporting such
Better document macros for DMA tracking. Add an
explicit one for DMA in progress instead of
relying on user supplying len != 1.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
drivers/vhost/net.c | 3 ++-
drivers/vhost/vhost.c | 2 +-
drivers/vhost/vhost.h | 12 +---
3 files
This will be used to disable zerocopy when error rate
is high.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
drivers/vhost/vhost.c | 7 ---
drivers/vhost/vhost.h | 4
2 files changed, 8 insertions(+), 3 deletions(-)
diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c
Zerocopy handling code is vhost-net specific.
Move it from vhost.c/vhost.h out to net.c
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
drivers/vhost/net.c | 45
drivers/vhost/tcm_vhost.c | 1 +
drivers/vhost/vhost.c | 53
Even when vhost-net is in zero-copy transmit mode,
net core might still decide to copy the skb later
which is somewhat slower than a copy in user
context: data copy overhead is added to the cost of
page pin/unpin. The result is that enabling tx zero copy
option leads to higher CPU utilization for
On 10/31/2012 03:05 AM, Rick Jones wrote:
On 10/30/2012 03:03 AM, Jason Wang wrote:
Hi all:
This series is an update version of multiqueue virtio-net driver
based on
Krishna Kumar's work to let virtio-net use multiple rx/tx queues to
do the
packets reception and transmission. Please review
On 23.10.2012, at 08:20, Christian Borntraeger borntrae...@de.ibm.com wrote:
On 22/10/12 23:14, Alexander Graf wrote:
Hi Christian,
During our normal Factory kernel builds, s390x seems to choke:
It seems that to avoid deadlocks it is enough to poll vq before
we are going to use the last buffer. This is faster than
c70aa540c7a9f67add11ad3161096fb95233aa2e.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
drivers/vhost/net.c | 14 --
1 file changed, 12 insertions(+), 2
Even if skb is marked for zero copy, net core might still decide
to copy it later which is somewhat slower than a copy in user context:
besides copying the data we need to pin/unpin the pages.
Add a parameter reporting such cases through zero copy callback:
if this happens a lot, device can take
When tun transmits a zero copy skb, it orphans the frags
which might need to allocate extra memory, in atomic context.
If that fails, notify ubufs callback before freeing the skb
as a hint that device should disable zerocopy mode.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
On 31.10.2012, at 11:26, Avi Kivity a...@redhat.com wrote:
On 10/31/2012 12:22 PM, Alexander Graf wrote:
On 31.10.2012, at 02:32, Marcelo Tosatti mtosa...@redhat.com wrote:
On Tue, Oct 30, 2012 at 11:02:13AM +0100, Alexander Graf wrote:
Hi Avi / Marcelo,
This is my current patch
On Fri, Sep 21, 2012 at 1:17 PM, Vasilis Liaskovitis
vasilis.liaskovi...@profitbricks.com wrote:
This is v3 of the ACPI memory hotplug functionality. Only x86_64 target is
supported
for now.
Hi Vasilis,
Regarding the hot unplug issue we've been discussing, it's possible to
progress this patch
On 10/24/2012 10:06 AM, liu ping fan wrote:
On Tue, Oct 23, 2012 at 8:25 PM, Stefan Hajnoczi stefa...@gmail.com wrote:
On Fri, Sep 21, 2012 at 01:17:21PM +0200, Vasilis Liaskovitis wrote:
+static void dimm_populate(DimmDevice *s)
+{
+DeviceState *dev= (DeviceState*)s;
+MemoryRegion
On 10/31/2012 12:58 PM, Stefan Hajnoczi wrote:
On Fri, Sep 21, 2012 at 1:17 PM, Vasilis Liaskovitis
vasilis.liaskovi...@profitbricks.com wrote:
This is v3 of the ACPI memory hotplug functionality. Only x86_64 target is
supported
for now.
Hi Vasilis,
Regarding the hot unplug issue we've
On 10/31/2012 12:34 PM, Alexander Graf wrote:
On 31.10.2012, at 11:26, Avi Kivity a...@redhat.com wrote:
On 10/31/2012 12:22 PM, Alexander Graf wrote:
On 31.10.2012, at 02:32, Marcelo Tosatti mtosa...@redhat.com wrote:
On Tue, Oct 30, 2012 at 11:02:13AM +0100, Alexander Graf wrote:
On Wed, Oct 31, 2012 at 12:26:04PM +0200, Avi Kivity wrote:
On 10/31/2012 12:22 PM, Alexander Graf wrote:
On 31.10.2012, at 02:32, Marcelo Tosatti mtosa...@redhat.com wrote:
On Tue, Oct 30, 2012 at 11:02:13AM +0100, Alexander Graf wrote:
Hi Avi / Marcelo,
This is my current
On Wed, Oct 31, 2012 at 11:22:55AM +0100, Alexander Graf wrote:
On 31.10.2012, at 02:32, Marcelo Tosatti mtosa...@redhat.com wrote:
On Tue, Oct 30, 2012 at 11:02:13AM +0100, Alexander Graf wrote:
Hi Avi / Marcelo,
This is my current patch queue for ppc. Please pull.
Headline
Hi Rusty,
On Wed, 31 Oct 2012 13:58:15 +1030 Rusty Russell ru...@rustcorp.com.au wrote:
Stephen Rothwell s...@canb.auug.org.au writes:
On Tue, 02 Oct 2012 15:56:56 +0930 Rusty Russell ru...@rustcorp.com.au
wrote:
Please remove my quilt tree
On Wed, Oct 31, 2012 at 12:15 PM, Avi Kivity a...@redhat.com wrote:
On 10/24/2012 10:06 AM, liu ping fan wrote:
On Tue, Oct 23, 2012 at 8:25 PM, Stefan Hajnoczi stefa...@gmail.com wrote:
On Fri, Sep 21, 2012 at 01:17:21PM +0200, Vasilis Liaskovitis wrote:
+static void dimm_populate(DimmDevice
On 10/30/2012 02:37 PM, Andrew Jones wrote:
On Tue, Oct 30, 2012 at 01:01:54PM +0530, Raghavendra K T wrote:
On 10/30/2012 12:04 PM, Andrew Jones wrote:
On Tue, Oct 30, 2012 at 11:27:52AM +0530, Raghavendra K T wrote:
On 10/29/2012 11:24 PM, Peter Zijlstra wrote:
On Mon, 2012-10-29 at 19:37
On 10/31/2012 02:18 PM, Stefan Hajnoczi wrote:
IMO we should use the same mechanism as proposed for other devices:
address_space_map() should grab a reference on the dimm device, and
address_space_unmap() can release it. This way device destruction will
be deferred as soon as all devices
On Wed, Oct 31, 2012 at 1:34 PM, Avi Kivity a...@redhat.com wrote:
On 10/31/2012 02:18 PM, Stefan Hajnoczi wrote:
IMO we should use the same mechanism as proposed for other devices:
address_space_map() should grab a reference on the dimm device, and
address_space_unmap() can release it. This
On 10/29/2012 04:07 PM, Raghavendra K T wrote:
From: Raghavendra K T raghavendra...@linux.vnet.ibm.com
Also we do not update last boosted vcpu in failure cases.
#endif
+
void kvm_vcpu_on_spin(struct kvm_vcpu *me)
{
struct kvm *kvm = me-kvm;
@@ -1727,11 +1727,12 @@ void
On 10/31/2012 06:08 PM, Avi Kivity wrote:
On 10/29/2012 04:07 PM, Raghavendra K T wrote:
From: Raghavendra K T raghavendra...@linux.vnet.ibm.com
Also we do not update last boosted vcpu in failure cases.
#endif
+
void kvm_vcpu_on_spin(struct kvm_vcpu *me)
{
struct kvm *kvm =
On 31.10.2012, at 12:25, Marcelo Tosatti wrote:
On Wed, Oct 31, 2012 at 12:26:04PM +0200, Avi Kivity wrote:
On 10/31/2012 12:22 PM, Alexander Graf wrote:
On 31.10.2012, at 02:32, Marcelo Tosatti mtosa...@redhat.com wrote:
On Tue, Oct 30, 2012 at 11:02:13AM +0100, Alexander Graf wrote:
On 10/31/2012 06:11 PM, Raghavendra K T wrote:
On 10/31/2012 06:08 PM, Avi Kivity wrote:
On 10/29/2012 04:07 PM, Raghavendra K T wrote:
From: Raghavendra K T raghavendra...@linux.vnet.ibm.com
Also we do not update last boosted vcpu in failure cases.
#endif
+
void kvm_vcpu_on_spin(struct
On 10/31/2012 03:15 PM, Raghavendra K T wrote:
On 10/31/2012 06:11 PM, Raghavendra K T wrote:
On 10/31/2012 06:08 PM, Avi Kivity wrote:
On 10/29/2012 04:07 PM, Raghavendra K T wrote:
From: Raghavendra K T raghavendra...@linux.vnet.ibm.com
Also we do not update last boosted vcpu in failure
On Tue, Oct 30, 2012 at 10:48 PM, Stefan Hajnoczi stefa...@gmail.com wrote:
On Tue, Oct 30, 2012 at 10:09 PM, ronnie sahlberg
ronniesahlb...@gmail.com wrote:
About half a year there was an issue where recent kernels had added
support to start using new scsi opcodes, but the qemu functions
- Implements the arch specific APIs for KVM, some are stubs for MIPS
- kvm_mips_handle_exit(): Main 'C' distpatch routine for handling exceptions
while in Guest mode.
- Also implements in-kernel timer interrupt support for the guest.
Signed-off-by: Sanjay Lal sanj...@kymasys.com
---
Both Guest kernel and Guest Userspace execute in UM. The memory map is as
follows:
Guest User address space: 0x - 0x4000
Guest Kernel Unmapped: 0x4000 - 0x6000
Guest Kernel Mapped:0x6000 - 0x8000
- Guest Usermode virtual memory is limited to 1GB.
- Note that this file is statically linked with the rest of the host kernel
(KSEG0). This is because kernel modules are
loaded into mapped space on MIPS and we want to make sure that we don't get any
host kernel TLB faults while
manipulating TLBs.
- Virtual Guest TLBs are implemented as 64 entry
- Add the KVM option to MIPS build files.
- Add default config files for KVM host/guest kernels.
- Change the link address for the Malta KVM Guest kernel to UM (0x4010).
- Add KVM Kconfig file with KVM/MIPS specific options
Signed-off-by: Sanjay Lal sanj...@kymasys.com
---
arch/mips/Kbuild
- __kvm_mips_vcpu_run: main entry point to enter guest, we save kernel context,
load
up guest context from and ERET to guest context.
- mips32_exception: L1 exception handler(s), save k0/k1 and jump to main
handlers.
- mips32_GuestException: Generic exception handlers for exceptions/interrupts
Signed-off-by: Sanjay Lal sanj...@kymasys.com
---
arch/mips/include/asm/mmu_context.h | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/mips/include/asm/mmu_context.h
b/arch/mips/include/asm/mmu_context.h
index 9b02cfb..9c7024c 100644
--- a/arch/mips/include/asm/mmu_context.h
+++
Signed-off-by: Sanjay Lal sanj...@kymasys.com
---
arch/mips/kvm/kvm_mips_int.c | 251 +++
arch/mips/kvm/kvm_mips_int.h | 49 +
2 files changed, 300 insertions(+)
create mode 100644 arch/mips/kvm/kvm_mips_int.c
create mode 100644
Signed-off-by: Sanjay Lal sanj...@kymasys.com
---
arch/mips/mm/c-r4k.c | 6 --
arch/mips/mm/cache.c | 1 +
arch/mips/mm/tlb-r4k.c | 2 ++
3 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/arch/mips/mm/c-r4k.c b/arch/mips/mm/c-r4k.c
index 2b61462..1923063 100644
---
Signed-off-by: Sanjay Lal sanj...@kymasys.com
---
arch/mips/kernel/smp.c | 1 +
mm/bootmem.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/arch/mips/kernel/smp.c b/arch/mips/kernel/smp.c
index 9005bf9..60ea489 100644
--- a/arch/mips/kernel/smp.c
+++ b/arch/mips/kernel/smp.c
@@
Signed-off-by: Sanjay Lal sanj...@kymasys.com
---
virt/kvm/kvm_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
index e59bb63..1cc985a 100644
--- a/virt/kvm/kvm_main.c
+++ b/virt/kvm/kvm_main.c
@@ -1882,7 +1882,7 @@ static long
This bug is discussed in:
http://lkml.indiana.edu/hypermail/linux/kernel/1205.2/00719.html
Signed-off-by: Sanjay Lal sanj...@kymasys.com
---
arch/mips/kernel/entry.S | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/arch/mips/kernel/entry.S b/arch/mips/kernel/entry.S
Signed-off-by: Sanjay Lal sanj...@kymasys.com
---
arch/mips/kernel/asm-offsets.c | 67 ++
1 file changed, 67 insertions(+)
diff --git a/arch/mips/kernel/asm-offsets.c b/arch/mips/kernel/asm-offsets.c
index 833eeab..d65a2fd 100644
---
Currently, the following instructions are translated:
- CACHE (indexed)
- CACHE (va based): translated to a synci, overkill on D-CACHE operations, but
still much faster than a trap.
- mfc0/mtc0: the virtual COP0 registers for the guest are implemented as 2-D
array
[COP#][SEL] and this is
Signed-off-by: Sanjay Lal sanj...@kymasys.com
---
arch/mips/kvm/kvm_mips_stats.c | 93 ++
arch/mips/kvm/kvm_mips_stats.h | 47 +
2 files changed, 140 insertions(+)
create mode 100644 arch/mips/kvm/kvm_mips_stats.c
create mode 100644
Signed-off-by: Sanjay Lal sanj...@kymasys.com
---
arch/mips/kvm/kvm_cb.c| 16 ++
arch/mips/kvm/kvm_trap_emul.c | 446 ++
2 files changed, 462 insertions(+)
create mode 100644 arch/mips/kvm/kvm_cb.c
create mode 100644 arch/mips/kvm/kvm_trap_emul.c
The following patchset implements KVM support for MIPS32R2 processors,
using Trap Emulate, with basic runtime binary translation to improve
performance. The goal has been to keep the Guest kernel changes to a
minimum.
The patch is against Linux 3.7-rc2.
There is a companion patchset for QEMU
- The Guest kernel is run in UM and privileged instructions cause a trap.
- If the instruction causing the trap is in a branch delay slot, the branch
needs to be emulated to figure
out the PC @ which the guest will resume execution.
Signed-off-by: Sanjay Lal sanj...@kymasys.com
---
Signed-off-by: Sanjay Lal sanj...@kymasys.com
---
arch/mips/include/asm/stackframe.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/mips/include/asm/stackframe.h
b/arch/mips/include/asm/stackframe.h
index cb41af5..59c9245 100644
---
Signed-off-by: Sanjay Lal sanj...@kymasys.com
---
arch/mips/include/asm/kvm.h | 58
arch/mips/include/asm/kvm_host.h | 672 +++
2 files changed, 730 insertions(+)
create mode 100644 arch/mips/include/asm/kvm.h
create mode 100644
Signed-off-by: Sanjay Lal sanj...@kymasys.com
---
arch/mips/kvm/00README.txt | 31 +++
arch/mips/kvm/Makefile | 13 +
2 files changed, 44 insertions(+)
create mode 100644 arch/mips/kvm/00README.txt
create mode 100644 arch/mips/kvm/Makefile
diff --git
Hi,
here's the latest incarnation of my host patches to support channel
I/O on s390.
Most patches have only seen minor fixes, but patch 5 is completely
different since the kvm - user space interface has been reworked.
We now handle only interrupt-related operations in kvm. This
includes two
Add support for handling I/O interrupts (standard, subchannel-related
ones and rudimentary adapter interrupts).
The subchannel-identifying parameters are encoded into the interrupt
type.
I/O interrupts are floating, so they can't be injected on a specific
vcpu.
Signed-off-by: Cornelia Huck
Explicitely catch all channel I/O related instructions intercepts
in the kernel and set condition code 3 for them.
This paws the way for properly handling these instructions later
on.
Note: This is not architecture compliant (the previous code wasn't
either) since setting cc 3 is not the correct
Add a new capability, KVM_CAP_S390_CSS_SUPPORT, which will pass
intercepts for channel I/O instructions to userspace. Only I/O
instructions interacting with I/O interrupts need to be handled
in-kernel:
- TEST PENDING INTERRUPTION (tpi) dequeues and stores pending
interrupts entirely in-kernel.
Signed-off-by: Cornelia Huck cornelia.h...@de.ibm.com
---
Documentation/virtual/kvm/api.txt | 2 +-
arch/s390/kvm/kvm-s390.c | 26 ++
2 files changed, 27 insertions(+), 1 deletion(-)
diff --git a/Documentation/virtual/kvm/api.txt
Signed-off-by: Cornelia Huck cornelia.h...@de.ibm.com
---
linux-headers/asm-generic/kvm_para.h | 5 +++
linux-headers/asm-powerpc/kvm.h | 59 ++
linux-headers/asm-powerpc/kvm_para.h | 7 +++--
linux-headers/asm-x86/kvm.h | 17 ++
Add support for injecting machine checks (only repressible
conditions for now).
This is a bit more involved than I/O interrupts, for these reasons:
- Machine checks come in both floating and cpu varieties.
- We don't have a bit for machine checks enabling, but have to use
a roundabout approach
Add a new virtio transport that uses channel commands to perform
virtio operations.
Add a new machine type s390-ccw that uses this virtio-ccw transport
and make it the default machine for s390.
Signed-off-by: Cornelia Huck cornelia.h...@de.ibm.com
---
hw/s390-virtio.c | 282
Hi,
here's the latest version of my patchset introducing virtio-ccw.
This has been reworked with the changed kernel interface: qemu
will now handle all channel I/O requests (except the I/O interrupt
related ones that are handled in-kernel in the kvm case). This
avoids duplicating code in qemu
On 10/31/2012 07:11 PM, Avi Kivity wrote:
On 10/31/2012 03:15 PM, Raghavendra K T wrote:
On 10/31/2012 06:11 PM, Raghavendra K T wrote:
On 10/31/2012 06:08 PM, Avi Kivity wrote:
On 10/29/2012 04:07 PM, Raghavendra K T wrote:
From: Raghavendra K T raghavendra...@linux.vnet.ibm.com
Also we do
1) Start migration with stressed VM.
2) Wait cancel_delay and then cancel migration.
3) Check if machine is alive on source host.
4) Stop stress of VM.
5) Migrate machine again.
6) Check if machine is alive on destination host.
Signed-off-by: Jiří Župka jzu...@redhat.com
---
1 - 100 of 136 matches
Mail list logo
