Hello All,
I've run into a problem with getting network performance data on
Windows VMs running on KVM. When I check the network data in the
Windows task manager on the VM, it remains at zero, even if large
amounts of data are being transferred. This has been tested on Windows
Server 2008r2 using
On Wed, Jun 26, 2013 at 12:05:54PM -0700, Christoffer Dall wrote:
Hi Gleb and Paolo,
The following changes since commit 87d41fb4da6467622b7a87fd6afe8071abab6dae:
KVM: s390: Fixed priority of execution in STSI (2013-06-20 23:33:01 +0200)
are available in the git repository at:
Hi Alexy,
On Thu, 27 Jun 2013 15:02:31 +1000 Alexey Kardashevskiy a...@ozlabs.ru wrote:
index c488da5..54192b2 100644
--- a/drivers/vfio/vfio.c
+++ b/drivers/vfio/vfio.c
@@ -1370,6 +1370,59 @@ static const struct file_operations vfio_device_fops =
{
};
/**
+ * External user API,
Hi Alexy,
On Thu, 27 Jun 2013 15:02:31 +1000 Alexey Kardashevskiy a...@ozlabs.ru wrote:
+/* Allows an external user (for example, KVM) to unlock an IOMMU group */
+static void vfio_group_del_external_user(struct file *filep)
+{
+ struct vfio_group *group = filep-private_data;
+
+
If vfio_unmap_unpin() returns an error then we leak split. I've moved
the allocation later in the function to fix this.
Signed-off-by: Dan Carpenter dan.carpen...@oracle.com
diff --git a/drivers/vfio/vfio_iommu_type1.c b/drivers/vfio/vfio_iommu_type1.c
index 98231d1..657f6a8 100644
---
VFIO is designed to be used via ioctls on file descriptors
returned by VFIO.
However in some situations support for an external user is required.
The first user is KVM on PPC64 (SPAPR TCE protocol) which is going to
use the existing VFIO groups for exclusive access in real/virtual mode
in the
On Wed, Jun 26, 2013 at 03:30:23PM -0700, Guenter Roeck wrote:
Enable support for MSI interrupts if the device supports it.
Since MSI interrupts are edge triggered, it is no longer necessary to
disable interrupts in the kernel and re-enable them from user-space.
Instead, clearing the interrupt
Signed-off-by: Asias He as...@redhat.com
---
net/vmw_vsock/af_vsock.c | 70
net/vmw_vsock/af_vsock.h | 2 ++
2 files changed, 72 insertions(+)
diff --git a/net/vmw_vsock/af_vsock.c b/net/vmw_vsock/af_vsock.c
index 593071d..bc76ddb 100644
---
This module contains the common code and header files for the following
virtio-vsock and virtio-vhost kernel modules.
Signed-off-by: Asias He as...@redhat.com
---
include/linux/virtio_vsock.h| 200 +++
include/uapi/linux/virtio_ids.h | 1 +
VM sockets virtio transport implementation. This module runs in guest
kernel.
Signed-off-by: Asias He as...@redhat.com
---
net/vmw_vsock/virtio_transport.c | 424 +++
1 file changed, 424 insertions(+)
create mode 100644 net/vmw_vsock/virtio_transport.c
diff
Enable virtio-vsock and vhost-vsock.
Signed-off-by: Asias He as...@redhat.com
---
drivers/vhost/Kconfig | 4
drivers/vhost/Kconfig.vsock | 7 +++
drivers/vhost/Makefile | 5 +
net/vmw_vsock/Kconfig | 18 ++
net/vmw_vsock/Makefile | 4
5
VM sockets vhost transport implementation. This module runs in host
kernel.
Signed-off-by: Asias He as...@redhat.com
---
drivers/vhost/vsock.c | 534 ++
drivers/vhost/vsock.h | 4 +
2 files changed, 538 insertions(+)
create mode 100644
On Wed, Jun 26, 2013 at 03:53:21PM +0200, folkert wrote:
I noticed that on my 3 VMs running server, that there are 10-20 threads
doing i/o. As the VMs are running on HDDs and not SSDs I think that is
counterproductive: won't these threads make the HDDs seek back and forth
constantly?
The
On Fri, Jun 07, 2013 at 04:51:26PM +0800, Xiao Guangrong wrote:
This patch tries to introduce a very simple and scale way to invalidate
all mmio sptes - it need not walk any shadow pages and hold mmu-lock
KVM maintains a global mmio valid generation-number which is stored in
On Thu, Jun 27, 2013 at 11:29:00AM +0300, Gleb Natapov wrote:
On Fri, Jun 07, 2013 at 04:51:26PM +0800, Xiao Guangrong wrote:
This patch tries to introduce a very simple and scale way to invalidate
all mmio sptes - it need not walk any shadow pages and hold mmu-lock
KVM maintains a
On Thu, Jun 27, 2013 at 12:01:10PM +0300, Gleb Natapov wrote:
On Thu, Jun 27, 2013 at 11:29:00AM +0300, Gleb Natapov wrote:
On Fri, Jun 07, 2013 at 04:51:26PM +0800, Xiao Guangrong wrote:
This patch tries to introduce a very simple and scale way to invalidate
all mmio sptes - it need not
On Thu, Jun 27, 2013 at 12:14:24PM +0300, Gleb Natapov wrote:
On Thu, Jun 27, 2013 at 12:01:10PM +0300, Gleb Natapov wrote:
On Thu, Jun 27, 2013 at 11:29:00AM +0300, Gleb Natapov wrote:
On Fri, Jun 07, 2013 at 04:51:26PM +0800, Xiao Guangrong wrote:
This patch tries to introduce a very
On Wed, Jun 26, 2013 at 10:49 PM, Jan Kiszka jan.kis...@web.de wrote:
On 2013-06-26 10:03, Kashyap Chamarthy wrote:
Thanks for the note, it's very helpful! This test actually fails on
older CPUs as well, and I can finally reproduce the issue that Jay also
reported. I'm not able to cure it by
On Thu, 2013-06-27 at 16:59 +1000, Stephen Rothwell wrote:
+/* Allows an external user (for example, KVM) to unlock an IOMMU
group */
+static void vfio_group_del_external_user(struct file *filep)
+{
+ struct vfio_group *group = filep-private_data;
+
+ BUG_ON(filep-f_op !=
On 06/27/2013 05:21 PM, Gleb Natapov wrote:
On Thu, Jun 27, 2013 at 12:14:24PM +0300, Gleb Natapov wrote:
On Thu, Jun 27, 2013 at 12:01:10PM +0300, Gleb Natapov wrote:
On Thu, Jun 27, 2013 at 11:29:00AM +0300, Gleb Natapov wrote:
On Fri, Jun 07, 2013 at 04:51:26PM +0800, Xiao Guangrong wrote:
On Thu, Jun 27, 2013 at 05:50:08PM +0800, Xiao Guangrong wrote:
On 06/27/2013 05:21 PM, Gleb Natapov wrote:
On Thu, Jun 27, 2013 at 12:14:24PM +0300, Gleb Natapov wrote:
On Thu, Jun 27, 2013 at 12:01:10PM +0300, Gleb Natapov wrote:
On Thu, Jun 27, 2013 at 11:29:00AM +0300, Gleb Natapov
Il 27/06/2013 04:56, Paul Gortmaker ha scritto:
Il 26/06/2013 20:11, Paul Gortmaker ha scritto:
spin_unlock(kvm-mmu_lock);
+ kvm_put_kvm(kvm);
srcu_read_unlock(kvm-srcu, idx);
kvm_put_kvm needs to go last. I can fix when applying,
On Thu, Jun 27, 2013 at 03:59:59PM +0800, Asias He wrote:
Hello guys,
In commit d021c344051af91 (VSOCK: Introduce VM Sockets), VMware added VM
Sockets support. VM Sockets allows communication between virtual
machines and the hypervisor. VM Sockets is able to use different
hyervisor neutral
On Thu, Jun 27, 2013 at 04:00:01PM +0800, Asias He wrote:
This module contains the common code and header files for the following
virtio-vsock and virtio-vhost kernel modules.
Signed-off-by: Asias He as...@redhat.com
---
include/linux/virtio_vsock.h| 200 +++
On Thu, Jun 27, 2013 at 04:00:03PM +0800, Asias He wrote:
VM sockets vhost transport implementation. This module runs in host
kernel.
Signed-off-by: Asias He as...@redhat.com
Has any thought been given to how this affects migration?
I don't see any API for an application to
move to a
On 06/27/2013 07:42 PM, Benjamin Herrenschmidt wrote:
On Thu, 2013-06-27 at 16:59 +1000, Stephen Rothwell wrote:
+/* Allows an external user (for example, KVM) to unlock an IOMMU
group */
+static void vfio_group_del_external_user(struct file *filep)
+{
+ struct vfio_group *group =
On 06/27/2013 06:19 PM, Gleb Natapov wrote:
On Thu, Jun 27, 2013 at 05:50:08PM +0800, Xiao Guangrong wrote:
On 06/27/2013 05:21 PM, Gleb Natapov wrote:
On Thu, Jun 27, 2013 at 12:14:24PM +0300, Gleb Natapov wrote:
On Thu, Jun 27, 2013 at 12:01:10PM +0300, Gleb Natapov wrote:
On Thu, Jun 27,
On Sun, Jun 23, 2013 at 10:41:24PM -0600, Alex Williamson wrote:
On Mon, 2013-06-24 at 13:52 +1000, David Gibson wrote:
On Sat, Jun 22, 2013 at 08:28:06AM -0600, Alex Williamson wrote:
On Sat, 2013-06-22 at 22:03 +1000, David Gibson wrote:
On Thu, Jun 20, 2013 at 08:55:13AM -0600, Alex
On Tue, Jun 25, 2013 at 06:34:03PM -0400, Paul Gortmaker wrote:
In commit e935b8372cf8 (KVM: Convert kvm_lock to raw_spinlock),
I am copying Jan, the author of the patch. Commit message says:
Code under this lock requires non-preemptibility, but which code
exactly is this? Is this still true?
On Thu, Jun 27, 2013 at 07:05:20PM +0800, Xiao Guangrong wrote:
On 06/27/2013 06:19 PM, Gleb Natapov wrote:
On Thu, Jun 27, 2013 at 05:50:08PM +0800, Xiao Guangrong wrote:
On 06/27/2013 05:21 PM, Gleb Natapov wrote:
On Thu, Jun 27, 2013 at 12:14:24PM +0300, Gleb Natapov wrote:
On Thu, Jun
Il 27/06/2013 13:09, Gleb Natapov ha scritto:
On Tue, Jun 25, 2013 at 06:34:03PM -0400, Paul Gortmaker wrote:
In commit e935b8372cf8 (KVM: Convert kvm_lock to raw_spinlock),
I am copying Jan, the author of the patch. Commit message says:
Code under this lock requires non-preemptibility, but
On Thu, Jun 27, 2013 at 01:38:29PM +0200, Paolo Bonzini wrote:
Il 27/06/2013 13:09, Gleb Natapov ha scritto:
On Tue, Jun 25, 2013 at 06:34:03PM -0400, Paul Gortmaker wrote:
In commit e935b8372cf8 (KVM: Convert kvm_lock to raw_spinlock),
I am copying Jan, the author of the patch. Commit
On 06/26/2013 02:03 PM, Raghavendra K T wrote:
On 06/24/2013 06:47 PM, Andrew Jones wrote:
On Mon, Jun 24, 2013 at 06:10:14PM +0530, Raghavendra K T wrote:
Results:
===
base = 3.10-rc2 kernel
patched = base + this series
The test was on 32 core (model: Intel(R) Xeon(R) CPU X7560) HT
Il 27/06/2013 13:43, Gleb Natapov ha scritto:
I am copying Jan, the author of the patch. Commit message says:
Code under this lock requires non-preemptibility, but which code
exactly is this? Is this still true?
hardware_enable_nolock/hardware_disable_nolock does.
I suspected
On 2013-06-27 13:38, Paolo Bonzini wrote:
Il 27/06/2013 13:09, Gleb Natapov ha scritto:
On Tue, Jun 25, 2013 at 06:34:03PM -0400, Paul Gortmaker wrote:
In commit e935b8372cf8 (KVM: Convert kvm_lock to raw_spinlock),
I am copying Jan, the author of the patch. Commit message says:
Code under
On Thu, Jun 27, 2013 at 02:16:07PM +0200, Jan Kiszka wrote:
On 2013-06-27 13:38, Paolo Bonzini wrote:
Il 27/06/2013 13:09, Gleb Natapov ha scritto:
On Tue, Jun 25, 2013 at 06:34:03PM -0400, Paul Gortmaker wrote:
In commit e935b8372cf8 (KVM: Convert kvm_lock to raw_spinlock),
I am copying
Il 27/06/2013 14:32, Gleb Natapov ha scritto:
In commit e935b8372cf8 (KVM: Convert kvm_lock to raw_spinlock),
I am copying Jan, the author of the patch. Commit message says:
Code under this lock requires non-preemptibility, but which code
exactly is this? Is this still true?
Il 27/06/2013 15:00, Paolo Bonzini ha scritto:
Il 27/06/2013 14:32, Gleb Natapov ha scritto:
In commit e935b8372cf8 (KVM: Convert kvm_lock to raw_spinlock),
I am copying Jan, the author of the patch. Commit message says:
Code under this lock requires non-preemptibility, but which code
exactly
Il 26/06/2013 20:36, Mathias Krause ha scritto:
Use a const pointer type instead of casting away the const qualifier
from const arrays. Keep the pointer array on the stack, nonetheless.
Making it static just increases the object size.
Signed-off-by: Mathias Krause mini...@googlemail.com
---
Il 26/06/2013 20:36, Mathias Krause ha scritto:
The type for storing values of the sizeof operator should be size_t.
No semantical changes, only type correctness.
Signed-off-by: Mathias Krause mini...@googlemail.com
---
arch/x86/kvm/vmx.c |4 ++--
1 file changed, 2 insertions(+), 2
Il 26/06/2013 20:36, Mathias Krause ha scritto:
Void pointers don't need no casting, drop it.
Signed-off-by: Mathias Krause mini...@googlemail.com
---
arch/x86/kvm/x86.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index
On 27 June 2013 15:33, Paolo Bonzini pbonz...@redhat.com wrote:
Il 26/06/2013 20:36, Mathias Krause ha scritto:
Use a const pointer type instead of casting away the const qualifier
from const arrays. Keep the pointer array on the stack, nonetheless.
Making it static just increases the object
On Wed, 26 Jun 2013 00:52:31 -0500
Rob Landley r...@landley.net wrote:
I intermittently get this from current kernels running under currentish
qemu-git. Look familiar to anybody?
Which kernel do you run in the host? Is the guest doing anything
special?
reboot: machine restart
general
Il 27/06/2013 15:42, Mathias Krause ha scritto:
The const int is not particularly useful, but doesn't hurt either.
It's more of a hint for the compiler to take the values verbatim
instead of allocating stack space for them. But it'll probably already
do it even without that hint.
It won't
On Thu, Jun 27, 2013 at 10:45:01AM +0300, Michael S. Tsirkin wrote:
On Wed, Jun 26, 2013 at 03:30:23PM -0700, Guenter Roeck wrote:
Enable support for MSI interrupts if the device supports it.
Since MSI interrupts are edge triggered, it is no longer necessary to
disable interrupts in the
On 26.06.2013 12:47, Gleb Natapov wrote:
On Mon, Jun 24, 2013 at 10:42:57PM +0200, Stefan Pietsch wrote:
On 24.06.2013 14:30, Gleb Natapov wrote:
On Mon, Jun 24, 2013 at 01:59:34PM +0200, Stefan Pietsch wrote:
As soon as I remove kvmvapic.bin the virtual machine boots with
qemu-kvm 1.5.0. I
On Thu, 2013-06-27 at 10:07 +0300, Dan Carpenter wrote:
If vfio_unmap_unpin() returns an error then we leak split. I've moved
the allocation later in the function to fix this.
Thanks for spotting this and for the patch. The allocation is done
early because if we get an allocation failure
On Thu, 2013-06-27 at 17:14 +1000, Alexey Kardashevskiy wrote:
VFIO is designed to be used via ioctls on file descriptors
returned by VFIO.
However in some situations support for an external user is required.
The first user is KVM on PPC64 (SPAPR TCE protocol) which is going to
use the
Am 17.06.2013 18:17, schrieb Paolo Bonzini:
Il 16/06/2013 17:57, Andreas Färber ha scritto:
Signed-off-by: Andreas Färber afaer...@suse.de
---
gdbstub.c| 2 +-
include/sysemu/kvm.h | 2 +-
kvm-all.c| 5 ++---
kvm-stub.c | 2 +-
4 files changed, 5
On Thu, Jun 27, 2013 at 10:45:01AM +0300, Michael S. Tsirkin wrote:
On Wed, Jun 26, 2013 at 03:30:23PM -0700, Guenter Roeck wrote:
Enable support for MSI interrupts if the device supports it.
Since MSI interrupts are edge triggered, it is no longer necessary to
disable interrupts in the
On 06/27/2013 12:02:36 AM, Alexey Kardashevskiy wrote:
+/*
+ * The KVM guest can be backed with 16MB pages.
+ * In this case, we cannot do page counting from the real mode
+ * as the compound pages are used - they are linked in a list
+ * with pointers as virtual addresses which are inaccessible
Hi Asias,
Looks nice! Some comments inline below (I've removed anything that mst already
commented on).
On 06/27/2013 03:59 AM, Asias He wrote:
Hello guys,
In commit d021c344051af91 (VSOCK: Introduce VM Sockets), VMware added VM
Sockets support. VM Sockets allows communication between virtual
On Thursday, June 27, 2013 1:09:37 AM CDT, Bill Rich wrote:
Hello All,
I've run into a problem with getting network performance data on
Windows VMs running on KVM. When I check the network data in the
Windows task manager on the VM, it remains at zero, even if large
amounts of data are being
On Wednesday, June 26, 2013 8:25:54 PM CDT, Ken Roberts wrote:
Sorry for the user query but I'm not finding expertise on the
Linux mailing lists I belong to. The web site says one-off user
questions are OK.
I have a few VM images on Parallels 8 for Mac. I want them to
be on KVM/Linux.
On Thu, Jun 27, 2013 at 04:09:50PM +0200, Stefan Pietsch wrote:
On 26.06.2013 12:47, Gleb Natapov wrote:
On Mon, Jun 24, 2013 at 10:42:57PM +0200, Stefan Pietsch wrote:
On 24.06.2013 14:30, Gleb Natapov wrote:
On Mon, Jun 24, 2013 at 01:59:34PM +0200, Stefan Pietsch wrote:
As soon as I
Once stop_machine() is gone from the CPU offline path, we won't be able
to depend on disabling preemption to prevent CPUs from going offline
from under us.
Use the get/put_online_cpus_atomic() APIs to prevent CPUs from going
offline, while invoking from atomic context.
Cc: Benjamin Herrenschmidt
Once stop_machine() is gone from the CPU offline path, we won't be able
to depend on disabling preemption to prevent CPUs from going offline
from under us.
Use the get/put_online_cpus_atomic() APIs to prevent CPUs from going
offline, while invoking from atomic context.
Acked-by: Paolo Bonzini
Did You Recieve Our Last Notification!!
--
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://vger.kernel.org/majordomo-info.html
On 06/28/2013 01:44 AM, Alex Williamson wrote:
On Thu, 2013-06-27 at 17:14 +1000, Alexey Kardashevskiy wrote:
VFIO is designed to be used via ioctls on file descriptors
returned by VFIO.
However in some situations support for an external user is required.
The first user is KVM on PPC64
On Fri, 2013-06-28 at 08:57 +1000, Alexey Kardashevskiy wrote:
On 06/28/2013 01:44 AM, Alex Williamson wrote:
On Thu, 2013-06-27 at 17:14 +1000, Alexey Kardashevskiy wrote:
VFIO is designed to be used via ioctls on file descriptors
returned by VFIO.
However in some situations support
--
Ken Roberts
k...@9ci.com
ken.roberts163 @ skype
605-222-5758 @ cell
On Jun 27, 2013, at 2:33 PM, Brian Jackson i...@theiggy.com wrote:
On Wednesday, June 26, 2013 8:25:54 PM CDT, Ken Roberts wrote:
Sorry for the user query but I'm not finding expertise on the Linux mailing
lists I
On 06/28/2013 10:41 AM, Alex Williamson wrote:
On Fri, 2013-06-28 at 08:57 +1000, Alexey Kardashevskiy wrote:
On 06/28/2013 01:44 AM, Alex Williamson wrote:
On Thu, 2013-06-27 at 17:14 +1000, Alexey Kardashevskiy wrote:
VFIO is designed to be used via ioctls on file descriptors
returned by
Hi Michael,
__u32 guest_cid;
Given that cid is like an IP address, 32 bit seems too
limiting. I would go for a 64 bit one or maybe even 128 bit,
so that e.g. GUIDs can be used there.
That's likely based on what vSockets uses, which is in turn based on
what the VMCI device
On Fri, 2013-06-28 at 11:38 +1000, Alexey Kardashevskiy wrote:
On 06/28/2013 10:41 AM, Alex Williamson wrote:
On Fri, 2013-06-28 at 08:57 +1000, Alexey Kardashevskiy wrote:
On 06/28/2013 01:44 AM, Alex Williamson wrote:
On Thu, 2013-06-27 at 17:14 +1000, Alexey Kardashevskiy wrote:
VFIO
Hi Michael,
+ u32 cid = VHOST_VSOCK_DEFAULT_HOST_CID;
+ return cid;
+}
+
Interesting. So all hosts in fact have the same CID?
Host here means the thing _below_ the VM. Any process running on
the host OS can be addressed with cid 2. Each VM gets its own cid.
So communication is
One possibility for a softlockup report in a Linux VM, is that the host
system is overcommitted to the point where the watchdog task is unable
to make progress (unable to touch the watchdog).
Maintain the increment in stolen time for the period of
softlockup threshold detection (20 seconds by
On 06/28/2013 12:37 PM, Alex Williamson wrote:
On Fri, 2013-06-28 at 11:38 +1000, Alexey Kardashevskiy wrote:
On 06/28/2013 10:41 AM, Alex Williamson wrote:
On Fri, 2013-06-28 at 08:57 +1000, Alexey Kardashevskiy wrote:
On 06/28/2013 01:44 AM, Alex Williamson wrote:
On Thu, 2013-06-27 at
On Thu, Jun 27, 2013 at 07:25:40PM -0700, Andy King wrote:
Hi Michael,
__u32 guest_cid;
Given that cid is like an IP address, 32 bit seems too
limiting. I would go for a 64 bit one or maybe even 128 bit,
so that e.g. GUIDs can be used there.
That's likely based on what
Hi Alexy,
On Thu, 27 Jun 2013 15:02:31 +1000 Alexey Kardashevskiy a...@ozlabs.ru wrote:
index c488da5..54192b2 100644
--- a/drivers/vfio/vfio.c
+++ b/drivers/vfio/vfio.c
@@ -1370,6 +1370,59 @@ static const struct file_operations vfio_device_fops =
{
};
/**
+ * External user API,
Hi Alexy,
On Thu, 27 Jun 2013 15:02:31 +1000 Alexey Kardashevskiy a...@ozlabs.ru wrote:
+/* Allows an external user (for example, KVM) to unlock an IOMMU group */
+static void vfio_group_del_external_user(struct file *filep)
+{
+ struct vfio_group *group = filep-private_data;
+
+
On Thu, 2013-06-27 at 16:59 +1000, Stephen Rothwell wrote:
+/* Allows an external user (for example, KVM) to unlock an IOMMU
group */
+static void vfio_group_del_external_user(struct file *filep)
+{
+ struct vfio_group *group = filep-private_data;
+
+ BUG_ON(filep-f_op !=
On 06/27/2013 07:42 PM, Benjamin Herrenschmidt wrote:
On Thu, 2013-06-27 at 16:59 +1000, Stephen Rothwell wrote:
+/* Allows an external user (for example, KVM) to unlock an IOMMU
group */
+static void vfio_group_del_external_user(struct file *filep)
+{
+ struct vfio_group *group =
On Sun, Jun 23, 2013 at 10:41:24PM -0600, Alex Williamson wrote:
On Mon, 2013-06-24 at 13:52 +1000, David Gibson wrote:
On Sat, Jun 22, 2013 at 08:28:06AM -0600, Alex Williamson wrote:
On Sat, 2013-06-22 at 22:03 +1000, David Gibson wrote:
On Thu, Jun 20, 2013 at 08:55:13AM -0600, Alex
On 06/27/2013 12:02:36 AM, Alexey Kardashevskiy wrote:
+/*
+ * The KVM guest can be backed with 16MB pages.
+ * In this case, we cannot do page counting from the real mode
+ * as the compound pages are used - they are linked in a list
+ * with pointers as virtual addresses which are inaccessible
Once stop_machine() is gone from the CPU offline path, we won't be able
to depend on disabling preemption to prevent CPUs from going offline
from under us.
Use the get/put_online_cpus_atomic() APIs to prevent CPUs from going
offline, while invoking from atomic context.
Cc: Benjamin Herrenschmidt
Did You Recieve Our Last Notification!!
--
To unsubscribe from this list: send the line unsubscribe kvm-ppc in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
76 matches
Mail list logo
