Hi,
For (2), you cannot use bus=X,addr=Y because it makes assumptions about
the PCI topology which may change in newer -M pc's.
Why should the PCI topology for 'pc' ever change?
We'll probably get q35 support some day, but when this lands I expect
we'll see a new machine type 'q35', so
Am 20.01.2011 06:19, schrieb Yoshiaki Tamura:
+return;
+}
+
+bdrv_aio_writev(bs, blk_req-reqs[0].sector, blk_req-reqs[0].qiov,
+blk_req-reqs[0].nb_sectors, blk_req-reqs[0].cb,
+blk_req-reqs[0].opaque);
Same here.
+
On 2011-01-19 20:32, Blue Swirl wrote:
On Wed, Jan 19, 2011 at 4:57 PM, Anthony Liguori
aligu...@linux.vnet.ibm.com wrote:
On 01/19/2011 07:15 AM, Markus Armbruster wrote:
So they interact with KVM (need kvm_state), and they interact with the
emulated PCI bus. Could you elaborate on the
On Thu, Jan 20, 2011 at 09:44:05AM +0100, Gerd Hoffmann wrote:
Hi,
For (2), you cannot use bus=X,addr=Y because it makes assumptions about
the PCI topology which may change in newer -M pc's.
Why should the PCI topology for 'pc' ever change?
We'll probably get q35 support some day, but
2011/1/20 Kevin Wolf kw...@redhat.com:
Am 20.01.2011 06:19, schrieb Yoshiaki Tamura:
+ return;
+ }
+
+ bdrv_aio_writev(bs, blk_req-reqs[0].sector, blk_req-reqs[0].qiov,
+ blk_req-reqs[0].nb_sectors, blk_req-reqs[0].cb,
+
On Wed, Jan 19, 2011 at 10:53:52AM -0800, Jeremy Fitzhardinge wrote:
The reason for wanting this should be clear I guess, it allows PI.
Well, if we can expand the spinlock to include an owner, then all this
becomes moot...
How so? Having an owner will not eliminate the need for
Am 20.01.2011 11:39, schrieb Yoshiaki Tamura:
2011/1/20 Kevin Wolf kw...@redhat.com:
Am 20.01.2011 06:19, schrieb Yoshiaki Tamura:
+return;
+}
+
+bdrv_aio_writev(bs, blk_req-reqs[0].sector, blk_req-reqs[0].qiov,
+blk_req-reqs[0].nb_sectors,
I'm suddenly getting lots of the following errors on a server running
2.36.7, but I have no idea what it means:
2011-01-20T12:41:18.358603+01:00 phy005 kernel: EPT: Misconfiguration.
2011-01-20T12:41:18.358621+01:00 phy005 kernel: EPT: GPA: 0x3dbff6b0
2011-01-20T12:41:18.358624+01:00 phy005
On Thu, Jan 20, 2011 at 12:48, Ruben Kerkhof ru...@rubenkerkhof.com wrote:
I'm suddenly getting lots of the following errors on a server running
2.36.7, but I have no idea what it means:
Sorry, that should be 2.34.7.
Kind regards,
Ruben
--
To unsubscribe from this list: send the line
On Wed, Jan 19, 2011 at 10:53:52AM -0800, Jeremy Fitzhardinge wrote:
I didn't really read the patch, and I totally forgot everything from
when I looked at the Xen series, but does the Xen/KVM hypercall
interface for this include the vcpu to await the kick from?
My guess is not, since the
The following series implements page cache control,
this is a split out version of patch 1 of version 3 of the
page cache optimization patches posted earlier at
Previous posting http://lwn.net/Articles/419564/
The previous few revision received lot of comments, I've tried to
address as many of
This patch moves zone_reclaim and associated helpers
outside CONFIG_NUMA. This infrastructure is reused
in the patches for page cache control that follow.
Signed-off-by: Balbir Singh bal...@linux.vnet.ibm.com
---
include/linux/mmzone.h |4 ++--
include/linux/swap.h |4 ++--
Changelog v3
1. Renamed zone_reclaim_unmapped_pages to zone_reclaim_pages
Refactor zone_reclaim, move reusable functionality outside
of zone_reclaim. Make zone_reclaim_unmapped_pages modular
Signed-off-by: Balbir Singh bal...@linux.vnet.ibm.com
---
mm/vmscan.c | 35
Changelog v2
1. Use a config option to enable the code (Andrew Morton)
2. Explain the magic tunables in the code or at-least attempt
to explain them (General comment)
3. Hint uses of the boot parameter with unlikely (Andrew Morton)
4. Use better names (balanced is not a good naming convention)
On Thu, 2011-01-20 at 17:29 +0530, Srivatsa Vaddagiri wrote:
If we had a yield-to [1] sort of interface _and_ information on which vcpu
owns a lock, then lock-spinners can yield-to the owning vcpu,
and then I'd nak it for being stupid ;-)
really, yield*() is retarded, never even consider
2011/1/20 Kevin Wolf kw...@redhat.com:
Am 20.01.2011 11:39, schrieb Yoshiaki Tamura:
2011/1/20 Kevin Wolf kw...@redhat.com:
Am 20.01.2011 06:19, schrieb Yoshiaki Tamura:
+ return;
+ }
+
+ bdrv_aio_writev(bs, blk_req-reqs[0].sector,
blk_req-reqs[0].qiov,
+
Prints more information when IO_PAGE_FAULT event occurs.
Signed-off-by: Prasad Joshi prasadjoshi...@gmail.com
---
diff --git a/arch/x86/include/asm/amd_iommu_types.h
b/arch/x86/include/asm/amd_iommu_types.h
index e3509fc..add56b3 100644
--- a/arch/x86/include/asm/amd_iommu_types.h
+++
Am 20.01.2011 14:50, schrieb Yoshiaki Tamura:
2011/1/20 Kevin Wolf kw...@redhat.com:
Am 20.01.2011 11:39, schrieb Yoshiaki Tamura:
2011/1/20 Kevin Wolf kw...@redhat.com:
Am 20.01.2011 06:19, schrieb Yoshiaki Tamura:
+return;
+}
+
+bdrv_aio_writev(bs, blk_req-reqs[0].sector,
On Thu, Jan 20, 2011 at 02:41:46PM +0100, Peter Zijlstra wrote:
On Thu, 2011-01-20 at 17:29 +0530, Srivatsa Vaddagiri wrote:
If we had a yield-to [1] sort of interface _and_ information on which vcpu
owns a lock, then lock-spinners can yield-to the owning vcpu,
and then I'd nak it for
On Thu, 20 Jan 2011, Balbir Singh wrote:
--- a/include/linux/swap.h
+++ b/include/linux/swap.h
@@ -253,11 +253,11 @@ extern int vm_swappiness;
extern int remove_mapping(struct address_space *mapping, struct page *page);
extern long vm_total_pages;
+extern int sysctl_min_unmapped_ratio;
Reviewed-by: Christoph Lameter c...@linux.com
--
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
Change cleanup function.
1) Try cleanup faster way.
2) Try restart ssh session.
3) Try restart machine.
*) If test end with kernel crash directly try to restart machine.
Signed-off-by: Jiri Zupka jzu...@redhat.com
---
client/tests/kvm/scripts/virtio_guest.py | 79 -
On Thu, 20 Jan 2011, Balbir Singh wrote:
+ unmapped_page_control
+ [KNL] Available if CONFIG_UNMAPPED_PAGECACHE_CONTROL
+ is enabled. It controls the amount of unmapped memory
+ that is present in the system. This boot option
When MSI is off, each interrupt needs to be bounced through the io
thread when it's set/cleared, so vhost-net causes more context switches and
higher CPU utilization than userspace virtio which handles networking in
the same thread.
We'll need to fix this by adding level irq support in kvm irqfd,
On Thu, Jan 20, 2011 at 11:03:31AM +0800, Xiao Guangrong wrote:
On 01/20/2011 02:13 AM, Marcelo Tosatti wrote:
On Wed, Jan 19, 2011 at 01:16:23PM +0800, Xiao Guangrong wrote:
On 01/12/2011 03:39 PM, Xiao Guangrong wrote:
Fix:
[ 1001.499596]
On 01/20/2011 09:35 AM, Michael S. Tsirkin wrote:
When MSI is off, each interrupt needs to be bounced through the io
thread when it's set/cleared, so vhost-net causes more context switches and
higher CPU utilization than userspace virtio which handles networking in
the same thread.
We'll need
2011/1/20 Kevin Wolf kw...@redhat.com:
Am 20.01.2011 14:50, schrieb Yoshiaki Tamura:
2011/1/20 Kevin Wolf kw...@redhat.com:
Am 20.01.2011 11:39, schrieb Yoshiaki Tamura:
2011/1/20 Kevin Wolf kw...@redhat.com:
Am 20.01.2011 06:19, schrieb Yoshiaki Tamura:
+ return;
+ }
+
+
On Thu, Jan 20, 2011 at 09:43:57AM -0600, Anthony Liguori wrote:
On 01/20/2011 09:35 AM, Michael S. Tsirkin wrote:
When MSI is off, each interrupt needs to be bounced through the io
thread when it's set/cleared, so vhost-net causes more context switches and
higher CPU utilization than
On Thu, 2011-01-20 at 17:35 +0200, Michael S. Tsirkin wrote:
When MSI is off, each interrupt needs to be bounced through the io
thread when it's set/cleared, so vhost-net causes more context switches and
higher CPU utilization than userspace virtio which handles networking in
the same thread.
https://bugzilla.kernel.org/show_bug.cgi?id=27052
Marcelo Tosatti mtosa...@redhat.com changed:
What|Removed |Added
CC||mtosa...@redhat.com
https://bugzilla.kernel.org/show_bug.cgi?id=27052
--- Comment #5 from Marcelo Tosatti mtosa...@redhat.com 2011-01-20 17:30:38
---
Created an attachment (id=44522)
-- (https://bugzilla.kernel.org/attachment.cgi?id=44522)
KVM: MMU: fix rmap_remove on non present sptes
KVM: MMU: fix
On Thu, Jan 20, 2011 at 08:31:53AM -0800, Sridhar Samudrala wrote:
On Thu, 2011-01-20 at 17:35 +0200, Michael S. Tsirkin wrote:
When MSI is off, each interrupt needs to be bounced through the io
thread when it's set/cleared, so vhost-net causes more context switches and
higher CPU
On 01/20/2011 03:42 AM, Srivatsa Vaddagiri wrote:
On Wed, Jan 19, 2011 at 10:53:52AM -0800, Jeremy Fitzhardinge wrote:
The reason for wanting this should be clear I guess, it allows PI.
Well, if we can expand the spinlock to include an owner, then all this
becomes moot...
How so? Having an
On 01/20/2011 03:59 AM, Srivatsa Vaddagiri wrote:
At least in the Xen code, a current owner isn't very useful, because we
need the current owner to kick the *next* owner to life at release time,
which we can't do without some structure recording which ticket belongs
to which cpu.
If we had a
On Thu, 2011-01-20 at 17:35 +0200, Michael S. Tsirkin wrote:
When MSI is off, each interrupt needs to be bounced through the io
thread when it's set/cleared, so vhost-net causes more context switches and
higher CPU utilization than userspace virtio which handles networking in
the same thread.
On Thu, Jan 20, 2011 at 9:33 AM, Jan Kiszka jan.kis...@siemens.com wrote:
On 2011-01-19 20:32, Blue Swirl wrote:
On Wed, Jan 19, 2011 at 4:57 PM, Anthony Liguori
aligu...@linux.vnet.ibm.com wrote:
On 01/19/2011 07:15 AM, Markus Armbruster wrote:
So they interact with KVM (need kvm_state),
On 01/20/2011 03:33 AM, Jan Kiszka wrote:
On 2011-01-19 20:32, Blue Swirl wrote:
On Wed, Jan 19, 2011 at 4:57 PM, Anthony Liguori
aligu...@linux.vnet.ibm.com wrote:
On 01/19/2011 07:15 AM, Markus Armbruster wrote:
So they interact with KVM (need kvm_state), and they
On 01/20/2011 02:44 AM, Gerd Hoffmann wrote:
Hi,
For (2), you cannot use bus=X,addr=Y because it makes assumptions about
the PCI topology which may change in newer -M pc's.
Why should the PCI topology for 'pc' ever change?
We'll probably get q35 support some day, but when this lands I
On 01/20/2011 04:33 AM, Daniel P. Berrange wrote:
On Thu, Jan 20, 2011 at 09:44:05AM +0100, Gerd Hoffmann wrote:
Hi,
For (2), you cannot use bus=X,addr=Y because it makes assumptions about
the PCI topology which may change in newer -M pc's.
Why should the PCI topology
https://bugzilla.kernel.org/show_bug.cgi?id=27052
--- Comment #6 from prochazka prochazka.nico...@gmail.com 2011-01-20
19:45:49 ---
hello,
I do not understand, patch seems to be already apply on 2.6.37 kernel tree,
and my test are based on this release.
NP.
--
Configure bugmail:
On Thu, Jan 20, 2011 at 7:37 PM, Anthony Liguori
aligu...@linux.vnet.ibm.com wrote:
On 01/20/2011 03:33 AM, Jan Kiszka wrote:
On 2011-01-19 20:32, Blue Swirl wrote:
On Wed, Jan 19, 2011 at 4:57 PM, Anthony Liguori
aligu...@linux.vnet.ibm.com wrote:
On 01/19/2011 07:15 AM, Markus
On 2011-01-20 20:27, Blue Swirl wrote:
On Thu, Jan 20, 2011 at 9:33 AM, Jan Kiszka jan.kis...@siemens.com wrote:
On 2011-01-19 20:32, Blue Swirl wrote:
On Wed, Jan 19, 2011 at 4:57 PM, Anthony Liguori
aligu...@linux.vnet.ibm.com wrote:
On 01/19/2011 07:15 AM, Markus Armbruster wrote:
So
On 2011-01-20 20:37, Anthony Liguori wrote:
On 01/20/2011 03:33 AM, Jan Kiszka wrote:
On 2011-01-19 20:32, Blue Swirl wrote:
On Wed, Jan 19, 2011 at 4:57 PM, Anthony Liguori
aligu...@linux.vnet.ibm.com wrote:
On 01/19/2011 07:15 AM, Markus Armbruster wrote:
So they
With CONFIG_FAIR_GROUP_SCHED, each task_group has its own cfs_rq.
Yielding to a task from another cfs_rq may be worthwhile, since
a process calling yield typically cannot use the CPU right now.
Therefor, we want to check the per-cpu nr_running, not the
cgroup local one.
Signed-off-by: Rik van
The clear_buddies function does not seem to play well with the concept
of hierarchical runqueues. In the following tree, task groups are
represented by 'G', tasks by 'T', next by 'n' and last by 'l'.
(nl)
/\
G(nl) G
/ \ \
T(l) T(n) T
This situation can arise when a
Use the buddy mechanism to implement yield_task_fair. This
allows us to skip onto the next highest priority se at every
level in the CFS tree, unless doing so would introduce gross
unfairness in CPU time distribution.
We order the buddy selection in pick_next_entity to check
yield first, then
From: Mike Galbraith efa...@gmx.de
Currently only implemented for fair class tasks.
Add a yield_to_task method() to the fair scheduling class. allowing the
caller of yield_to() to accelerate another thread in it's thread group,
task group.
Implemented via a scheduler hint, using cfs_rq-next to
Instead of sleeping in kvm_vcpu_on_spin, which can cause gigantic
slowdowns of certain workloads, we instead use yield_to to get
another VCPU in the same KVM guest to run sooner.
This seems to give a 10-15% speedup in certain workloads, versus
not having PLE at all.
Signed-off-by: Rik van Riel
Keep track of which task is running a KVM vcpu. This helps us
figure out later what task to wake up if we want to boost a
vcpu that got preempted.
Unfortunately there are no guarantees that the same task
always keeps the same vcpu, so we can only track the task
across a single run of the vcpu.
When running SMP virtual machines, it is possible for one VCPU to be
spinning on a spinlock, while the VCPU that holds the spinlock is not
currently running, because the host scheduler preempted it to run
something else.
Both Intel and AMD CPUs have a feature that detects when a virtual
CPU is
Export the symbols required for a race-free kvm_vcpu_on_spin.
Signed-off-by: Rik van Riel r...@redhat.com
diff --git a/kernel/fork.c b/kernel/fork.c
index 3b159c5..adc8f47 100644
--- a/kernel/fork.c
+++ b/kernel/fork.c
@@ -191,6 +191,7 @@ void __put_task_struct(struct task_struct *tsk)
Fairness is enforced by pick_next_entity, so we can drop some
superfluous tests from yield_to.
Signed-off-by: Rik van Riel r...@redhat.com
---
kernel/sched.c |8
1 files changed, 0 insertions(+), 8 deletions(-)
diff --git a/kernel/sched.c b/kernel/sched.c
index 1f38ed2..398eedf
On Thu, Jan 20, 2011 at 9:22 PM, Jan Kiszka jan.kis...@web.de wrote:
On 2011-01-20 20:27, Blue Swirl wrote:
On Thu, Jan 20, 2011 at 9:33 AM, Jan Kiszka jan.kis...@siemens.com wrote:
On 2011-01-19 20:32, Blue Swirl wrote:
On Wed, Jan 19, 2011 at 4:57 PM, Anthony Liguori
On 2011-01-20 21:02, Blue Swirl wrote:
I think KVMState was designed to match KVM ioctl interface: all stuff
that is needed for talking to KVM or received from KVM are there. But
I think this shouldn't be a design driver.
Agreed. The nice cleanup would probably be the complete assimilation of
On 2011-01-20 22:40, Blue Swirl wrote:
On Thu, Jan 20, 2011 at 9:22 PM, Jan Kiszka jan.kis...@web.de wrote:
On 2011-01-20 20:27, Blue Swirl wrote:
On Thu, Jan 20, 2011 at 9:33 AM, Jan Kiszka jan.kis...@siemens.com wrote:
On 2011-01-19 20:32, Blue Swirl wrote:
On Wed, Jan 19, 2011 at 4:57 PM,
On Tue, Jan 18, 2011 at 04:08:33AM -0800, Mehul Chadha wrote:
Hi,
I have been trying to get suspending and resuming done across kvm and qemu.
While resuming a suspended state in kvm, an error was generated saying
unknown section kvmclock . I modified loadvm in qemu to neglect the
kvmclock
On Sat, Jan 15, 2011 at 10:00:53AM +0100, Jan Kiszka wrote:
From: Jan Kiszka jan.kis...@siemens.com
This case is a pure user space error we do not need to record. Moreover,
it can be misused to flood the kernel log. Remove it.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
Applied,
On Mon, Jan 17, 2011 at 10:17:49AM -0700, Alex Williamson wrote:
The vmsd code expects the fields structure to be properly terminated,
not NULL. An assigned device should never be saved or restored, and
recent qemu fixes to the no_migrate flag should ensure this, but let's
avoid setting the
On Tue, Jan 18, 2011 at 03:42:57PM +0200, Michael S. Tsirkin wrote:
Fix virtio-pci error handling in the mask notifiers: be careful to undo
exactly what we did so far.
Reported-by: Alex Williamson alex.william...@redhat.com
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
This is
On Mon, Jan 17, 2011 at 09:21:08PM +0100, Heiko Carstens wrote:
From: Heiko Carstens heiko.carst...@de.ibm.com
Get rid of this warning:
CC arch/s390/kvm/../../../virt/kvm/kvm_main.o
arch/s390/kvm/../../../virt/kvm/kvm_main.c:596:12: warning:
'kvm_create_dirty_bitmap' defined but
On Mon, Jan 17, 2011 at 08:47:39AM +0800, Huang Ying wrote:
Hi, Andrew,
On Sun, 2011-01-16 at 23:35 +0800, Avi Kivity wrote:
On 01/14/2011 03:37 AM, Huang Ying wrote:
On Thu, 2011-01-13 at 18:43 +0800, Avi Kivity wrote:
On 01/13/2011 10:42 AM, Huang Ying wrote:
Make
On Thu, 2011-01-20 at 19:47 +0200, Michael S. Tsirkin wrote:
On Thu, Jan 20, 2011 at 08:31:53AM -0800, Sridhar Samudrala wrote:
On Thu, 2011-01-20 at 17:35 +0200, Michael S. Tsirkin wrote:
When MSI is off, each interrupt needs to be bounced through the io
thread when it's set/cleared, so
On 01/20/2011 10:07 AM, Michael S. Tsirkin wrote:
On Thu, Jan 20, 2011 at 09:43:57AM -0600, Anthony Liguori wrote:
On 01/20/2011 09:35 AM, Michael S. Tsirkin wrote:
When MSI is off, each interrupt needs to be bounced through the io
thread when it's set/cleared, so vhost-net causes
On Thu, 2011-01-20 at 18:23 -0600, Anthony Liguori wrote:
On 01/20/2011 10:07 AM, Michael S. Tsirkin wrote:
On Thu, Jan 20, 2011 at 09:43:57AM -0600, Anthony Liguori wrote:
On 01/20/2011 09:35 AM, Michael S. Tsirkin wrote:
When MSI is off, each interrupt needs to be bounced
[ Trimmed Eric from CC list as vger was complaining that it is too long ]
On Tue, Jan 18, 2011 at 11:41:22AM -0800, Rick Jones wrote:
So it won't be all that simple to implement well, and before we try,
I'd like to know whether there are applications that are helped
by it. For example, we
Simon Horman wrote:
[ Trimmed Eric from CC list as vger was complaining that it is too long ]
...
I have constructed a test where I run an un-paced UDP_STREAM test in
one guest and a paced omni rr test in another guest at the same time.
Breifly I get the following results from the omni test..
https://bugzilla.kernel.org/show_bug.cgi?id=27052
--- Comment #7 from Marcelo Tosatti mtosa...@redhat.com 2011-01-21 03:27:36
---
Nicolas,
My bad. Can you please try the following patch.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving
https://bugzilla.kernel.org/show_bug.cgi?id=27052
--- Comment #8 from Marcelo Tosatti mtosa...@redhat.com 2011-01-21 03:29:36
---
Created an attachment (id=44552)
-- (https://bugzilla.kernel.org/attachment.cgi?id=44552)
update sp-gfns on pte update path
--
Configure bugmail:
[Resubmit of prior version which contained a wayward
patch hunk. Thanks Marcelo]
A correction to Intel cpu model CPUID data (patch queued)
caused winxp to BSOD when booted with a Penryn model.
This was traced to the CPUID model field correction from
6 - 23 (as is proper for a Penryn class of
* Christoph Lameter c...@linux.com [2011-01-20 08:49:27]:
On Thu, 20 Jan 2011, Balbir Singh wrote:
--- a/include/linux/swap.h
+++ b/include/linux/swap.h
@@ -253,11 +253,11 @@ extern int vm_swappiness;
extern int remove_mapping(struct address_space *mapping, struct page
*page);
* Christoph Lameter c...@linux.com [2011-01-20 08:50:40]:
Reviewed-by: Christoph Lameter c...@linux.com
Thanks for the review!
--
Three Cheers,
Balbir
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More
* Christoph Lameter c...@linux.com [2011-01-20 09:00:09]:
On Thu, 20 Jan 2011, Balbir Singh wrote:
+ unmapped_page_control
+ [KNL] Available if CONFIG_UNMAPPED_PAGECACHE_CONTROL
+ is enabled. It controls the amount of unmapped memory
+
72 matches
Mail list logo
