On 02/10/2012 02:28 PM, Takuya Yoshikawa wrote:
> Other threads may process the same page in that small window and skip
> TLB flush and then return before these functions do flush.
>
It is possible that flush tlb in mmu lock only when writeable
spte is invalided? Sometimes, kvm_flush_remote_tlb
On 02/10/2012 03:21 PM, Takuya Yoshikawa wrote:
> (2012/02/10 15:55), Xiao Guangrong wrote:
>> On 02/10/2012 02:29 PM, Takuya Yoshikawa wrote:
>>
>>> diff --git a/arch/x86/kvm/paging_tmpl.h b/arch/x86/kvm/paging_tmpl.h
>>> index 1561028..69d06f5 100644
>>> --- a/arch/x86/kvm/paging_tmpl.h
>>> +++
(2012/02/10 15:55), Xiao Guangrong wrote:
On 02/10/2012 02:29 PM, Takuya Yoshikawa wrote:
diff --git a/arch/x86/kvm/paging_tmpl.h b/arch/x86/kvm/paging_tmpl.h
index 1561028..69d06f5 100644
--- a/arch/x86/kvm/paging_tmpl.h
+++ b/arch/x86/kvm/paging_tmpl.h
@@ -682,6 +682,7 @@ static void FNAME(in
On 02/10/2012 02:29 PM, Takuya Yoshikawa wrote:
> diff --git a/arch/x86/kvm/paging_tmpl.h b/arch/x86/kvm/paging_tmpl.h
> index 1561028..69d06f5 100644
> --- a/arch/x86/kvm/paging_tmpl.h
> +++ b/arch/x86/kvm/paging_tmpl.h
> @@ -682,6 +682,7 @@ static void FNAME(invlpg)(struct kvm_vcpu *vcpu, gva_t
That method of representing an IPv6 address with a port is
discouraged because of its ambiguity. Referencing to RFC5952,
the recommended format is:
[2312::8274]:5200
test status: Successed
listen side: qemu-kvm -incoming tcp:[2312::8274]:5200
client side: qemu-kvm ...
(qemu
IPv6 address contains colons, parse will be wrong.
[2312::8274]:5200
Signed-off-by: Amos Kong
---
net.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/net.c b/net.c
index f63014c..9e1ef9e 100644
--- a/net.c
+++ b/net.c
@@ -84,7 +84,7 @@ static int get_str_sep(char
Remove use of parse_host_port.
More SO_SOCKADDR changes.
Signed-off-by: Juan Quintela
Signed-off-by: Amos Kong
---
net/socket.c | 60 +++---
1 files changed, 11 insertions(+), 49 deletions(-)
diff --git a/net/socket.c b/net/socket.c
index d
This allows us to use ipv4/ipv6 for migration addresses.
Once there, it also uses /etc/services names (it came free).
Signed-off-by: Juan Quintela
Signed-off-by: Amos Kong
---
migration-tcp.c | 60 ---
net.c | 108
Those four patches make migration of IPv6 address work.
Use getaddrinfo() to socket addresses infomation.
---
Amos Kong (4):
Use getaddrinfo for migration
net/socket: allow ipv6 for net_socket_listen_init and socket_connect_init
net: split hostname and service by last colon
This function's TLB flush was moved sometimes in the past:
1.
commit 4539b35881ae9664b0e2953438dd83f5ee02c0b4
KVM: Fix missing smp tlb flush in invlpg
inserted it in the critical section.
2.
commit 505aef8f30a95f7e4abf2c07e54ded1521587ba0
KVM: MMU: cleanup FNAME(invlpg)
moved it inside
Other threads may process the same page in that small window and skip
TLB flush and then return before these functions do flush.
Signed-off-by: Takuya Yoshikawa
---
virt/kvm/kvm_main.c | 19 ++-
1 files changed, 10 insertions(+), 9 deletions(-)
diff --git a/virt/kvm/kvm_main.c
Signed-off-by: Cong Wang
---
drivers/vhost/vhost.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c
index c14c42b..bdb2d64 100644
--- a/drivers/vhost/vhost.c
+++ b/drivers/vhost/vhost.c
@@ -937,9 +937,9 @@ static int set_bit
Acked-by: Avi Kivity
Acked-by: Herbert Xu
Signed-off-by: Cong Wang
---
arch/x86/crypto/aesni-intel_glue.c | 24
arch/x86/kernel/crash_dump_32.c|6 +++---
arch/x86/kvm/lapic.c |8
arch/x86/kvm/paging_tmpl.h |4 ++--
arch/x
Signed-off-by: Cong Wang
---
arch/powerpc/kvm/book3s_pr.c |4 ++--
arch/powerpc/mm/dma-noncoherent.c |5 ++---
arch/powerpc/mm/hugetlbpage.c |4 ++--
arch/powerpc/mm/mem.c |4 ++--
4 files changed, 8 insertions(+), 9 deletions(-)
diff --git a/arch/powerpc/kvm
On Fri, Feb 10, 2012 at 12:17 PM, Sasha Levin wrote:
> On Fri, 2012-02-10 at 11:03 +0800, Yang Bai wrote:
>> On Fri, Feb 10, 2012 at 12:53 PM, Sasha Levin
>> wrote:
>> > On Fri, 2012-02-10 at 10:34 +0800, Yang Bai wrote:
>> >> On Thu, Feb 9, 2012 at 9:07 PM, Cyrill Gorcunov
>> >> wrote:
>> >>
On Fri, 2012-02-10 at 11:03 +0800, Yang Bai wrote:
> On Fri, Feb 10, 2012 at 12:53 PM, Sasha Levin wrote:
> > On Fri, 2012-02-10 at 10:34 +0800, Yang Bai wrote:
> >> On Thu, Feb 9, 2012 at 9:07 PM, Cyrill Gorcunov
> >> wrote:
> >> > On Thu, Feb 09, 2012 at 03:01:26PM +0200, Pekka Enberg wrote:
>
On 2/9/2012 6:14 PM, John Fastabend wrote:
> On 2/9/2012 1:11 PM, jamal wrote:
>> On Thu, 2012-02-09 at 09:52 -0800, John Fastabend wrote:
>>
> By netlink_notifier do you mean adding a notifier_block and using
> atomic_notifier_call_chain()
> probably in rtnl_notify()? Then drivers cou
Anthony Liguori wrote:
> >The new API will do away with the IOAPIC/PIC/PIT emulation and defer
> >them to userspace.
>
> I'm a big fan of this.
I agree with getting rid of unnecessary emulations.
(Why were those things emulated in the first place?)
But it would be good to retain some way to "plu
On Fri, Feb 10, 2012 at 12:53 PM, Sasha Levin wrote:
> On Fri, 2012-02-10 at 10:34 +0800, Yang Bai wrote:
>> On Thu, Feb 9, 2012 at 9:07 PM, Cyrill Gorcunov wrote:
>> > On Thu, Feb 09, 2012 at 03:01:26PM +0200, Pekka Enberg wrote:
>> >> On Thu, Feb 9, 2012 at 7:40 AM, Yang Bai wrote:
>> >> > Sin
On Fri, 2012-02-10 at 10:34 +0800, Yang Bai wrote:
> On Thu, Feb 9, 2012 at 9:07 PM, Cyrill Gorcunov wrote:
> > On Thu, Feb 09, 2012 at 03:01:26PM +0200, Pekka Enberg wrote:
> >> On Thu, Feb 9, 2012 at 7:40 AM, Yang Bai wrote:
> >> > Since the different issues have been handled in the
> >> > inte
On Thu, Feb 9, 2012 at 9:07 PM, Cyrill Gorcunov wrote:
> On Thu, Feb 09, 2012 at 03:01:26PM +0200, Pekka Enberg wrote:
>> On Thu, Feb 9, 2012 at 7:40 AM, Yang Bai wrote:
>> > Since the different issues have been handled in the
>> > internal of kvm__init, it can only return NULL if error
>> > happ
On 2/9/2012 1:11 PM, jamal wrote:
> On Thu, 2012-02-09 at 09:52 -0800, John Fastabend wrote:
>
By netlink_notifier do you mean adding a notifier_block and using
atomic_notifier_call_chain()
probably in rtnl_notify()? Then drivers could register with the notifier
chain with
>>
>> @@ -601,6 +591,7 @@ int kvm_vcpu_ioctl_interrupt(struct kvm_vcpu *vcpu,
>> struct kvm_interrupt *irq)
>> }
>>
>> kvmppc_core_queue_external(vcpu, irq);
>> +
>
> Apart from this little glitch the patch looks fine to me. But I'd like to
> have Scott and Paul ack it too.
>
>
damn, can
On 10.02.2012, at 02:40, Christoffer Dall wrote:
> The kvm_vcpu_kick function performs roughly the same funcitonality on
> most all architectures, so we shouldn't have separate copies.
>
> PowerPC keeps a pointer to interchanging waitqueues on the vcpu_arch
> structure and to accomodate this spe
The kvm_vcpu_kick function performs roughly the same funcitonality on
most all architectures, so we shouldn't have separate copies.
PowerPC keeps a pointer to interchanging waitqueues on the vcpu_arch
structure and to accomodate this special need a
__KVM_HAVE_ARCH_VCPU_GET_WQ define and accompanyi
In order to avoid compilation failure when KVM is not compiled in,
guard the mmu_notifier specific sections with both CONFIG_MMU_NOTIFIER
and KVM_ARCH_WANT_MMU_NOTIFIER, like it is being done in the rest of
the KVM code.
Signed-off-by: Marc Zyngier
---
include/linux/kvm_host.h |4 ++--
1 fil
Add the necessary infrastructure to handle MMU notifiers on KVM/ARM.
As we don't have shadow page tables, the implementation is actually very
simple. The only supported operation is kvm_unmap_hva(), where we remove
the HVA from the 2nd stage translation. All other hooks are NOPs.
Signed-off-by: Ma
On 10.02.2012, at 02:13, Marc Zyngier wrote:
> Add the necessary infrastructure to handle MMU notifiers on KVM/ARM.
> As we don't have shadow page tables, the implementation is actually very
> simple. The only supported operation is kvm_unmap_hva(), where we remove
> the HVA from the 2nd stage tr
On 2/9/2012 4:39 PM, Sridhar Samudrala wrote:
> On Thu, 2012-02-09 at 12:30 -0800, John Fastabend wrote:
>> On 2/9/2012 10:14 AM, Sridhar Samudrala wrote:
>>> On Wed, 2012-02-08 at 19:22 -0800, John Fastabend wrote:
Propagate software FDB table into hardware uc, mc lists when
the NETIF_F_
On Thu, 2012-02-09 at 12:30 -0800, John Fastabend wrote:
> On 2/9/2012 10:14 AM, Sridhar Samudrala wrote:
> > On Wed, 2012-02-08 at 19:22 -0800, John Fastabend wrote:
> >> Propagate software FDB table into hardware uc, mc lists when
> >> the NETIF_F_HW_FDB is set.
> >>
> >> This resolves the case b
On Thu, Feb 09, 2012 at 12:28:05PM +0100, Joerg Roedel wrote:
> On Thu, Feb 09, 2012 at 08:39:28AM +1100, Benjamin Herrenschmidt wrote:
> > On Wed, 2012-02-08 at 16:27 +0100, Joerg Roedel wrote:
> > > Again, device grouping is done by the IOMMU drivers, so this all
> > > belongs
> > > into the gene
On 10.02.2012, at 00:43, Scott Wood wrote:
> On 02/09/2012 05:23 PM, Alexander Graf wrote:
>> How about we return 1 for kvm_arch_vcpu_in_guest_mode() on !x86
>> always, just like it's done today basically? Then we can worry about
>> needless IPIs later and don't regress from the respective curren
On 02/09/2012 05:23 PM, Alexander Graf wrote:
> How about we return 1 for kvm_arch_vcpu_in_guest_mode() on !x86
> always, just like it's done today basically? Then we can worry about
> needless IPIs later and don't regress from the respective current
> kick implementations.
And perhaps call the fu
On 10.02.2012, at 00:18, Christoffer Dall wrote:
> On Thu, Feb 9, 2012 at 3:02 PM, Alexander Graf wrote:
>>
>> On 09.02.2012, at 23:33, Christoffer Dall wrote:
>>
>>> From: Christoffer Dall
>>>
>>> The kvm_vcpu_kick function performs roughly the same funcitonality on
>>> most all architectur
On 10.02.2012, at 00:17, Andreas Färber wrote:
> Am 09.02.2012 23:37, schrieb Anthony Liguori:
>> On 02/09/2012 04:23 PM, Peter Maydell wrote:
>>> Ping re the VMState and variable sized arrays issue. I don't
>>> see any consensus in this discussion for a different approach,
>>> so should we just
On Thu, Feb 9, 2012 at 3:02 PM, Alexander Graf wrote:
>
> On 09.02.2012, at 23:33, Christoffer Dall wrote:
>
>> From: Christoffer Dall
>>
>> The kvm_vcpu_kick function performs roughly the same funcitonality on
>> most all architectures, so we shouldn't have separate copies.
>>
>> PowerPC keeps a
Am 09.02.2012 23:37, schrieb Anthony Liguori:
> On 02/09/2012 04:23 PM, Peter Maydell wrote:
>> Ping re the VMState and variable sized arrays issue. I don't
>> see any consensus in this discussion for a different approach,
>> so should we just commit Mitsyanko's patchset?
>
> I don't know if I men
On 10.02.2012, at 00:11, Christoffer Dall wrote:
> sorry about missing reply-all before
>
> On Thu, Feb 9, 2012 at 3:07 PM, Alexander Graf wrote:
>> On 10.02.2012, at 00:04, Christoffer Dall wrote:
>>
>>> becuase KVM_CAP_IRQ_ROUTING is only defined when __KVM_HAVE_IOAPIC.
>>> kvm/arm does not
On 09.02.2012, at 23:33, Christoffer Dall wrote:
> From: Christoffer Dall
>
> The kvm_vcpu_kick function performs roughly the same funcitonality on
> most all architectures, so we shouldn't have separate copies.
>
> PowerPC keeps a pointer to interchanging waitqueues on the vcpu_arch
> structu
On 9 February 2012 22:37, Anthony Liguori wrote:
> I don't know if I mentioned this, but do we really need variable sizes?
>
> Can we just use a fixed size (pre-allocated) array and then use a
> VMSTATE_SUB_ARRAY?
>
> If it's truly variable size with no upper bound, then that's actually a
> securi
On 02/09/2012 04:23 PM, Peter Maydell wrote:
Ping re the VMState and variable sized arrays issue. I don't
see any consensus in this discussion for a different approach,
so should we just commit Mitsyanko's patchset?
I don't know if I mentioned this, but do we really need variable sizes?
Can we
From: Christoffer Dall
The kvm_vcpu_kick function performs roughly the same funcitonality on
most all architectures, so we shouldn't have separate copies.
PowerPC keeps a pointer to interchanging waitqueues on the vcpu_arch
structure and to accomodate this special need a
__KVM_HAVE_ARCH_VCPU_GET
Ping re the VMState and variable sized arrays issue. I don't
see any consensus in this discussion for a different approach,
so should we just commit Mitsyanko's patchset?
- PMM
On 31 January 2012 13:15, Andreas Färber wrote:
> Am 31.01.2012 00:53, schrieb Anthony Liguori:
>> On 01/30/2012 05:41
On Thu, 2012-02-09 at 09:52 -0800, John Fastabend wrote:
> >> By netlink_notifier do you mean adding a notifier_block and using
> >> atomic_notifier_call_chain()
> >> probably in rtnl_notify()? Then drivers could register with the notifier
> >> chain with
> >> atomic_notifier_chain_register() an
From: Christoffer Dall
Introduces a couple of print functions, which are essentially wrappers
around standard printk functions, with a KVM: prefix.
Functions introduced or modified are:
- kvm_err(fmt, ...)
- kvm_info(fmt, ...)
- kvm_debug(fmt, ...)
- kvm_pr_unimpl(fmt, ...)
- pr_unimpl(vcpu
On 2/9/2012 10:14 AM, Sridhar Samudrala wrote:
> On Wed, 2012-02-08 at 19:22 -0800, John Fastabend wrote:
>> Propagate software FDB table into hardware uc, mc lists when
>> the NETIF_F_HW_FDB is set.
>>
>> This resolves the case below where an embedded switch is used
>> in hardware to do inter-VF o
On Wed, Feb 8, 2012 at 7:59 PM, Josh Boyer wrote:
> On Wed, Feb 8, 2012 at 8:31 PM, Sasha Levin wrote:
>> Hi all,
>>
>> I got the following warning when shutting down a KVM guest with a whole
>> bunch of cores (254 in this case).
>>
>> It's actually pretty easy to reproduce it, it happens every
Hi,
i recently started updating our VMs to qemu-kvm 1.0. Since that I see
that the usb tablet device (used for as pointer device for accurate
mouse positioning) becomes unavailable after live migrating.
If I migrate a few times a Windows 7 VM reliable stops using
the USB tablet and fails back t
Hi,
is anyone aware if there are still problems when enabling the threaded
vnc server?
I saw some VMs crashing when using a qemu-kvm build with
--enable-vnc-thread.
qemu-kvm-1.0[22646]: segfault at 0 ip 7fec1ca7ea0b sp
7fec19d056d0 error 6 in libz.so.1.2.3.3[7fec1ca75000+16000]
qemu-
On Wed, 2012-02-08 at 19:22 -0800, John Fastabend wrote:
> Propagate software FDB table into hardware uc, mc lists when
> the NETIF_F_HW_FDB is set.
>
> This resolves the case below where an embedded switch is used
> in hardware to do inter-VF or VF-PF switching. This patch
> pushes the FDB entry
On 2012-02-09 18:20, Paolo Bonzini wrote:
> On 02/09/2012 05:32 PM, Jan Kiszka wrote:
>> > I mean just check kpcr.self.
>>
>> Yes, clear, but that means that Windows must have initialized FS.base to
>> point to the KPCR also in UP mode. Is that really the case? E.g. when
>> ACPI is off?! I wonder
On 2/9/2012 9:40 AM, Stephen Hemminger wrote:
> On Thu, 09 Feb 2012 09:36:47 -0800
> John Fastabend wrote:
>
>> But the device features makes it easy for user space to learn that the device
>> supports this sort of offload. Now if all SR-IOV devices support this then it
>> doesn't matter but I th
On Thu, 09 Feb 2012 09:36:47 -0800
John Fastabend wrote:
> But the device features makes it easy for user space to learn that the device
> supports this sort of offload. Now if all SR-IOV devices support this then it
> doesn't matter but I thought there were SR-IOV devices that didn't do any
> sw
On 2/8/2012 8:36 PM, Stephen Hemminger wrote:
> On Wed, 08 Feb 2012 19:22:06 -0800
> John Fastabend wrote:
>
>> Propagate software FDB table into hardware uc, mc lists when
>> the NETIF_F_HW_FDB is set.
>>
>> This resolves the case below where an embedded switch is used
>> in hardware to do inter
On 2012-02-09 17:47, Avi Kivity wrote:
> On 02/09/2012 06:32 PM, Jan Kiszka wrote:
We need to patch the causing instruction, so we have to know where it
starts. Or what do you mean?
>>>
>>> Just don't deal with this at all, no one runs on kernels without kernel
>>> irqchip.
>>
>> Not
On Thu, 2012-02-09 at 21:53 +0530, Shashidhar Patil wrote:
> Hi Alex,
> I tested your code changes for two problems
> 1. MSIX vectors allocation for FreeBSD Guest
> Tested the allocation of MSI-X allocation happening for both
> FreeBSD-9.0 (also tested 8.2) and Linux guest.
> Also trie
On 02/09/2012 05:32 PM, Jan Kiszka wrote:
> I mean just check kpcr.self.
Yes, clear, but that means that Windows must have initialized FS.base to
point to the KPCR also in UP mode. Is that really the case? E.g. when
ACPI is off?! I wonder if that explains the reported bug of qemu-kvm
with -no-a
On 02/09/2012 06:32 PM, Jan Kiszka wrote:
> >>
> >> We need to patch the causing instruction, so we have to know where it
> >> starts. Or what do you mean?
> >
> > Just don't deal with this at all, no one runs on kernels without kernel
> > irqchip.
>
> Not true for upstream,
It was introduced in
On 2012-02-09 17:00, Avi Kivity wrote:
> On 02/09/2012 05:39 PM, Jan Kiszka wrote:
>> On 2012-02-09 16:18, Avi Kivity wrote:
>>> On 02/05/2012 02:39 PM, Jan Kiszka wrote:
From: Jan Kiszka
This enables acceleration for MMIO-based TPR registers accesses of
32-bit Windows guest sy
Hi Alex,
I tested your code changes for two problems
1. MSIX vectors allocation for FreeBSD Guest
Tested the allocation of MSI-X allocation happening for both
FreeBSD-9.0 (also tested 8.2) and Linux guest.
Also tried multiple restart of the guests to see if the hosts
still maintains th
On 02/09/2012 05:39 PM, Jan Kiszka wrote:
> On 2012-02-09 16:18, Avi Kivity wrote:
> > On 02/05/2012 02:39 PM, Jan Kiszka wrote:
> >> From: Jan Kiszka
> >>
> >> This enables acceleration for MMIO-based TPR registers accesses of
> >> 32-bit Windows guest systems. It is mostly useful with KVM enable
On 2012-02-09 16:18, Avi Kivity wrote:
> On 02/05/2012 02:39 PM, Jan Kiszka wrote:
>> From: Jan Kiszka
>>
>> This enables acceleration for MMIO-based TPR registers accesses of
>> 32-bit Windows guest systems. It is mostly useful with KVM enabled,
>> either on older Intel CPUs (without flexpriority
On 02/05/2012 02:39 PM, Jan Kiszka wrote:
> From: Jan Kiszka
>
> This enables acceleration for MMIO-based TPR registers accesses of
> 32-bit Windows guest systems. It is mostly useful with KVM enabled,
> either on older Intel CPUs (without flexpriority feature, can also be
> manually disabled for
On 02/09/2012 01:27 PM, Amit Shah wrote:
On (Tue) 07 Feb 2012 [19:05:42], Marcelo Tosatti wrote:
Upon resume from hibernation, CPU 0's hvclock area contains the old
values for system_time and tsc_timestamp. It is necessary for the
hypervisor to update these values with uptodate ones before the
On Wed, Feb 08, 2012 at 01:56:46PM -0200, Marcelo Tosatti wrote:
> On Wed, Feb 08, 2012 at 04:18:48PM +0100, Joerg Roedel wrote:
> > This is not going to work when tsc-scaling is enabled. The
> > adjust_tsc_offset_host() function just scales the offset the same way
> > the tsc is scaled. But that
On 02/08/2012 08:45 PM, Marcelo Tosatti wrote:
> > BTW do we really need fast slot creation/destruction?
>
> At the moment yes. Boot a RHEL/Fedora installation disk (or any other
> guest which uses SYSLINUX splash screen) and you will see.
Another workload that suffers is Windows XP clearing the s
On 02/09/2012 04:23 PM, Avi Kivity wrote:
> > BTW do we really need fast slot creation/destruction?
>
> Not really, but it's good to have infrastructure that copes with
> different workloads. If the patches keep the code simple I think it's a
> good thing to have.
To qualify - taking several tens
On 02/08/2012 05:43 PM, Takuya Yoshikawa wrote:
> [Dropped non-kvm members from cc]
>
> Marcelo Tosatti wrote:
>
> > VGABIOS mode constantly destroys and creates 0xa slot, so
> > performance is required for KVM_SET_MEM too (it can probably be fixed in
> > qemu, but older qemu's must be support
On Wed, 8 Feb 2012 14:38:07 -0200
Marcelo Tosatti wrote:
> Please don't forget the invalidate_page fix.
I will send in a few days.
Takuya
--
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:
On Wed, 8 Feb 2012 16:45:31 -0200
Marcelo Tosatti wrote:
> > For 3: I think doing both "write protection" and "shadow flush" is
> > unnecessary.
>
> If you enable dirty logging on a slot, certainly you have to write
> protect?
When we enable dirty logging, yes.
>
> > BTW do we really need f
On Thu, Feb 09, 2012 at 03:01:26PM +0200, Pekka Enberg wrote:
> On Thu, Feb 9, 2012 at 7:40 AM, Yang Bai wrote:
> > Since the different issues have been handled in the
> > internal of kvm__init, it can only return NULL if error
> > happened.
> >
> > Signed-off-by: Yang Bai
>
> Sorry, I don't und
On Thu, Feb 9, 2012 at 7:40 AM, Yang Bai wrote:
> Since the different issues have been handled in the
> internal of kvm__init, it can only return NULL if error
> happened.
>
> Signed-off-by: Yang Bai
Sorry, I don't understand what this patch is attempting to fix? Why do
you think it's better to
On (Tue) 07 Feb 2012 [19:05:42], Marcelo Tosatti wrote:
>
> Upon resume from hibernation, CPU 0's hvclock area contains the old
> values for system_time and tsc_timestamp. It is necessary for the
> hypervisor to update these values with uptodate ones before the CPU uses
> them.
>
> Abstract TSC's
Paolo Bonzini wrote:
> James, will you include virtio-scsi in 3.4?
The key arguments from my side for inclusion of virtio-scsi are:
- Support for SCSI multipathing, which can optionally be done on the host
operating system.
- We can now use other SCSI(non-block) devices and make them accessible t
On Thu, Feb 09, 2012 at 08:39:28AM +1100, Benjamin Herrenschmidt wrote:
> On Wed, 2012-02-08 at 16:27 +0100, Joerg Roedel wrote:
> > Again, device grouping is done by the IOMMU drivers, so this all
> > belongs
> > into the generic iommu-code rather than the driver core.
>
> Except that there isn't
Hi all,
I've emailed about some related issues lately with some good feedback.
About a year ago we decided to migrate off VMware to KVM. With some
mixed result we're fairly happy but we're somewhat stuck as far as RAM
utilization is concerned.
We've managed to gain some RAM space with KSM and we'
On 02/08/2012 02:37 PM, Christian Hoff wrote:
Again, I have already done much testing with virtio-scsi and can confirm
that the code is working flawlessly. In my opinion, virtio-scsi is a
worthwhile addition to virtio-block and should be considered for inclusion
into mainline kernel code.
Thank
Add 'perf kvm-events' support to analyze kvm vmexit/mmio/ioport smartly
Usage:
- trace kvm events:
perf kvm-events record, or, if other tracepoints are also
interesting, we can append the events like this:
perf kvm-events record -e timer:*
- show the result:
perf
'perf kvm-events' will use kvm_exit and kvm_mmio(read...) to calculate
mmio read emulated time for the old kernel, in order to trace mmio read
event more exactly, we add kvm_mmio_begin to trace the time when mmio read
begins
Also, add kvm_mmio_done to trace the time when mmio/pio is completed
Sig
They will be needed by 'perf kvm-events'
Signed-off-by: Xiao Guangrong
---
arch/x86/include/asm/kvm_host.h | 36 ---
arch/x86/include/asm/svm.h | 205 +--
arch/x86/include/asm/vmx.h | 125
arch/x86/kvm/trace.h
Changlog:
There are some changes from David Ahern's review:
- let the tool to be off-box analysis by getting cpu isa
from HEADER_CPUID feature and removing max-vcpu related code.
- attach per vcpu record structure to the thread by adding a void pointer
in "struct thread".
- remove unnecessary
81 matches
Mail list logo
