https://bugzilla.kernel.org/show_bug.cgi?id=73721
Bug ID: 73721
Summary: KVM hv-time
Product: Virtualization
Version: unspecified
Kernel Version: 3.14.0
Hardware: x86-64
OS: Linux
Tree: Mainline
St
We need to reset the usage state of the pages on kexec/kdump,
which use subcode 0 and 1. We will only do the cmma reset in
the kernel, everything else is done in userspace as before.
Signed-off-by: Christian Borntraeger
---
arch/s390/kvm/diag.c | 4
1 file changed, 4 insertions(+)
diff --g
From: "Jason J. Herne"
Replace the kvm_s390_sync_dirty_log() stub with code to construct the KVM
dirty_bitmap from S390 memory change bits. Also add code to properly clear
the dirty_bitmap size when clearing the bitmap.
Signed-off-by: Jason J. Herne
CC: Dominik Dingel
[Dominik Dingel: use gma
kernel/git/kvms390/linux.git
tags/kvm-s390-20140409
for you to fetch changes up to 384ee3e2a18893f9de84ce2f00cf786ad81fe08e:
KVM: s390: Add proper dirty bitmap support to S390 kvm. (2014-04-09 11:12:15
+0200)
here are two changes
From: Dominik Dingel
The first invocation of storage key operations on a given cpu will be
intercepted.
On these intercepts we will enable storage keys for the guest and remove the
previously added intercepts.
Signed-off-by: Dominik Dingel
Acked-by: Martin Schwidefsky
Signed-off-by: Christia
From: Martin Schwidefsky
Switch the user dirty bit detection used for migration from the hardware
provided host change-bit in the storage key/pgste to a fault based
detection method. Turns out that this is actually faster than the
old storage key operations.
As a bonus, this reduces the dependenc
From: Dominik Dingel
Introduce a new function s390_enable_skey(), which enables storage key
handling via setting the use_skey flag in the mmu context.
This function is only useful within the context of kvm.
Note that enabling storage keys will cause a one-time hickup when
walking the page table
From: Dominik Dingel
For live migration kvm needs to test and clear the dirty bit of guest pages.
Lets provide ptep_test_and_clear_user_dirty in architecture specific
memory management code, since we need proper locking.
Signed-off-by: Dominik Dingel
Acked-by: Martin Schwidefsky
Signed-off-by
From: Dominik Dingel
For lazy storage key handling, we need a mechanism to track if the
process ever issued a storage key operation.
This patch adds the basic infrastructure for making the storage
key handling optional, but still leaves it enabled for now by default.
Signed-off-by: Dominik Ding
From: Dominik Dingel
page_table_reset_pgste() already does a complete page table walk to
reset the pgste. Enhance it to initialize the storage keys to
PAGE_DEFAULT_KEY if requested by the caller. This will be used
for lazy storage key handling.
Lets adopt the current code (diag 308) to not clear
On 04/08/2014 10:47 PM, Alex Williamson wrote:
> On Tue, 2014-04-08 at 22:24 +0300, rndbit wrote:
>> On 04/08/2014 08:00 PM, Alex Williamson wrote:
>>> On Tue, 2014-04-08 at 17:01 +0300, rndbit wrote:
Hello,
I am one of those early tinkerers with VGA passthrough. This is very
exciti
On Thu, 3 Apr 2014 16:04:44 +
Andre Goree wrote:
> Hello list. I wanted to ask if anyone has been able to make filesystem
> mounting work under a FreeBSD guest? For example, I've added the following
> to the guest's xml config using 'virsh edit':
>
>
>
>
>
>
>
> However, I don't k
On 04/09/2014 12:45 AM, Waiman Long wrote:
Yes, I am able to reproduce the hang problem with ebizzy. BTW, could you
try to apply the attached patch file on top of the v8 patch series to
see if it can fix the hang problem?
Ran the benchmarks with the fix and I am not seeing hang so far.
ebizzy i
From: Alexander Yarygin
Trace events potentially can have a '-' in their trace system name,
e.g. kvm on s390 defines kvm-s390:* tracepoints.
tools/perf could not parse them, because there was no rule for this:
$ sudo ./perf top -e "kvm-s390:*"
invalid or unsupported event: 'kvm-s390:*'
This patc
Ingo, Arnaldo,
two fixes indentified during kvm on s390 development are available
since commit 538592ff0b008237ae88f5ce5fb1247127dc3ce5:
Merge tag 'perf-core-for-mingo' of
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/core
(2014-03-19 08:05:47 +0100)
in the git reposit
From: Alexander Yarygin
Every event in the perf-kvm has a 'stats' structure, which contains
max/min/average/etc times of handling this event.
The problem is that the 'perf-kvm stat report' command always shows
that 'min time' is 0us for every event. Example:
# perf kvm stat report
Analyze event
On Mon, Mar 10, 2014 at 10:01:49PM +0800, Xiao Guangrong wrote:
> Now we can flush all the TLBs out of the mmu lock without TLB corruption when
> write-proect the sptes, it is because:
> - we have marked large sptes readonly instead of dropping them that means we
> just change the spte from writa
On 4/9/14, 7:21 AM, Christian Borntraeger wrote:
From: Alexander Yarygin
Every event in the perf-kvm has a 'stats' structure, which contains
max/min/average/etc times of handling this event.
The problem is that the 'perf-kvm stat report' command always shows
that 'min time' is 0us for every eve
gt;
> are available in the git repository at:
>
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git
> tags/kvm-s390-20140409
>
> for you to fetch changes up to 384ee3e2a18893f9de84ce2f00cf786ad81fe08e:
>
> KVM: s390: Add proper dirty bitmap support to
t:
git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git
tags/kvm-s390-20140409
for you to fetch changes up to e31a06aaa22f66ba868148ae4f8e270d2ebb9c2b:
KVM: s390: Add proper dirty bitmap support to S390 kvm. (2014-04-09 21:22
On Mon, Apr 7, 2014 at 4:36 PM, Alexander Graf wrote:
>
> On 07.04.14 09:42, Aneesh Kumar K.V wrote:
>>
>> Alexander Graf writes:
>>
>>> On 03.04.14 04:36, Liu ping fan wrote:
Hi Alex, could you help to pick up this patch? since v3.14 kernel can
enable numa fault for powerpc.
>>>
21 matches
Mail list logo
