On 07/09/15 00:42, Bandan Das wrote:
>
> If a Linux guest is assigned more memory than is supported
> by the host processor, the guest is unable to boot. That
> is expected, however, there's no message indicating the user
> what went wrong. This change prints a message to stderr if
> KVM has the c
On 08/07/2015 22:48, Peter Maydell wrote:
> On 8 July 2015 at 12:19, Paolo Bonzini wrote:
>> The following changes since commit f6e3035f75e5c6a73485335765ae070304c7a110:
>>
>> Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream-smm' into
>> staging (2015-07-06 23:37:53 +0100)
>>
>
On Thu, Jul 09, 2015 at 12:00:59AM +0200, Maxime Leroy wrote:
> Hi Michael,
>
> On Wed, Jul 8, 2015 at 4:29 PM, Michael S. Tsirkin wrote:
> > On Thu, May 28, 2015 at 09:23:06AM +0800, Ouyang Changchun wrote:
> >> Based on patch by Nikolay Nikolaev:
> >> Vhost-user will implement the multi queue s
This is a revival of a patch set I posted in 2013. At the time
Paolo had some comments on the keystone patch, and I didn't have
time to address them. I've since made several revisions, and I
think the patchset is in good shape, but I've lost those original
comments.
Anyway, I'm reviving this now
Add forgotten zero-extension in the TARGET_X86_64, !CODE64, ss32 case;
use this new function to implement gen_string_movl_A0_EDI,
gen_string_movl_A0_ESI, gen_add_A0_ds_seg.
Signed-off-by: Richard Henderson
---
target-i386/translate.c | 160
1 file
Centralize handling of segment bases.
Signed-off-by: Richard Henderson
---
target-i386/translate.c | 82 ++---
1 file changed, 23 insertions(+), 59 deletions(-)
diff --git a/target-i386/translate.c b/target-i386/translate.c
index a900508..d85e800 1006
Use gen_lea_v_seg for centralized segment base knowledge. Unify
code across 32- and 64-bit. Fix note about "must save state"
before using the out-of-line helpers.
Signed-off-by: Richard Henderson
---
target-i386/helper.h | 4 ---
target-i386/seg_helper.c | 68 -
Centralize computation of a MO_SIZE for the stack pointer.
Signed-off-by: Richard Henderson
---
target-i386/translate.c | 24 ++--
1 file changed, 10 insertions(+), 14 deletions(-)
diff --git a/target-i386/translate.c b/target-i386/translate.c
index 2c6c5ec..a900508 100644
-
Having segs[].base as a register significantly improves code
generation for real and protected modes, particularly for TBs
that have multiple memory references where the segment base
can be held in a hard register through the TB.
Reviewed-by: Peter Maydell
Signed-off-by: Richard Henderson
---
t
I.e. gen_push_v, gen_pop_T0, gen_stack_A0.
More centralization of handling of segment bases.
Signed-off-by: Richard Henderson
---
target-i386/translate.c | 52 +
1 file changed, 13 insertions(+), 39 deletions(-)
diff --git a/target-i386/translate.
More centralization of handling of segment bases.
Also fixes the note about 16-bit wrap around not fully handled.
Signed-off-by: Richard Henderson
---
target-i386/translate.c | 50 +++--
1 file changed, 23 insertions(+), 27 deletions(-)
diff --git a/t
Unify the code across stack pointer widths. Fix the note about
not updating ESP before the potential exception.
Signed-off-by: Richard Henderson
---
target-i386/translate.c | 29 +++--
1 file changed, 15 insertions(+), 14 deletions(-)
diff --git a/target-i386/translate.
Merge gen_op_addl_A0_im and gen_op_addq_A0_im into gen_add_A0_im
and clean up the ifdef.
Replace the one remaining user of gen_op_addl_A0_im with gen_add_A0_im.
Reviewed-by: Peter Maydell
Signed-off-by: Richard Henderson
---
target-i386/translate.c | 27 +--
1 file chan
All references to cpu_T are done with a constant index. It aids
readability to decompose the array into two scalar variables.
Reviewed-by: Peter Maydell
Signed-off-by: Richard Henderson
---
target-i386/translate.c | 1254 ---
1 file changed, 644 inse
On Thu, Jul 09, 2015 at 01:29:48AM +, Ouyang, Changchun wrote:
>
>
> > -Original Message-
> > From: snabb-de...@googlegroups.com [mailto:snabb-
> > de...@googlegroups.com] On Behalf Of Maxime Leroy
> > Sent: Thursday, July 9, 2015 6:01 AM
> > To: Michael S. Tsirkin
> > Cc: Ouyang, Cha
On Wed, Jul 08, 2015 at 01:44:55PM +0800, Yi Min Zhao wrote:
> @@ -588,9 +606,172 @@ static const TypeInfo s390_pcihost_info = {
> }
> };
>
> +static void s390_pci_device_hot_plug(HotplugHandler *hotplug_dev,
> + DeviceState *dev, Error **errp)
> +{
> +
On 09/07/2015 00:42, Bandan Das wrote:
>
> If a Linux guest is assigned more memory than is supported
> by the host processor, the guest is unable to boot. That
> is expected, however, there's no message indicating the user
> what went wrong. This change prints a message to stderr if
> KVM has t
On 09/07/2015 03:19, Wen Congyang wrote:
> Yes, why migration doesn't trigger this problem? We will fix it soon.
This should be the fix if someone wants to test it and/or post it:
diff --git a/migration/ram.c b/migration/ram.c
index 57368e1..8d5a73a 100644
--- a/migration/ram.c
+++ b/migration/
* Juan Quintela (quint...@redhat.com) wrote:
> "Dr. David Alan Gilbert" wrote:
> > * Juan Quintela (quint...@redhat.com) wrote:
> >> "Dr. David Alan Gilbert (git)" wrote:
> >> > From: "Dr. David Alan Gilbert"
> >> >
> >> > My e4d633207 patch has an over zealous sanity check that checked
> >> > t
On 07/09/2015 03:59 PM, Paolo Bonzini wrote:
>
>
> On 09/07/2015 03:19, Wen Congyang wrote:
>> Yes, why migration doesn't trigger this problem? We will fix it soon.
>
> This should be the fix if someone wants to test it and/or post it:
>
> diff --git a/migration/ram.c b/migration/ram.c
> index
On 08/07/2015 16:22, Paolo Bonzini wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
>
>
> On 08/07/2015 17:03, James Hogan wrote:
>> Hi Paolo,
>>
>> On 24/04/15 11:26, James Hogan wrote:
>>> A couple of small fixes for accessing 32-bit KVM registers on
>>> big endian, and to sign ext
We will be able to reuse these pieces for XSAVE/XRSTOR.
Signed-off-by: Richard Henderson
---
target-i386/fpu_helper.c | 145 ---
target-i386/helper.h | 4 +-
target-i386/translate.c | 4 +-
3 files changed, 90 insertions(+), 63 deletions(-)
d
Rather than nesting tests of OP, MOD, and RM, decode them
all at once with a switch. Fixes incorrect decoding of
AMD Pacifica extensions (aka vmrun et al) via op==2 path.
Signed-off-by: Richard Henderson
---
target-i386/translate.c | 470 +---
1 file
This includes XSAVE, XRSTOR, XGETBV, XSETBV, which are all related,
as well as the associate cpuid bits.
Signed-off-by: Richard Henderson
---
target-i386/cpu.c| 39 +--
target-i386/cpu.h| 2 +
target-i386/fpu_helper.c | 123 +
This is immediately usable by lea and multi-byte nop,
and will be required to implement parts of the mpx spec.
Signed-off-by: Richard Henderson
---
target-i386/translate.c | 199 +---
1 file changed, 85 insertions(+), 114 deletions(-)
diff --git a/tar
I'm still in the process of testing this, as there's no code
written for it yet and hardware to compare against doesn't
start shipping until (probably) August.
But in the meantime there are a number of holes that I found
in XSAVE support that might affect KVM, and one question wrt
SMM support that
Signed-off-by: Richard Henderson
---
target-i386/translate.c | 54 -
1 file changed, 53 insertions(+), 1 deletion(-)
diff --git a/target-i386/translate.c b/target-i386/translate.c
index ada0dec..69bb6c6 100644
--- a/target-i386/translate.c
+++ b/ta
Note the cpu.c change -- don't advertise more XSAVE features
than we implement.
Signed-off-by: Richard Henderson
---
target-i386/cpu.c| 2 +-
target-i386/fpu_helper.c | 28 +++-
target-i386/helper.h | 1 +
target-i386/translate.c | 27 ++
Signed-off-by: Richard Henderson
---
target-i386/helper.h | 4 +++
target-i386/mpx_helper.c | 93
target-i386/translate.c | 61 +++
3 files changed, 158 insertions(+)
diff --git a/target-i386/helper.h b/target-i38
Signed-off-by: Richard Henderson
---
target-i386/helper.h | 2 ++
target-i386/mpx_helper.c | 8
target-i386/translate.c | 46 +-
3 files changed, 55 insertions(+), 1 deletion(-)
diff --git a/target-i386/helper.h b/target-i386/helper.h
i
Enable and disable at CPL changes, MSR changes, and XRSTOR changes.
Signed-off-by: Richard Henderson
---
target-i386/Makefile.objs | 2 +-
target-i386/cpu.c | 18 +--
target-i386/cpu.h | 21 -
target-i386/fpu_helper.c | 78 +++
Signed-off-by: Richard Henderson
---
target-i386/translate.c | 73 -
1 file changed, 72 insertions(+), 1 deletion(-)
diff --git a/target-i386/translate.c b/target-i386/translate.c
index 69bb6c6..fcafa81 100644
--- a/target-i386/translate.c
+++ b/ta
Signed-off-by: Richard Henderson
---
target-i386/cpu.c | 22 --
1 file changed, 20 insertions(+), 2 deletions(-)
diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index c19ff8a..2402c2a 100644
--- a/target-i386/cpu.c
+++ b/target-i386/cpu.c
@@ -2654,7 +2654,17 @@ static void
With helpers that can be reused for other things.
Signed-off-by: Richard Henderson
---
target-i386/cc_helper.c | 10 --
target-i386/helper.h| 2 --
target-i386/translate.c | 37 -
3 files changed, 28 insertions(+), 21 deletions(-)
diff --git a/ta
Signed-off-by: Richard Henderson
---
target-i386/mem_helper.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/target-i386/mem_helper.c b/target-i386/mem_helper.c
index 1aec8a5..c8d5fac 100644
--- a/target-i386/mem_helper.c
+++ b/target-i386/mem_helper.c
@@ -91,6 +91,9 @@ void helper_bou
Signed-off-by: Richard Henderson
---
target-i386/translate.c | 25 +
1 file changed, 25 insertions(+)
diff --git a/target-i386/translate.c b/target-i386/translate.c
index 7892951..f067d98 100644
--- a/target-i386/translate.c
+++ b/target-i386/translate.c
@@ -2410,6 +2410,
On Wed, 8 Jul 2015 22:39:24 +0200
Paolo Bonzini wrote:
>
>
> On 08/07/2015 21:26, Igor Mammedov wrote:
> > > This was suggested by Michael, so I think you should read the reviews
> > > of earlier versions first.
> >
> > That is basically the same as hooks in v1 only the other way around
> > wi
On 07/09/15 09:59, Paolo Bonzini wrote:
>
>
> On 09/07/2015 00:42, Bandan Das wrote:
>>
>> If a Linux guest is assigned more memory than is supported
>> by the host processor, the guest is unable to boot. That
>> is expected, however, there's no message indicating the user
>> what went wrong. Thi
from commit 2ff6403, we make a mistake to call synchronize_rcu()
within rcu_read_lock()/rcu_read_unlock()
Signed-off-by: Li Zhijian
Signed-off-by: Wen Congyang
Signed-off-by: Li Zhijian
---
migration/ram.c | 49 -
1 file changed, 32 insertions(+)
On Wed, Jul 08, 2015 at 04:29:49PM +0300, Emil Condrea wrote:
> On Mon, Jul 6, 2015 at 6:11 PM, Stefan Hajnoczi wrote:
>
> > On Sun, Jul 5, 2015 at 7:15 AM, Emil Condrea
> > wrote:
> > > Stefan, do you know if this patch was applied?
> >
> > It hasn't been applied, sorry. It slipped through the
On Wed, Jul 08, 2015 at 05:37:12PM +0300, Michael S. Tsirkin wrote:
> On Thu, Jul 02, 2015 at 09:21:21AM +0800, Fam Zheng wrote:
> > On Wed, 07/01 22:45, Naredula Janardhana Reddy wrote:
> > > HI,
> > > I am trying to improve the throughput of virtio-blk for my kernel (
> > > https://github.c
* Wen Congyang (we...@cn.fujitsu.com) wrote:
> >> I have sent the v8. But the usage is not changed. You can setup the
> >> environment according to the wiki.
> >> When we open nbd client, we need to connect to the nbd server. So I
> >> introduce a new command child_add to add NBD client
> >> as
Commit 3972ef6f830d ("tcg: Push merged memop+mmu_idx parameter to
softmmu routines") caused the following build errors when building TCG
for MIPS:
In file included from tcg/tcg.c:258:0:
tcg/mips/tcg-target.c In function ‘tcg_out_qemu_ld_slow_path’:
tcg/mips/tcg-target.c:1015:22: error: ‘lb’ undecl
The KVM_REG_MIPS_COUNT_* definitions are now included in
linux-headers/asm-mips/kvm.h since commit b061808d39fa ("linux-headers:
update linux headers to kvm/next"), therefore the duplicate definitions
in target-mips/kvm.c can now be dropped (the definitions were tweaked
slightly in commit 7a52ce8a1
These two patches fix build errors for the MIPS TCG backend and MIPS
KVM.
Please could they be applied for v2.4.
James Hogan (2):
tcg/mips: Fix build error from merged memop+mmu_idx parameter
mips/kvm: Sync with newer MIPS KVM headers
target-mips/kvm.c | 15 ++-
tcg/mips/tcg
On Tue, Jul 07, 2015 at 12:10:15PM +0300, Michael S. Tsirkin wrote:
> On Tue, Jul 07, 2015 at 04:58:29PM +0800, Jason Wang wrote:
> >
> >
> > On 07/07/2015 04:13 PM, Michael S. Tsirkin wrote:
> > > On Tue, Jul 07, 2015 at 09:21:07AM +0800, Fam Zheng wrote:
> > >> Since commit 6e99c63 "net/socket:
On Thu, 09 Jul 2015 09:02:38 +0200
Laszlo Ersek wrote:
> On 07/09/15 00:42, Bandan Das wrote:
> >
> > If a Linux guest is assigned more memory than is supported
> > by the host processor, the guest is unable to boot. That
> > is expected, however, there's no message indicating the user
> > what
The "chardev" property initialisation might failed (for example because
there is not enough chardev handled by Qemu).
The serial device emulator need to be able to "work" with an uninitialized
(NULL) "chardev" device pointer.
This patch add some test on the "chardev" pointer value before using it
On 7/9/2015 3:48 PM, Michael S. Tsirkin wrote:
On Wed, Jul 08, 2015 at 01:44:55PM +0800, Yi Min Zhao wrote:
@@ -588,9 +606,172 @@ static const TypeInfo s390_pcihost_info = {
}
};
+static void s390_pci_device_hot_plug(HotplugHandler *hotplug_dev,
+
On 07/09/2015 05:16 PM, Dr. David Alan Gilbert wrote:
> * Wen Congyang (we...@cn.fujitsu.com) wrote:
>
I have sent the v8. But the usage is not changed. You can setup the
environment according to the wiki.
When we open nbd client, we need to connect to the nbd server. So I
in
On 07/07/2015 19:33, Programmingkid wrote:
> Make physical devices like a USB flash drive or a CDROM drive work in
> QEMU. With
> this patch I can use a USB flash drive like a hard drive. Before this
> patch,
> QEMU would just quit with a message like "resource busy". Now it handles
> issues
> l
On Tue, Jul 07, 2015 at 05:00:56PM +0800, Jason Wang wrote:
> We should pass the size of packet instead of the remaining to
> qemu_send_packet_async().
>
> Fixes: 6e99c631f116221d169ea53953d91b8aa74d297a
>("net/socket: Drop net_socket_can_send")
>
> Signed-off-by: Jason Wang
> ---
> net
On Thu, Jul 09, 2015 at 06:39:02AM +0200, Peter Lieven wrote:
> Am 08.07.2015 um 17:30 schrieb Stefan Hajnoczi:
> >The maximum number of struct iovec elements depends on the
> >BlockDriverState. The raw-posix protocol has a maximum of IOV_MAX but
> >others could have different values.
> >
> >Inste
Add a function to query BlockLimits.max_iov.
Signed-off-by: Stefan Hajnoczi
---
block/block-backend.c | 5 +
include/sysemu/block-backend.h | 1 +
2 files changed, 6 insertions(+)
diff --git a/block/block-backend.c b/block/block-backend.c
index aee8a12..5108aec 100644
--- a/block/b
v2:
* Default to IOV_MAX instead of INT_MAX [Peter Lieven]
This series depends on "[PATCH] block/mirror: limit qiov to IOV_MAX elements".
IOV_MAX has been hardcoded in several places since preadv()/pwritev()/etc
refuse to take more iovecs per call. That's actually an implementation detail
of ra
Request merging must not result in a huge request that exceeds the
maximum number of iovec elements. Use BlockLimits.max_iov instead of
hardcoding IOV_MAX.
Signed-off-by: Stefan Hajnoczi
---
block/io.c| 3 ++-
hw/block/virtio-blk.c | 2 +-
2 files changed, 3 insertions(+), 2 deletio
The maximum number of struct iovec elements depends on the
BlockDriverState. The raw-posix and iSCSI protocols have a maximum of
IOV_MAX but others could have different values.
Cc: Peter Lieven
Suggested-by: Kevin Wolf
Signed-off-by: Stefan Hajnoczi
---
v2:
* Change default from INT_MAX to IO
On Thu, Jul 09, 2015 at 05:30:08PM +0800, zyimin wrote:
>
>
> On 7/9/2015 3:48 PM, Michael S. Tsirkin wrote:
> >On Wed, Jul 08, 2015 at 01:44:55PM +0800, Yi Min Zhao wrote:
> >>@@ -588,9 +606,172 @@ static const TypeInfo s390_pcihost_info = {
> >> }
> >> };
> >>+static void s390_pci_device_
Use blk_get_max_iov() instead of hardcoding IOV_MAX, which may not apply
to all BlockDrivers.
Signed-off-by: Stefan Hajnoczi
---
block/mirror.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/block/mirror.c b/block/mirror.c
index adde12b..74d475b 100644
--- a/block/mirr
On Tue, Jun 30, 2015 at 11:28:18AM -0700, Josh Durgin wrote:
> Ping
>
> On 06/10/2015 08:28 PM, Josh Durgin wrote:
> >Patches 1 and 2 are simple cleanups. 3 and 4 fix the precedence of
> >cache options and ceph settings. The cache option precedence in
> >particular is important due to the potentia
On Thu, 2015-07-09 at 12:35 +1000, Alexey Kardashevskiy wrote:
>
> > Does "all versions of POWER8" include things like POWER8E,
> > POWER8NVL
> > and "POWER8 DD1", as one of the variations is known in the kernel
> > source? Can we safely migrate guests eg. from a POWER8 v1.0 host to
> > a POWER8E
On 07/09/15 11:27, Igor Mammedov wrote:
> On Thu, 09 Jul 2015 09:02:38 +0200
> Laszlo Ersek wrote:
>
>> On 07/09/15 00:42, Bandan Das wrote:
>>>
>>> If a Linux guest is assigned more memory than is supported
>>> by the host processor, the guest is unable to boot. That
>>> is expected, however, th
On Wed, Jul 08, 2015 at 01:55:34PM +0200, Kevin Wolf wrote:
> Am 26.06.2015 um 11:57 hat Stefan Hajnoczi geschrieben:
> > On Thu, Jun 25, 2015 at 11:05:20AM -0400, Jeff Cody wrote:
> > > On Thu, Jun 25, 2015 at 03:28:35PM +0100, Stefan Hajnoczi wrote:
> > > > On Wed, Jun 24, 2015 at 03:54:27PM -040
Am 07.07.2015 um 16:12 schrieb Paolo Bonzini:
> From: "Daniel P. Berrange"
>
> Switch the qcow/qcow2 block driver over to use the generic cipher
> API, this allows it to use the pluggable AES implementations,
> instead of being hardcoded to use QEMU's built-in impl.
>
> Signed-off-by: Daniel P.
On Mon, Jun 29, 2015 at 04:56:26PM -0400, John Snow wrote:
> Minor cleanup.
>
> Signed-off-by: John Snow
> ---
> hw/ide/ahci.c | 2 +-
> hw/vfio/platform.c | 2 +-
> net/tap-linux.c| 4 ++--
> 3 files changed, 4 insertions(+), 4 deletions(-)
Reviewed-by: Stefan Hajnoczi
Laszlo Ersek
* Wen Congyang (we...@cn.fujitsu.com) wrote:
> On 07/09/2015 05:16 PM, Dr. David Alan Gilbert wrote:
> > * Wen Congyang (we...@cn.fujitsu.com) wrote:
> >
> I have sent the v8. But the usage is not changed. You can setup the
> environment according to the wiki.
> When we open nbd cl
On Tue, Jul 07, 2015 at 02:43:06PM +0300, Catalin Vasile wrote:
> My vhost module respects the format vhost-net uses:
>
> /* summary */
> mutex_lock(&vq->mutex);
> vhost_disable_notify();
> for (;;) {
> head = vhost_get_vq_desc();
>if (head == vq->num) {
> if (unlikely
I have managed to deal with it.
The thing is I was using one of the latest versions of qemu, but an
old Linux Kernel version of 3.12.
On Thu, Jul 9, 2015 at 1:43 PM, Stefan Hajnoczi wrote:
> On Tue, Jul 07, 2015 at 02:43:06PM +0300, Catalin Vasile wrote:
>> My vhost module respects the format vho
On Tue, Jul 07, 2015 at 01:33:23PM -0400, Programmingkid wrote:
> Make physical devices like a USB flash drive or a CDROM drive work in QEMU.
> With
> this patch I can use a USB flash drive like a hard drive. Before this patch,
> QEMU would just quit with a message like "resource busy".
The comm
Forgot some CCs (patch author and migration folks)
Am 09.07.2015 um 12:17 schrieb Christian Borntraeger:
> Am 07.07.2015 um 16:12 schrieb Paolo Bonzini:
>> From: "Daniel P. Berrange"
>>
>> Switch the qcow/qcow2 block driver over to use the generic cipher
>> API, this allows it to use the pluggab
On 07/09/2015 06:37 PM, Dr. David Alan Gilbert wrote:
> * Wen Congyang (we...@cn.fujitsu.com) wrote:
>> On 07/09/2015 05:16 PM, Dr. David Alan Gilbert wrote:
>>> * Wen Congyang (we...@cn.fujitsu.com) wrote:
>>>
>> I have sent the v8. But the usage is not changed. You can setup the
>> envir
64 bit props used 32 bit callbacks in two places, leading to broken
feature bits on virtio (example: got 0x310006d4 which is
obviously bogus). Fix this.
Fixes: fdba6d96 ("qdev: add 64bit properties")
Signed-off-by: Cornelia Huck
---
hw/core/qdev-properties.c| 2 +-
include/hw/qdev-pr
On Tue, Jul 07, 2015 at 10:50:59PM +0530, Naredula Janardhana Reddy wrote:
> How to enable MSIX for virtio-blk, this is to avoid extra use of
> VIRTIO_PCI_ISR port reads.
> This is for qemu 2.3.0 with virtio-blk-pci with x-data-plane is on.
I tried the following with QEMU 2.3.0:
qemu-system-x8
Am 09.07.2015 um 12:53 schrieb Christian Borntraeger:
> Forgot some CCs (patch author and migration folks)
>
>
> Am 09.07.2015 um 12:17 schrieb Christian Borntraeger:
>> Am 07.07.2015 um 16:12 schrieb Paolo Bonzini:
>>> From: "Daniel P. Berrange"
>>>
>>> Switch the qcow/qcow2 block driver over t
Am 09.07.2015 um 13:01 schrieb Cornelia Huck:
> 64 bit props used 32 bit callbacks in two places, leading to broken
> feature bits on virtio (example: got 0x310006d4 which is
> obviously bogus). Fix this.
>
> Fixes: fdba6d96 ("qdev: add 64bit properties")
> Signed-off-by: Cornelia Huck
T
Patch adds
- memory_region_init_hva_range()
- memory_region_add_subregion_to_hva()
- memory_region_find_hva_range()
API to allocate, map into and lookup reserved HVA MemoryRegion.
MemoryRegion with reserved HVA range will be used for
providing linear 1:1 HVA->GVA mapping for RAM MemoryRegion
it will allow to return atomically return RAMBlock's host
address range into continuos HVA area so that no hole
would appear in there.
also mark RAMBlock with RAM_PREALLOC flag so it won't be
umapped as conventional memory by
reclaim_ramblock()->qemu_anon_ram_free()
Signed-off-by: Igor Mammedov
QEMU asserts in vhost due to hitting vhost backend limit
on number of supported memory regions.
Describe all hotplugged memory as one continuos range
to vhost with linear 1:1 HVA->GPA mapping in backend.
Signed-off-by: Igor Mammedov
---
hw/virtio/vhost.c | 47 +++
It makes sure that all hotplugged memory will be put in
continuos HVA range allowing to use 1:1 GVA<->HVA mapping.
1:1 mapping will be used by vhost to reduce number of memory
ranges for hotplugged memory to a single range that covers
all hotpluggable memory address space.
Signed-off-by: Igor Mam
HVA remapped file backed RAMBlock shouldn't be freed
with munmap() as it will create a hole in HVA area
but file descriptor should be freed so it won't leak.
Rearrange code so that file descriptor is freed always
if it's been used and drop unnecessary munmap()
call/branch because qemu_anon_ram_fre
Changelog:
v3->v4:
* drop patch extending memory_region_subregion_add()
with error argument
* and add memory_region_add_subregion_to_hva() API instead
* add madvise(DONTNEED) when returning range to HVA container
v2->v3:
* fixed(work-arouned) unmapping issues,
now memory sub
memory_region_destructor_ram() -> qemu_ram_free()
calls reclaim_ramblock() which does:
if (!(block->flags & RAM_PREALLOC))
free_host_memory()
g_free(block)
while
memory_region_destructor_ram_from_ptr() -> qemu_ram_free_from_ptr()
calls g_free_rcu(block, rcu) results -> g_free(block
Although memory_region_del_subregion() removes MemoryRegion
from current address space, it's possible that it's still
in use/referenced until old address space view is destroyed.
That doesn't allow to unmap it from HVA region at the time
of memory_region_del_subregion().
As a solution track HVA map
Hi,
I have tested them, they works fine here (tested with source :raw on nfs, raw
on ext3, and ceph/rbd device).
Patch 3 give me a big boost with an empty 10GB source raw on ext3. (take some
seconds vs some minutes)
- Mail original -
De: "Fam Zheng"
À: "qemu-devel"
Cc: "Kevin Wolf"
On Thu, Jul 09, 2015 at 10:06:35AM +0300, Michael S. Tsirkin wrote:
On Thu, Jul 09, 2015 at 12:00:59AM +0200, Maxime Leroy wrote:
Hi Michael,
On Wed, Jul 8, 2015 at 4:29 PM, Michael S. Tsirkin wrote:
> On Thu, May 28, 2015 at 09:23:06AM +0800, Ouyang Changchun wrote:
>> Based on patch by Nikol
On 09/07/2015 10:17, James Hogan wrote:
> These two patches fix build errors for the MIPS TCG backend and MIPS
> KVM.
>
> Please could they be applied for v2.4.
>
> James Hogan (2):
> tcg/mips: Fix build error from merged memop+mmu_idx parameter
> mips/kvm: Sync with newer MIPS KVM headers
>
Hi Martin, Michael,
On Thu, Jul 9, 2015 at 2:00 PM, Martin Kletzander wrote:
> On Thu, Jul 09, 2015 at 10:06:35AM +0300, Michael S. Tsirkin wrote:
>>
>> On Thu, Jul 09, 2015 at 12:00:59AM +0200, Maxime Leroy wrote:
>>>
>>> Hi Michael,
>>>
>>> On Wed, Jul 8, 2015 at 4:29 PM, Michael S. Tsirkin
>>
Am 09.07.2015 um 08:36 schrieb Peter Crosthwaite:
> Hi All,
>
> So for my multi-arch work, one of the eventual requirements is to
> remove all #define TARGET_FOO from core code. I came across this in
> cpus.c/qmp_query_cpus():
>
> #if defined(TARGET_I386)
> X86CPU *x86_cpu = X86_CPU(cpu);
On Thu, Jul 09, 2015 at 02:24:51PM +0200, Maxime Leroy wrote:
Hi Martin, Michael,
On Thu, Jul 9, 2015 at 2:00 PM, Martin Kletzander wrote:
On Thu, Jul 09, 2015 at 10:06:35AM +0300, Michael S. Tsirkin wrote:
On Thu, Jul 09, 2015 at 12:00:59AM +0200, Maxime Leroy wrote:
Hi Michael,
On Wed,
On 09/07/2015 08:43, Laszlo Ersek wrote:
> On 07/09/15 08:09, Paolo Bonzini wrote:
>>
>>
>> On 09/07/2015 00:36, Bandan Das wrote:
>>> Let userspace inquire the maximum physical address width
>>> of the host processors; this can be used to identify maximum
>>> memory that can be assigned to the g
On Wed, 8 Jul 2015 12:31:40 +0200
Cornelia Huck wrote:
> On Wed, 8 Jul 2015 09:45:05 +0200
> Cornelia Huck wrote:
>
> > On Tue, 7 Jul 2015 14:11:18 -0700
> > Peter Crosthwaite wrote:
>
> > > Yes I see. I think it is a core code bug though and we want to avoid
> > > having to patch individual
On Wed, 08 Jul 2015 18:42:01 -0400
Bandan Das wrote:
>
> If a Linux guest is assigned more memory than is supported
> by the host processor, the guest is unable to boot. That
> is expected, however, there's no message indicating the user
> what went wrong. This change prints a message to stderr
On 09/07/2015 10:14, Wen Congyang wrote:
> > flush_compressed_data(f);
> > ram_control_after_iterate(f, RAM_CONTROL_FINISH);
> > -migration_end();
> > -
> > rcu_read_unlock();
> > +
> > +migration_end();
> > qemu_put_be64(f, RAM_SAVE_FLAG_EOS);
>
> Yes, this patch can
On Thu, Jul 09, 2015 at 02:24:51PM +0200, Maxime Leroy wrote:
> Hi Martin, Michael,
>
> On Thu, Jul 9, 2015 at 2:00 PM, Martin Kletzander wrote:
> > On Thu, Jul 09, 2015 at 10:06:35AM +0300, Michael S. Tsirkin wrote:
> >>
> >> On Thu, Jul 09, 2015 at 12:00:59AM +0200, Maxime Leroy wrote:
> >>>
>
On Thu, Jul 09, 2015 at 11:47:56AM +0800, Fam Zheng wrote:
> block_job_sleep_ns is called by block job coroutines to yield the
> execution to VCPU threads and monitor etc. It is pointless to sleep for
> 0 or a few nanoseconds, because that equals to a "yield + enter" with no
> intermission in betwe
On Thu, Jul 09, 2015 at 11:47:58AM +0800, Fam Zheng wrote:
> Limiting to sectors_per_chunk for each bdrv_is_allocated_above is slow,
> because the underlying protocol driver would issue much more queries
> than necessary. We should coalesce the query.
>
> Signed-off-by: Fam Zheng
> ---
> block/m
On Thu, Jul 09, 2015 at 11:47:57AM +0800, Fam Zheng wrote:
> Sleeping for 0 second may not be as effective as we want, use
> block_job_relax_cpu.
>
> Signed-off-by: Fam Zheng
> ---
> block/mirror.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Stefan Hajnoczi
pgpVTPfKr
On Thu, Jul 09, 2015 at 11:47:55AM +0800, Fam Zheng wrote:
> This supersedes:
>
> http://patchwork.ozlabs.org/patch/491415/
>
> and [1] which is currently in Jeff's tree.
>
> Although [1] fixed the QMP responsiveness, Alexandre DERUMIER reported that
> guest responsiveness still suffers when we
On 09/07/2015 10:26, Laszlo Ersek wrote:
>> >
>> > Perhaps KVM could simply hide memory above the limit (i.e. treat it as
>> > MMIO), and the BIOS could remove RAM above the limit from the e820
>> > memory map?
> I'd prefer to leave the guest firmware*s* out of this... :)
>
> E820 is a legacy B
On Thu, Jul 09, 2015 at 01:47:21PM +0200, Igor Mammedov wrote:
> QEMU asserts in vhost due to hitting vhost backend limit
> on number of supported memory regions.
>
> Describe all hotplugged memory as one continuos range
> to vhost with linear 1:1 HVA->GPA mapping in backend.
>
> Signed-off-by: I
1 - 100 of 246 matches
Mail list logo
