Hi Liuis,
On Tue, Sep 04, 2012 at 10:08:09PM +0200, Lluís Vilanova wrote:
Hi there,
Given that right now I don't have enough time to write the paper that should
accompany this work, I've decided to open it up so that whoever is interested
can have access to it.
You can get some
On 09/20/12 17:38, Hans de Goede wrote:
There are several issues with our handling of the MULT epcap field
of interrupt qhs, which this patch fixes.
Patch added to usb patch queue.
thanks,
Gerd
Am 21.09.2012 01:20, schrieb Kevin Shanahan:
If readonly=on is given at device creation time, the -readonly flag
needs to be set in the block driver state for this device so that
readonly-ness is preserved across media changes (qmp change command).
Similarly, to preserve the snapshot property
On Thu, Sep 20, 2012 at 5:07 PM, Avi Kivity a...@redhat.com wrote:
On 09/20/2012 10:51 AM, liu ping fan wrote:
On Wed, Sep 19, 2012 at 5:23 PM, Avi Kivity a...@redhat.com wrote:
On 09/19/2012 12:19 PM, liu ping fan wrote:
On Wed, Sep 19, 2012 at 5:14 PM, Paolo Bonzini pbonz...@redhat.com
On Thu, Sep 20, 2012 at 5:15 PM, Avi Kivity a...@redhat.com wrote:
On 09/20/2012 10:51 AM, liu ping fan wrote:
On Wed, Sep 19, 2012 at 5:05 PM, Avi Kivity a...@redhat.com wrote:
On 09/19/2012 11:36 AM, liu ping fan wrote:
It basically means you can't hold contents of device state in local
Orit Wasserman owass...@redhat.com writes:
On 09/20/2012 04:14 PM, Markus Armbruster wrote:
Orit Wasserman owass...@redhat.com writes:
getaddrinfo can give us a list of addresses, but we only try to
connect to the first one. If that fails we never proceed to
the next one. This is common
Orit Wasserman owass...@redhat.com writes:
On 09/20/2012 04:19 PM, Markus Armbruster wrote:
Orit Wasserman owass...@redhat.com writes:
Changes from v2:
- remove the use of getnameinfo
- remove errp for inet_connect_addr
- remove QemuOpt block
- fix errors in
Am 20.09.2012 19:03, schrieb Stefan Weil:
Am 05.09.2012 19:45, schrieb Stefan Weil:
Am 05.09.2012 19:15, schrieb Stefan Weil:
AFAIK, binutils moved to GPL 3. Therefore I don't expect that
QEMU will update to upstream in the next years.
We'll have to maintain the code which we have.
Try
Oh! And from this thread, my understanding of the reason for the rule
of lock sequence: coarse-fine is that biglock means higher
possibility of conflict, so we try it first, then try the fine-lock.
In this way, we have a smaller window for holding fine-lock which
means the other thread can
Il 21/09/2012 05:50, Bharata B Rao ha scritto:
Just shooting around a possibility: why reinvent the wheel poorly if we
can use a full-blown URI parsing library? The libxml2 one is very good
and easy to use.
It is also pretty much self-contained and has hardly seen a commit in 3
Am 20.09.2012 21:13, schrieb Jeff Cody:
This is the support for reopen, for win32. Note that there is a key
difference in the win32 reopen, namely that it is not guaranteed safe
like all the other drivers. Attempts are made to reopen the file, or
open the file in a new handle prior to
On 21.09.2012 04:18, Max Filippov wrote:
diff --git a/tcg/tcg.c b/tcg/tcg.c
+#ifdef CONFIG_DEBUG_TCG
+static void tcg_sanity_check(TCGContext *s)
#ifndef CONFIG_DEBUG_TCG
#define tcg_sanity_check(s) /*empty*/
#else
static void tcg_sanity_check(TCGContext *s)
+{
[]
+}
+#endif
@@ -2082,6
On Thu, 20 Sep 2012 16:03:17 -0400
Don Slutz d...@cloudswitch.com wrote:
Fix duplicate name (kvmclock = kvm_clock2) also.
Signed-off-by: Don Slutz d...@cloudswitch.com
---
target-i386/cpu.c | 12
1 files changed, 8 insertions(+), 4 deletions(-)
diff --git
Il 21/09/2012 10:33, Kevin Wolf ha scritto:
+/* could not reopen the file handle, so fall back to opening
+ * new file (CreateFile) */
+if (raw_s-hfile == INVALID_HANDLE_VALUE) {
+raw_s-hfile = CreateFile(state-bs-filename, access_flags,
+
Signed-off-by: Juan Quintela quint...@redhat.com
---
arch_init.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch_init.c b/arch_init.c
index f849f9b..cdd8ab7 100644
--- a/arch_init.c
+++ b/arch_init.c
@@ -489,6 +489,7 @@ static int ram_save_setup(QEMUFile *f, void *opaque)
ram_addr_t
Adjust all callers
Signed-off-by: Juan Quintela quint...@redhat.com
---
buffered_file.c | 8 ++--
migration.c | 7 ---
migration.h | 2 +-
3 files changed, 11 insertions(+), 6 deletions(-)
diff --git a/buffered_file.c b/buffered_file.c
index 9db73dc..6d9a50b 100644
---
Signed-off-by: Juan Quintela quint...@redhat.com
---
block-migration.c | 21 +++--
1 file changed, 11 insertions(+), 10 deletions(-)
diff --git a/block-migration.c b/block-migration.c
index 565628f..9f94733 100644
--- a/block-migration.c
+++ b/block-migration.c
@@ -423,10 +423,9
This means we don't need to pass through qemu_file to get the errors.
Adjust all callers.
Signed-off-by: Juan Quintela quint...@redhat.com
---
block-migration.c | 22 --
1 file changed, 8 insertions(+), 14 deletions(-)
diff --git a/block-migration.c b/block-migration.c
index
Signed-off-by: Juan Quintela quint...@redhat.com
---
arch_init.c | 6 ++
trace-events | 4
2 files changed, 10 insertions(+)
diff --git a/arch_init.c b/arch_init.c
index a58e8c3..6e0d7c4 100644
--- a/arch_init.c
+++ b/arch_init.c
@@ -45,6 +45,7 @@
#include hw/pcspk.h
#include
Or the amount of data written if there is no error. Adjust all callers.
Signed-off-by: Juan Quintela quint...@redhat.com
---
buffered_file.c | 32
1 file changed, 24 insertions(+), 8 deletions(-)
diff --git a/buffered_file.c b/buffered_file.c
index
Hi Mel,
Thank you for this series. I have applied on clean 3.6-rc5 and tested, and
it works well for me - the lock contention is (still) gone and
isolate_freepages_block is much reduced.
Here is a typical test with these patches:
# grep -F '[k]' report | head -8
65.20% qemu-kvm
It was setting last_error directly once, and with the helper the other time.
Signed-off-by: Juan Quintela quint...@redhat.com
---
savevm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/savevm.c b/savevm.c
index 8ddb9d5..4e4aa3c 100644
--- a/savevm.c
+++ b/savevm.c
@@ -501,7
Signed-off-by: Juan Quintela quint...@redhat.com
---
migration.c | 5 +++--
qemu-file.h | 2 +-
savevm.c| 4 ++--
3 files changed, 6 insertions(+), 5 deletions(-)
diff --git a/migration.c b/migration.c
index 6a505c1..2c29d04 100644
--- a/migration.c
+++ b/migration.c
@@ -285,10 +285,11 @@
We only used it once, just remove the callback indirection.
Signed-off-by: Juan Quintela quint...@redhat.com
---
buffered_file.c | 5 +
buffered_file.h | 2 --
migration.c | 4 +---
migration.h | 1 +
4 files changed, 3 insertions(+), 9 deletions(-)
diff --git a/buffered_file.c
It has no users, and is only half implemented.
Signed-off-by: Juan Quintela quint...@redhat.com
---
qemu-file.h | 1 -
savevm.c| 21 -
2 files changed, 22 deletions(-)
diff --git a/qemu-file.h b/qemu-file.h
index d8487cd..7fe7274 100644
--- a/qemu-file.h
+++
It was unused out of savevm.c.
Signed-off-by: Juan Quintela quint...@redhat.com
---
qemu-file.h | 3 ---
savevm.c| 2 +-
2 files changed, 1 insertion(+), 4 deletions(-)
diff --git a/qemu-file.h b/qemu-file.h
index 7fe7274..289849a 100644
--- a/qemu-file.h
+++ b/qemu-file.h
@@ -230,7 +230,4
Signed-off-by: Juan Quintela quint...@redhat.com
---
qemu-file.h | 1 -
savevm.c| 2 +-
2 files changed, 1 insertion(+), 2 deletions(-)
diff --git a/qemu-file.h b/qemu-file.h
index 289849a..8dd9207 100644
--- a/qemu-file.h
+++ b/qemu-file.h
@@ -103,7 +103,6 @@ int
It is not used outside of savevm.c
Signed-off-by: Juan Quintela quint...@redhat.com
---
qemu-file.h | 1 -
savevm.c| 2 +-
2 files changed, 1 insertion(+), 2 deletions(-)
diff --git a/qemu-file.h b/qemu-file.h
index 31b83f6..d8487cd 100644
--- a/qemu-file.h
+++ b/qemu-file.h
@@ -71,7 +71,6
On Fri, Sep 21, 2012 at 10:13:33AM +0100, Richard Davies wrote:
Hi Mel,
Thank you for this series. I have applied on clean 3.6-rc5 and tested, and
it works well for me - the lock contention is (still) gone and
isolate_freepages_block is much reduced.
Excellent!
Here is a typical test
It always have that type, just change it.
Signed-off-by: Juan Quintela quint...@redhat.com
---
buffered_file.c | 6 +++---
buffered_file.h | 4 +++-
2 files changed, 6 insertions(+), 4 deletions(-)
diff --git a/buffered_file.c b/buffered_file.c
index 33b700b..59d952d 100644
---
It was used only one, and was only one if. It makes error handling
saner.
Signed-off-by: Juan Quintela quint...@redhat.com
---
savevm.c | 26 ++
1 file changed, 6 insertions(+), 20 deletions(-)
diff --git a/savevm.c b/savevm.c
index 0953695..8efa7cc 100644
---
From: Paolo Bonzini pbonz...@redhat.com
Simplify the logic for pushing data from the buffer to the output
pipe/socket. This also matches more closely what will be the
operation of the migration thread.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
Signed-off-by: Juan Quintela
It indicates how many pages were dirtied during the last second.
Signed-off-by: Juan Quintela quint...@redhat.com
---
arch_init.c | 18 ++
hmp.c| 4
migration.c | 2 ++
migration.h | 1 +
qapi-schema.json | 8 ++--
5 files changed, 31
Signed-off-by: Juan Quintela quint...@redhat.com
---
migration.c | 2 +-
migration.h | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/migration.c b/migration.c
index c1655b3..2827663 100644
--- a/migration.c
+++ b/migration.c
@@ -53,7 +53,7 @@ static NotifierList
Signed-off-by: Juan Quintela quint...@redhat.com
---
migration.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/migration.c b/migration.c
index 1edeec5..1e3f791 100644
--- a/migration.c
+++ b/migration.c
@@ -327,6 +327,7 @@ static void migrate_fd_put_ready(void *opaque)
Mel Gorman wrote:
I did manage to get a couple which were slightly worse, but nothing like as
bad as before. Here are the results:
# grep -F '[k]' report | head -8
45.60% qemu-kvm [kernel.kallsyms] [k] clear_page_c
11.26% qemu-kvm [kernel.kallsyms] [k]
qemu_fseek() is known to be wrong. Would be removed on the next
commit. This code should never been used (value has been
MAC_TABLE_ENTRIES since 2009).
Signed-off-by: Juan Quintela quint...@redhat.com
---
hw/virtio-net.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
Signed-off-by: Juan Quintela quint...@redhat.com
---
arch_init.c | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/arch_init.c b/arch_init.c
index cdd8ab7..013e5e5 100644
--- a/arch_init.c
+++ b/arch_init.c
@@ -539,7 +539,7 @@ static int
Signed-off-by: Juan Quintela quint...@redhat.com
---
buffered_file.c | 5 ++---
buffered_file.h | 3 +--
migration.c | 2 +-
3 files changed, 4 insertions(+), 6 deletions(-)
diff --git a/buffered_file.c b/buffered_file.c
index 4fca774..43e68b6 100644
--- a/buffered_file.c
+++
It just marks a region of memory as dirty.
Signed-off-by: Juan Quintela quint...@redhat.com
---
arch_init.c | 20 +---
1 file changed, 13 insertions(+), 7 deletions(-)
diff --git a/arch_init.c b/arch_init.c
index 57f7f1a..b2dcc24 100644
--- a/arch_init.c
+++ b/arch_init.c
@@
Signed-off-by: Juan Quintela quint...@redhat.com
---
arch_init.c | 2 ++
hmp.c| 4
migration.c | 2 ++
migration.h | 1 +
qapi-schema.json | 5 +
qmp-commands.hx | 6 ++
6 files changed, 20 insertions(+)
diff --git a/arch_init.c b/arch_init.c
index
On Fri, Sep 21, 2012 at 10:17:01AM +0100, Richard Davies wrote:
Richard Davies wrote:
I did manage to get a couple which were slightly worse, but nothing like as
bad as before. Here are the results:
# grep -F '[k]' report | head -8
45.60% qemu-kvm [kernel.kallsyms] [k]
We only used it once, just remove the callback indirection.
Signed-off-by: Juan Quintela quint...@redhat.com
---
buffered_file.c | 7 ++-
buffered_file.h | 5 +
migration.c | 8 ++--
migration.h | 1 +
4 files changed, 6 insertions(+), 15 deletions(-)
diff --git
Helper that we use each time that we need to syncronize the migration
bitmap with the other dirty bitmaps.
Signed-off-by: Juan Quintela quint...@redhat.com
---
arch_init.c | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/arch_init.c b/arch_init.c
index
We only used it once, just remove the callback indirection
Signed-off-by: Juan Quintela quint...@redhat.com
---
buffered_file.c | 7 ++-
buffered_file.h | 2 --
migration.c | 6 ++
migration.h | 3 +++
4 files changed, 7 insertions(+), 11 deletions(-)
diff --git
We only use it once, just remove the callback indirection.
Signed-off-by: Juan Quintela quint...@redhat.com
---
buffered_file.c | 5 +
buffered_file.h | 2 --
migration.c | 4 +---
migration.h | 1 +
4 files changed, 3 insertions(+), 9 deletions(-)
diff --git a/buffered_file.c
Old code used !io_thread to know if a thread was an vcpu or not. That
fails when we introduce the iothread.
Signed-off-by: Juan Quintela quint...@redhat.com
---
cpus.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/cpus.c b/cpus.c
index e476a3c..1b7061a 100644
---
Am 20.09.2012 21:13, schrieb Jeff Cody:
Move AIO initialization for raw-posix block driver into a helper function.
In addition to just code motion, the aio_ctx pointer is checked for NULL,
prior to calling laio_init(), to make sure laio_init() is only run once.
Signed-off-by: Jeff Cody
Callers on savevm.c:qemu_fflush() will set it.
Signed-off-by: Juan Quintela quint...@redhat.com
---
buffered_file.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/buffered_file.c b/buffered_file.c
index 6d9a50b..318d0f0 100644
--- a/buffered_file.c
+++ b/buffered_file.c
@@ -120,8 +120,6 @@
Signed-off-by: Juan Quintela quint...@redhat.com
---
buffered_file.c | 10 +-
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/buffered_file.c b/buffered_file.c
index f170aa0..4148abb 100644
--- a/buffered_file.c
+++ b/buffered_file.c
@@ -50,20 +50,12 @@ static void
Make consistent the result of blk_mig_save_dirty_block() and
mig_save_device_dirty()
Signed-off-by: Juan Quintela quint...@redhat.com
---
block-migration.c | 14 +-
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/block-migration.c b/block-migration.c
index
This patch creates a migration bitmap, which is periodically kept in
sync with the qemu bitmap. A separate copy of the dirty bitmap for the
migration limits the amount of concurrent access to the qemu bitmap
from iothread and migration thread (which requires taking the big
lock).
We use the qemu
Move the error check to the beggining of the callers. Once this is fixed
qemu_file_set_if_error() is not used anymore, so remove it.
Signed-off-by: Juan Quintela quint...@redhat.com
---
savevm.c | 35 ++-
1 file changed, 18 insertions(+), 17 deletions(-)
diff
It just test if the dirty bit is set, and clears it.
Signed-off-by: Juan Quintela quint...@redhat.com
---
arch_init.c | 19 ++-
1 file changed, 14 insertions(+), 5 deletions(-)
diff --git a/arch_init.c b/arch_init.c
index b2dcc24..acc057f 100644
--- a/arch_init.c
+++
Adjust all the callers. We moved the set of last_error from inside
qemu_fflush() to all the callers.
Signed-off-by: Juan Quintela quint...@redhat.com
---
savevm.c | 39 +++
1 file changed, 23 insertions(+), 16 deletions(-)
diff --git a/savevm.c b/savevm.c
Is the only way of knowing the RAM size.
Signed-off-by: Juan Quintela quint...@redhat.com
---
cpu-all.h | 2 ++
exec.c| 2 +-
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/cpu-all.h b/cpu-all.h
index 74d3681..5408782 100644
--- a/cpu-all.h
+++ b/cpu-all.h
@@ -517,6 +517,8 @@
Signed-off-by: Juan Quintela quint...@redhat.com
---
buffered_file.c | 7 ---
1 file changed, 7 deletions(-)
diff --git a/buffered_file.c b/buffered_file.c
index 43e68b6..747d672 100644
--- a/buffered_file.c
+++ b/buffered_file.c
@@ -61,13 +61,6 @@ static void
Signed-off-by: Juan Quintela quint...@redhat.com
---
buffered_file.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/buffered_file.c b/buffered_file.c
index 7155800..33b700b 100644
--- a/buffered_file.c
+++ b/buffered_file.c
@@ -27,7 +27,7 @@ typedef struct
03:07:27 +0400)
are available in the git repository at:
http://repo.or.cz/r/qemu/quintela.git migration-next-20120921
for you to fetch changes up to 4bce0b88b10ed790ad3669ce4ff61c945cd655eb:
cpus: create qemu_cpu_is_vcpu() (2012-09-21 10:43:10 +0200)
Juan Quintela (40):
buffered_file
Signed-off-by: Juan Quintela quint...@redhat.com
---
arch_init.c | 12 +---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/arch_init.c b/arch_init.c
index 52ccc7b..57f7f1a 100644
--- a/arch_init.c
+++ b/arch_init.c
@@ -482,6 +482,14 @@ static void ram_migration_cancel(void
Signed-off-by: Juan Quintela quint...@redhat.com
---
hmp.c| 4
migration.c | 6 +-
migration.h | 1 +
qapi-schema.json | 7 ++-
qmp-commands.hx | 3 +++
5 files changed, 19 insertions(+), 2 deletions(-)
diff --git a/hmp.c b/hmp.c
index ba6fbd3..40b0c05 100644
On Mon, Sep 17, 2012 at 08:28:52AM -0700, Richard Henderson wrote:
Commit 6375e09e changed the type of TranslationBlock.tb_next,
but failed to change the type of TCGContext.tb_next.
Signed-off-by: Richard Henderson r...@twiddle.net
---
tcg/tcg.h | 2 +-
1 file changed, 1 insertion(+), 1
Am 20.09.2012 21:13, schrieb Jeff Cody:
These patches are based off Supriya Kannery's original bdrv_reopen()
patches as part of the hostcache series.
This provides support for safe reopen of a single image, or transactional
reopening of multiple images atomically.
These changes are all
This reverts
mm-compaction-abort-compaction-loop-if-lock-is-contended-or-run-too-long-fix
as it is replaced by a later patch in the series.
Signed-off-by: Mel Gorman mgor...@suse.de
---
mm/compaction.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/mm/compaction.c
From: Shaohua Li s...@fusionio.com
Changelog since V2
o Fix BUG_ON triggered due to pages left on cc.migratepages
o Make compact_zone_order() require non-NULL arg `contended'
Changelog since V1
o only abort the compaction if lock is contended or run too long
o Rearranged the code by Andrea
On Fri, 21 Sep 2012, Gerd Hoffmann wrote:
On 09/20/12 17:33, Stefano Stabellini wrote:
On Thu, 20 Sep 2012, Stefano Stabellini wrote:
On Thu, 20 Sep 2012, Gerd Hoffmann wrote:
Hi,
In any graphics mode relevant today vga emulation will use
qemu_create_displaysurface_from(). Whenever
When compaction was implemented it was known that scanning could potentially
be excessive. The ideal was that a counter be maintained for each pageblock
but maintaining this information would incur a severe penalty due to a
shared writable cache line. It has reached the point where the scanning
Define SSDT hotplug-able memory devices in _SB namespace. The dynamically
generated SSDT includes per memory device hotplug methods. These methods
just call methods defined in the DSDT. Also dynamically generate a MTFY
method and a MEON array of the online/available memory devices. ACPI
Example:
-dimm id=dimm0,size=512M,node=0,populated=off
will define a 512M memory slot belonging to numa node 0.
When populated=on, a DimmDevice is created and hot-plugged at system startup.
Signed-off-by: Vasilis Liaskovitis vasilis.liaskovi...@profitbricks.com
---
hw/Makefile.objs |2 +-
This reverts
mm-compaction-abort-compaction-loop-if-lock-is-contended-or-run-too-long.patch
as it is replaced by a later patch in the series.
Signed-off-by: Mel Gorman mgor...@suse.de
---
mm/compaction.c | 12 +---
mm/internal.h |2 +-
2 files changed, 6 insertions(+), 8
pcimem_start and pcimem64_start are adjusted from srat entries. For this reason,
paravirt info (NUMA SRAT entries and number of cpus) need to be read before
pci_setup.
Imho, this is an ugly code change since SRAT bios tables and number of
cpus have to be read earlier. But the advantage is that no
This allows qemu to receive notifications from the guest OS on success or
failure of a memory hotplug request. The guest OS needs to implement the _OST
functionality for this to work (linux-next: http://lkml.org/lkml/2012/6/25/321)
This patch also updates dimm bitmap state and hot-remove pending
query-balloon and info balloon should report total memory available to the
guest.
balloon inflate/ deflate can also use all memory available to the guest (initial
+ hotplugged memory)
Ballon driver has been minimaly tested with the patch, please review and test.
Caveat: if the guest does not
Add support for _OST method. _OST method will write into the correct I/O byte to
signal success / failure of hot-add or hot-remove to qemu.
Signed-off-by: Vasilis Liaskovitis vasilis.liaskovi...@profitbricks.com
---
src/acpi-dsdt.dsl | 50 ++
in case of hot-remove failure on a guest that does not implement _OST,
the dimm bitmaps in qemu and Seabios show the dimm as unplugged, but the dimm
is still present on the qdev/memory bus. To avoid this inconsistency, we set the
dimm state to active/hot-plugged on a reset of the associated
This is almost entirely based on Rik's previous patches and discussions
with him about how this might be implemented.
Order 0 compaction stops when enough free pages of the correct page
order have been coalesced. When doing subsequent higher order allocations,
it is possible for compaction to
Am 20.09.2012 23:00, schrieb Eduardo Otubo:
Seccomp syscall whitelist updated after tests running qemu under
libvirt. Reference to the bug -
https://bugzilla.redhat.com/show_bug.cgi?id=855162
Regards,
---
qemu-seccomp.c | 21 -
1 file changed, 20 insertions(+), 1
A 32-byte register is used to present up to 256 hotplug-able memory devices
to BIOS and OSPM. Hot-add and hot-remove functions trigger an ACPI hotplug
event through these. Only reads are allowed from these registers.
An ACPI hot-remove event but needs to wait for OSPM to eject the device.
We use
This reverts
mm-compaction-check-lock-contention-first-before-taking-lock.patch as it
is replaced by a later patch in the series.
Signed-off-by: Mel Gorman mgor...@suse.de
---
mm/compaction.c |5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/mm/compaction.c
Compactions migrate scanner acquires the zone-lru_lock when scanning a range
of pages looking for LRU pages to acquire. It does this even if there are
no LRU pages in the range. If multiple processes are compacting then this
can cause severe locking contention. To make matters worse commit
Live migration works after memory hot-add events, as long as the
qemu command line -dimm arguments are changed on the destination host
to specify populated=on for the dimms that have been hot-added.
If a command-line change has not occured, the destination host does not yet
have the corresponding
Signed-off-by: Vasilis Liaskovitis vasilis.liaskovi...@profitbricks.com
---
src/acpi-dsdt.dsl | 15 +++
src/ssdt-mem.dsl |4
2 files changed, 19 insertions(+), 0 deletions(-)
diff --git a/src/acpi-dsdt.dsl b/src/acpi-dsdt.dsl
index 0d37bbc..8a18770 100644
---
The memory device generation is guided by qemu paravirt info. Seabios
first uses the info to setup SRAT entries for the hotplug-able memory slots.
Afterwards, build_memssdt uses the created SRAT entries to generate
appropriate memory device objects. One memory device (and corresponding SRAT
entry)
Qemu already calculates the 32-bit and 64-bit PCI starting offsets based on
initial memory and hotplug-able dimms. This info needs to be passed to Seabios
for PCI initialization.
Signed-off-by: Vasilis Liaskovitis vasilis.liaskovi...@profitbricks.com
---
docs/specs/fwcfg.txt |9 +
Each hotplug-able memory slot is a DimmDevice. All DimmDevices are attached
to a new bus called DimmBus. This bus is introduced so that we no longer
depend on hotplug-capability of main system bus (the main bus does not allow
hotplugging). The DimmBus should be attached to a chipset Device (i440fx
This will allow us to update dimm state on OSPM-initiated eject operations e.g.
with echo 1 /sys/bus/acpi/devices/PNP0C80\:00/eject
Signed-off-by: Vasilis Liaskovitis vasilis.liaskovi...@profitbricks.com
---
docs/specs/acpi_hotplug.txt |7 +++
hw/acpi_piix4.c |5 +
Guest can respond to ACPI hotplug events e.g. with _EJ or _OST method.
This patch implements a tail queue to store guest notifications for memory
hot-add and hot-remove requests.
Guest responses for memory hotplug command on a per-dimm basis can be detected
with the new hmp command info memhp or
On 2012-09-18 11:41, Hans de Goede wrote:
Hi,
On 09/17/2012 06:22 PM, Jan Kiszka wrote:
If that does not work, add the debug parameter to the usb-redir device,
set it
to 4, collect logs of trying to redirect the device and send me the logs
please, ie:
-device
This allows to extract the beginning, end and name of a Device object.
Signed-off-by: Vasilis Liaskovitis vasilis.liaskovi...@profitbricks.com
---
tools/acpi_extract.py | 28
1 files changed, 28 insertions(+), 0 deletions(-)
diff --git a/tools/acpi_extract.py
Hi Andrew,
Richard Davies and Shaohua Li have both reported lock contention
problems in compaction on the zone and LRU locks as well as
significant amounts of time being spent in compaction. This series
aims to reduce lock contention and scanning rates to reduce that CPU
usage. Richard reported
The numa_fw_cfg paravirt interface is extended to include SRAT information for
all hotplug-able dimms. There are 3 words for each hotplug-able memory slot,
denoting start address, size and node proximity. The new info is appended after
existing numa info, so that the fw_cfg layout does not break.
This reverts commit 7db8889a (mm: have order 0 compaction start off
where it left) and commit de74f1cc (mm: have order 0 compaction start
near a pageblock with free pages). These patches were a good idea and
tests confirmed that they massively reduced the amount of scanning but
the
Compactions free scanner acquires the zone-lock when checking for PageBuddy
pages and isolating them. It does this even if there are no PageBuddy pages
in the range.
This patch defers acquiring the zone lock for as long as possible. In the
event there are no free pages in the pageblock then the
Extend the DSDT to include methods for handling memory hot-add and hot-remove
notifications and memory device status requests. These functions are called
from the memory device SSDT methods.
Signed-off-by: Vasilis Liaskovitis vasilis.liaskovi...@profitbricks.com
---
src/acpi-dsdt.dsl | 70
Returns total physical memory available to guest in bytes, including hotplugged
memory. Note that the number reported here may be different from what the guest
sees e.g. if the guest has not logically onlined hotplugged memory.
This functionality is provided independently of a balloon device,
Initialize the 32-bit and 64-bit pci starting offsets from values passed in by
the qemu paravirt interface QEMU_CFG_PCI_WINDOW. Qemu calculates the starting
offsets based on initial memory and hotplug-able dimms.
Signed-off-by: Vasilis Liaskovitis vasilis.liaskovi...@profitbricks.com
---
Dimm physical address offsets are calculated automatically and memory map is
adjusted accordingly. If a DIMM can fit before the PCI_HOLE_START (currently
0xe000), it will be added normally, otherwise its physical address will be
above 4GB.
Also create memory bus on i440fx-pcihost device.
This is v3 of the ACPI memory hotplug functionality. Only x86_64 target is
supported
for now.
Overview:
Dimm device layout is modeled with a new qemu command line
-dimm id=name,size=sz,node=pxm,populated=on|off
The starting physical address for all dimms is calculated automatically from
top
Il 21/09/2012 10:46, Juan Quintela ha scritto:
Signed-off-by: Juan Quintela quint...@redhat.com
---
buffered_file.c | 10 +-
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/buffered_file.c b/buffered_file.c
index f170aa0..4148abb 100644
--- a/buffered_file.c
+++
On 09/21/2012 04:43 AM, Paolo Bonzini wrote:
Il 21/09/2012 10:33, Kevin Wolf ha scritto:
+/* could not reopen the file handle, so fall back to opening
+ * new file (CreateFile) */
+if (raw_s-hfile == INVALID_HANDLE_VALUE) {
+raw_s-hfile = CreateFile(state-bs-filename,
1 - 100 of 401 matches
Mail list logo
