On 04/18/2010 02:21 AM, Espen Berg wrote:
Den 17.04.2010 22:17, skrev Michael Tokarev:
We have three KVM hosts that supports live-migration between them, but
one of our problems is time drifting. The three frontends has different
CPU frequency and the KVM guests adopt the frequency from the host
Den 18.04.2010 11:22, skrev Dor Laor:
What do you mean by "adopts" ? Note that the cpu frequency
means nothing for all the modern operating systems, at least
since the days of common usage of MS-DOS which relied on CPU
frequency for its time functions. All interesting things are
now done using ti
On Sun, Apr 18, 2010 at 12:22:54PM +0300, Dor Laor wrote:
> On 04/18/2010 02:21 AM, Espen Berg wrote:
> >Den 17.04.2010 22:17, skrev Michael Tokarev:
> We have three KVM hosts that supports live-migration between them, but
> one of our problems is time drifting. The three frontends has diff
On Sat, 2010-04-17 at 22:55 -0600, David S. Ahern wrote:
>
> On 04/17/2010 10:09 PM, Amos Kong wrote:
> > %post --interpreter /usr/bin/python
> > import socket, os
> > os.system('dhclient')
> > os.system('chkconfig sshd on')
> > os.system('iptables -F')
> > os.system('echo 0 > /selinux/enforce')
>
To get additional details, samples and counts for our USA contact data please
email me at this address allyson.hairs...@alwaysgood. co.cc
we have lots of different lists in many fields and this week is the time to buy
with lowered list prices.
to subtract your address from our databa#se lo
When we get a performance counter interrupt we need to route it on to the
Linux handler after we got out of the guest context. We also need to tell
our handling code that this particular interrupt doesn't need treatment.
So let's add those two bits in, making perf work while having a KVM guest
run
In the process of merging Book3S_32 and 64 I somehow ended up having the
alignment interrupt handler take last_inst, but the fetching code not
fetching it. So we ended up with stale last_inst values.
Let's just enable last_inst fetching for alignment interrupts too.
Signed-off-by: Alexander Graf
Book3S_64 didn't set VSID_PR when we're in PR=1. This lead to pretty bad
behavior when searching for the shadow segment, as part of the code relied
on VSID_PR being set.
This patch fixes booting Book3S_64 guests.
Signed-off-by: Alexander Graf
---
arch/powerpc/kvm/book3s_64_mmu.c |3 +++
1 f
While working with the PPC32 host target we finally have I stumbled over
several things. Thanks to the now possible performance measurements I also
tracked down split mode as one of the major slowdowns to KVM.
What's left now that slows us down is the normal flushing code that needs
to move to a t
For KVM we need to find the location of the HTAB. We can either rely
on internal data structures of the kernel or ask the hardware.
Ben issued complaints about the internal data structure method, so
let's switch it to our own inquiry of the HTAB. Now we're fully
independent :-).
CC: Benjamin Herr
We have a condition in the ppc64 host mmu code that should never occur.
Unfortunately, it just did happen to me and I was rather puzzled on why,
because BUG_ON doesn't tell me anything useful.
So let's add some more debug output in case this goes wrong. Also change
BUG to WARN, since I don't want
There are some pieces in the code that I overlooked that still use
u64s instead of longs. This slows down 32 bit hosts unnecessarily, so
let's just move them to ulong.
Signed-off-by: Alexander Graf
---
v1 -> v2:
- don't touch vsid - that stays u64!
---
arch/powerpc/include/asm/kvm_book3s.h
We have some debug output in Book3S_64. Some of that was invalid though,
partially not even compiling because it accessed incorrect variables.
So let's fix that up, making debugging more fun again.
Signed-off-by: Alexander Graf
---
arch/powerpc/kvm/book3s_64_mmu_host.c | 23 ++
When in split mode, instruction relocation and data relocation are not equal.
So far we implemented this mode by reserving a special pseudo-VSID for the
two cases and flushing all PTEs when going into split mode, which is slow.
Unfortunately 32bit Linux and Mac OS X use split mode extensively. So
Alexander Graf wrote:
> We have a condition in the ppc64 host mmu code that should never occur.
> Unfortunately, it just did happen to me and I was rather puzzled on why,
> because BUG_ON doesn't tell me anything useful.
>
> So let's add some more debug output in case this goes wrong. Also change
On 19.04.2010, at 03:01, Jim Paris wrote:
> Alexander Graf wrote:
>> We have a condition in the ppc64 host mmu code that should never occur.
>> Unfortunately, it just did happen to me and I was rather puzzled on why,
>> because BUG_ON doesn't tell me anything useful.
>>
>> So let's add some more
On 19.04.2010, at 03:07, Alexander Graf wrote:
>
> On 19.04.2010, at 03:01, Jim Paris wrote:
>
>> Alexander Graf wrote:
>>> We have a condition in the ppc64 host mmu code that should never occur.
>>> Unfortunately, it just did happen to me and I was rather puzzled on why,
>>> because BUG_ON doe
Srivatsa Vaddagiri wrote:
> On Thu, Apr 15, 2010 at 03:33:18PM +0200, Peter Zijlstra wrote:
>> On Thu, 2010-04-15 at 11:18 +0300, Avi Kivity wrote:
>>>
>>> Certainly that has even greater potential for Linux guests. Note
>>> that we spin on mutexes now, so we need to prevent preemption while
>>>
On 04/18/2010 12:26 PM, Lucas Meneghel Rodrigues wrote:
> On Sat, 2010-04-17 at 22:55 -0600, David S. Ahern wrote:
>>
>> On 04/17/2010 10:09 PM, Amos Kong wrote:
>>> %post --interpreter /usr/bin/python
>>> import socket, os
>>> os.system('dhclient')
>>> os.system('chkconfig sshd on')
>>> os.syste
Here is the new patch of V5 against tip/master of April 17th
if anyone wants to try it.
ChangeLog V5:
1) Split kernel patch to 2 parts. The one introduces
perf_guest_info_callbacks() and related register/unregister
functions. The other is the kvm implementation of the callb
Below patch introduces perf_guest_info_callbacks and related register/unregister
functions. Add more PERF_RECORD_MISC_XXX bits meaning guest kernel and guest
user
space.
Signed-off-by: Zhang Yanmin
---
diff -Nraup --exclude-from=exclude.diff
linux-2.6_tip0417/arch/x86/include/asm/perf_event.h
Below patch implements the perf_guest_info_callbacks on kvm.
Signed-off-by: Zhang Yanmin
---
diff -Nraup linux-2.6_tip0417/arch/x86/kvm/vmx.c
linux-2.6_tip0417_perfkvm/arch/x86/kvm/vmx.c
--- linux-2.6_tip0417/arch/x86/kvm/vmx.c2010-04-19 09:51:47.908673911
+0800
+++ linux-2.6_tip0417_
From: sshang
The test use kvm test harness kvmctl load binary test case file
to test various functions of the kvm kernel module.
This test is for older style unit testing, after some
consideration we decided to keep the 2 modules separated.
Signed-off-by: Shuxi Shang
---
client/tests/kvm/test
* Zhang, Yanmin wrote:
> Here is the new patch of V5 against tip/master of April 17th if anyone wants
> to try it.
Ok, this looks pretty good from the perf angle - so once Avi likes patches #1
and #2 and creates a pullable branch we can apply #3 as well to tip:perf/core
and put it on the pot
24 matches
Mail list logo
