On 2017/4/20 17:09, Dr. David Alan Gilbert wrote:
* Hailiang Zhang (zhang.zhanghaili...@huawei.com) wrote:
On 2017/4/8 1:18, Dr. David Alan Gilbert wrote:
* zhanghailiang (zhang.zhanghaili...@huawei.com) wrote:
There are several stages during loadvm/savevm process. In different stage,
migratio
Currently, qemu-img 'amend' subcommand would fail to adjust image's backing file
which was moved into different path.
For example, parent.qcow2, the backing file of leaf.qcow2, first is at /home/a/,
then moved into /home/b/. Originally this command,
"qemu-img amend -f qcow2 -o
backing_fmt=qcow2,b
Hi all,
As a non-native English speaker,
I sincerely hope you give me more suggestions about English
style and/or grammar for the spec.
Thanks in advance!
-Gonglei
> -Original Message-
> From: Gonglei (Arei)
> Sent: Thursday, April 13, 2017 5:11 PM
> To: qemu-devel@nongnu.org; virtio-
Kevin Wolf writes:
> Am 20.04.2017 um 17:30 hat Daniel P. Berrange geschrieben:
>> On Thu, Apr 20, 2017 at 12:00:03PM +0800, Fam Zheng wrote:
>> > Signed-off-by: Fam Zheng
>> > ---
>> > block/sheepdog.c | 1 +
>> > 1 file changed, 1 insertion(+)
>> >
>> > diff --git a/block/sheepdog.c b/block/
From: Laurent Vivier
cannot_destroy_with_object_finalize_yet was added by 4c315c2
("qdev: Protect device-list-properties against broken devices")
because "realview_pci" and "versatile_pci" were hanging
during "device-list-properties" cleanup (an infinite loop in
bus_unparent()).
We have this pro
Laurent Vivier writes:
> This series removes all the remaining uses of
> cannot_destroy_with_object_finalize_yet to finally remove
> the flag itself.
>
> The ARM patch has already been sent alone and reviewed by Markus.
> I have tested the ppc one on ppc64 machine with KVM and using
> QDM device-
From: Laurent Vivier
This removes the assert(kvm_enabled()) from kvmppc_host_cpu_initfn()
This assert can never be triggered as the function is only registered
when KVM is available (see also 4c315c2
"qdev: Protect device-list-properties against broken devices").
So we can remove the cannot_des
The following changes since commit 359c41abe32638adad503e386969fa428cecff52:
Update version for v2.9.0 release (2017-04-20 15:31:34 +0100)
are available in the git repository at:
git://repo.or.cz/qemu/armbru.git tags/pull-qdev-2017-04-21
for you to fetch changes up to 08f00df4f4b8b4e38ad620
From: Laurent Vivier
As all users have been removed, we can remove
cannot_destroy_with_object_finalize_yet field
from the DeviceClass structure.
Signed-off-by: Laurent Vivier
Message-Id: <20170414083717.13641-5-lviv...@redhat.com>
Reviewed-by: Markus Armbruster
Acked-by: Peter Maydell
Signed-
From: Laurent Vivier
With commit ce5b1bbf624b ("exec: move cpu_exec_init() calls to
realize functions"), we can now remove all the
remaining cannot_destroy_with_object_finalize_yet as
unsafe references have been moved to cpu_exec_realizefn().
(tested with QOM command provided by commit 4c315c27).
On Fri, Apr 21, 2017 at 10:58 AM, 858585 jemmy wrote:
> On Thu, Apr 20, 2017 at 6:00 PM, Kevin Wolf wrote:
>> Am 20.04.2017 um 10:38 hat jemmy858...@gmail.com geschrieben:
>>> From: Lidong Chen
>>>
>>> when the buffer is zero, blk_co_pwrite_zeroes is more effectively than
>>> blk_co_pwritev with
(I forgot to reply all in last email, so I resend the reply again)
I have resubmitted two split-out patches in https://lists.nongnu.org/
archive/html/qemu-devel/2017-04/msg03096.html, which change the exit
funtion of sclp and virtio-ccw. But the exit function of DeviceClass still
returns int after
Hi Tao,
On 04/20/2017 04:36 PM, Tao Wu wrote:
This bug was introduced by https://github.com/qemu/qemu/commit/98c6305
Nice catch...
In 98c6305 Guillaume probably missed parentheses :S
- mss = min(IF_MTU, IF_MRU) - sizeof(struct tcpiphdr);
+ mss = min(IF_MTU, IF_MRU) - sizeof(struct tcphdr) + s
On 2017年04月21日 11:48, Zhang Chen wrote:
On 04/20/2017 02:43 PM, Jason Wang wrote:
On 2017年04月18日 10:20, Zhang Chen wrote:
In this patch we support packet that have tcp options field.
Add tcp options field check, If the packet have options
field we just skip it and compare tcp payload,
Avo
Signed-off-by: Fam Zheng
---
tests/qemu-iotests/153 | 219
tests/qemu-iotests/153.out | 627 +
tests/qemu-iotests/group | 1 +
3 files changed, 847 insertions(+)
create mode 100755 tests/qemu-iotests/153
create mode 100644 tes
Making this option available even before implementing it will let
converting tests easier: in coming patches they can specify the option
already when necessary, before we actually write code to lock the
images.
Signed-off-by: Fam Zheng
---
block/file-posix.c | 5 +
1 file changed, 5 insertio
Signed-off-by: Fam Zheng
---
blockdev.c | 15 ++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/blockdev.c b/blockdev.c
index 4927914..4e04dec 100644
--- a/blockdev.c
+++ b/blockdev.c
@@ -3174,6 +3174,7 @@ static BlockJob *do_drive_backup(DriveBackup *backup,
BlockJob
Signed-off-by: Fam Zheng
Reviewed-by: Max Reitz
---
tests/qemu-iotests/091 | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tests/qemu-iotests/091 b/tests/qemu-iotests/091
index 32bbd56..10ac4a8 100755
--- a/tests/qemu-iotests/091
+++ b/tests/qemu-iotests/091
@@ -95,7 +95,9 @@ echo "vm2: qe
Signed-off-by: Fam Zheng
Reviewed-by: Max Reitz
---
tests/drive_del-test.c| 2 +-
tests/nvme-test.c | 2 +-
tests/usb-hcd-uhci-test.c | 2 +-
tests/usb-hcd-xhci-test.c | 2 +-
tests/virtio-blk-test.c | 2 +-
tests/virtio-scsi-test.c | 4 ++--
6 files changed, 7 insertions(+), 7 de
They are wrappers of POSIX fcntl "file private locking", with a
convenient "try lock" wrapper implemented with F_OFD_GETLK.
Signed-off-by: Fam Zheng
Reviewed-by: Max Reitz
---
include/qemu/osdep.h | 3 +++
util/osdep.c | 48
2 files chan
Double attach is not a valid usage of the target image, drive-backup
will open the blockdev itself so skip the add_drive call in this case.
Signed-off-by: Fam Zheng
Reviewed-by: Max Reitz
---
tests/qemu-iotests/055 | 32 ++--
1 file changed, 18 insertions(+), 14 dele
virtlockd in libvirt locks the first byte, so we start looking at the
file bytes from 0x10.
The complication is in the transactional interface. To make the reopen
logic managable, and allow better reuse, the code is internally
organized with a table from old mode to the new one.
Signed-off-by: F
The test scenario doesn't require the same image, instead it focuses on
the duplicated node-name, so use null-co to avoid locking conflict.
Reviewed-by: Max Reitz
Signed-off-by: Fam Zheng
---
tests/qemu-iotests/087 | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/tests/
To avoid image lock failures.
Signed-off-by: Fam Zheng
---
tests/qemu-iotests/172 | 55 +-
tests/qemu-iotests/172.out | 50 +
2 files changed, 56 insertions(+), 49 deletions(-)
diff --git a/tests/qemu-iotest
The COLO block replication architecture requires one disk to be shared
between primary and secondary, in the test both processes use posix file
protocol (instead of over NBD) so it is affected by image locking.
Disable the lock.
Signed-off-by: Fam Zheng
---
tests/test-replication.c | 9 +++--
In the case where we test the expected error when a blockdev-snapshot
target already has a backing image, the backing chain is opened multiple
times. This will be a problem when we use image locking, so use a
different backing file that is not already open.
Signed-off-by: Fam Zheng
---
tests/qem
Similar to share-rw qdev property, this will force the opened images to
allow shared write permission of other programs.
Signed-off-by: Fam Zheng
---
qemu-img.c | 155 +++--
1 file changed, 119 insertions(+), 36 deletions(-)
diff --git a/q
Signed-off-by: Fam Zheng
---
qemu-img-cmds.hx | 48
1 file changed, 24 insertions(+), 24 deletions(-)
diff --git a/qemu-img-cmds.hx b/qemu-img-cmds.hx
index 8ac7822..1b00bb8 100644
--- a/qemu-img-cmds.hx
+++ b/qemu-img-cmds.hx
@@ -10,15 +10,15 @@
qemu-img and qemu-io commands when guest is running need "-U" option,
add it.
Signed-off-by: Fam Zheng
---
tests/qemu-iotests/030 | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/tests/qemu-iotests/030 b/tests/qemu-iotests/030
index 0d472d5..5f1dce8
The qemu-img info command is executed while VM is running, add -U option
to avoid the image locking error.
Signed-off-by: Fam Zheng
---
tests/qemu-iotests/046 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/qemu-iotests/046 b/tests/qemu-iotests/046
index e528b67..f2ebec
Signed-off-by: Fam Zheng
---
block.c | 31 +++
1 file changed, 23 insertions(+), 8 deletions(-)
diff --git a/block.c b/block.c
index f5c4e97..6acf618 100644
--- a/block.c
+++ b/block.c
@@ -1422,6 +1422,21 @@ static int bdrv_child_check_perm(BdrvChild *c, uint64_t
per
Add --share-rw/-U to program options and -U to open subcommand.
Signed-off-by: Fam Zheng
---
qemu-io.c | 35 +++
1 file changed, 27 insertions(+), 8 deletions(-)
diff --git a/qemu-io.c b/qemu-io.c
index 427cbae..c4d824f 100644
--- a/qemu-io.c
+++ b/qemu-io.c
@@ -
Signed-off-by: Fam Zheng
---
qapi/block-core.json | 3 +++
1 file changed, 3 insertions(+)
diff --git a/qapi/block-core.json b/qapi/block-core.json
index 033457c..b9b8002 100644
--- a/qapi/block-core.json
+++ b/qapi/block-core.json
@@ -2880,6 +2880,8 @@
# (default: false)
# @de
Signed-off-by: Fam Zheng
---
block.c | 9 +
include/block/block.h | 2 ++
include/block/block_int.h | 1 +
3 files changed, 12 insertions(+)
diff --git a/block.c b/block.c
index 1e668fb..f5c4e97 100644
--- a/block.c
+++ b/block.c
@@ -763,6 +763,7 @@ static void bdrv
v14: - Replace BDRV_ flag with the "force-shared-write" block option. [Kevin]
- Add bs->force_shared_write.
- Update test case accordingly, back to bash again. :)
- A few fixes in the locking code spotted by patchew and the new test,
though the long line error is still there f
On 04/20/2017 02:43 PM, Jason Wang wrote:
On 2017年04月18日 10:20, Zhang Chen wrote:
In this patch we support packet that have tcp options field.
Add tcp options field check, If the packet have options
field we just skip it and compare tcp payload,
Avoid unnecessary checkpoint, optimize perform
I recently left Freescale/NXP, and even before that it'd been a few years
since I was actively involved in KVM/QEMU work.
Signed-off-by: Scott Wood
---
Sorry for the resend -- fixed mailing list address.
MAINTAINERS | 3 ---
1 file changed, 3 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
While debugging an issue, I ran across something in the initialization
sequence of hardware accelerators. Being a noobie qemu developer, it's
hard to tell if I simply don't understand how AccelClass works or if
this is a bug.
The init_machine function for hardware accelerators is passed a
MachineS
On Thu, Apr 20, 2017 at 6:00 PM, Kevin Wolf wrote:
> Am 20.04.2017 um 10:38 hat jemmy858...@gmail.com geschrieben:
>> From: Lidong Chen
>>
>> when the buffer is zero, blk_co_pwrite_zeroes is more effectively than
>> blk_co_pwritev with BDRV_REQ_WRITE_COMPRESSED. this patch can reduces
>> the time
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20170420202745.149601-1-lep...@google.com
Subject: [Qemu-devel] [PATCH] Fix wrong length in IP header in tcp_respond.
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=base
n=1
tot
On Tue, Apr 18, 2017 at 01:09:50PM +1000, David Gibson wrote:
> On Fri, Apr 14, 2017 at 10:37:15AM +0200, Laurent Vivier wrote:
> > This removes the assert(kvm_enabled()) from kvmppc_host_cpu_initfn()
> >
> > This assert can never be triggered as the function is only registered
> > when KVM is ava
On Thu, Apr 20, 2017 at 05:59:27PM +0200, Markus Armbruster wrote:
> Peter Maydell writes:
>
> > On 14 April 2017 at 09:37, Laurent Vivier wrote:
> >> This series removes all the remaining uses of
> >> cannot_destroy_with_object_finalize_yet to finally remove
> >> the flag itself.
> >>
> >> The
The current code looks buggy, we zero ti_i while we access
ti_dst/ti_src later.
Signed-off-by: Tao Wu
---
slirp/tcp_subr.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/slirp/tcp_subr.c b/slirp/tcp_subr.c
index dc8b4bbb50..398d6b30d3 100644
--- a/slirp/tcp_subr.c
+++ b/slirp/tcp_subr.c
@@ -
This bug was introduced by https://github.com/qemu/qemu/commit/98c6305
And then we 'fix' it in
https://github.com/qemu/qemu/commit/27d92e
Actually I believe the root cause was that we sent out a RST packet with
wrong length and then get ignored by OS.
Signed-off-by: Tao Wu
---
slirp/tcp_subr.c |
I sent it several hours ago and they don't show at
http://lists.gnu.org/archive/html/qemu-devel/2017-04/index.html
Is there some kind of spam filter in this list? I sent those patches with
git send-email
This bug was introduced by https://github.com/qemu/qemu/commit/98c6305
Signed-off-by: Tao Wu
---
slirp/tcp_input.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/slirp/tcp_input.c b/slirp/tcp_input.c
index edb98f06f3..07bcbdb2dd 100644
--- a/slirp/tcp_input.c
+++ b/slirp
Hi Daniel,
2.9 was released, so...ping
Thanks.
On 2017/4/17 9:33, Longpeng(Mike) wrote:
> The AF_ALG socket family is the userspace interface for linux
> crypto API, users can use it to access hardware accelerators.
>
> This patchset adds a afalg-backend for qemu crypto subsystem. Currently
>
On Thu, Apr 20, 2017 at 10:43:46PM +0200, BALATON Zoltan wrote:
> This is not used by default on any emulated machine yet but it is
> still useful to have it compiled so it can be added from the command
> line for clients that can use it (e.g. MorphOS has no driver for any
> other emulated video ca
On Thu, 04/20 22:15, Kevin Wolf wrote:
> We test for the presence of perl and bc and save their path in the
> variables PERL_PROG and BC_PROG, but never actually make use of them.
> Remove the checks and assignments so qemu-iotests can run even when
> bc isn't installed.
>
> Reported-by: Yash Mank
On Thu, 04/20 22:32, Kevin Wolf wrote:
> Am 20.04.2017 um 17:30 hat Daniel P. Berrange geschrieben:
> > On Thu, Apr 20, 2017 at 12:00:03PM +0800, Fam Zheng wrote:
> > > Signed-off-by: Fam Zheng
> > > ---
> > > block/sheepdog.c | 1 +
> > > 1 file changed, 1 insertion(+)
> > >
> > > diff --git a/
Hi everyone,
A security update to the QEMU 2.8 series is now available at:
http://wiki.qemu.org/download/qemu-2.8.1.1.tar.xz
http://wiki.qemu.org/download/qemu-2.8.1.1.tar.xz.sig
v2.8.1.1 is now tagged in the official qemu.git repository,
and the stable-2.8 branch has been updated accordingl
On Thu, Apr 20, 2017 at 12:05 PM, Eric Blake wrote:
> On 04/20/2017 11:18 AM, Markus Armbruster wrote:
>> Eric Blake writes:
>>
>>> On 04/20/2017 06:59 AM, Markus Armbruster wrote:
>>>
No objection to Alistair's idea to turn this into an enumeration.
>>>
>>> Question - should the enum b
On 20 April 2017 at 21:43, BALATON Zoltan wrote:
> We only emulate the sysbus device in its default LE mode and PCI is LE
> as well so specify this for registers and framebuffer memory.
>
> Signed-off-by: BALATON Zoltan
> ---
I think it's worth a comment to the effect of:
Note that though the L
On 04/20/2017 04:03 PM, Chris Friesen wrote:
> Hi,
>
> Suppose the host has a physical disk that only supports 4KB access, with
> no 512B fallback.
>
> If we boot a guest with "cache=none", does the guest need to be able to
> handle disks with 4KB blocks or is qemu able to handle guests trying to
Hi,
Suppose the host has a physical disk that only supports 4KB access, with no 512B
fallback.
If we boot a guest with "cache=none", does the guest need to be able to handle
disks with 4KB blocks or is qemu able to handle guests trying to access the disk
with 512B granularity?
Also, does t
Rework HWC handling to simplify it and fix cursor not updating on
screen as needed. Previously cursor was not updated because checking
for changes in a line overrode the update flag set for the cursor but
fixing this is not enough because the cursor should also be updated if
its shape or location c
Signed-off-by: BALATON Zoltan
Reviewed-by: Peter Maydell
---
hw/display/sm501.c | 1132 ++-
hw/display/sm501_template.h | 52 +-
2 files changed, 594 insertions(+), 590 deletions(-)
diff --git a/hw/display/sm501.c b/hw/display/sm501.c
index 040
This is to allow clients to initialise these without failing as long
as no 2D engine function is called that would use the written value.
Saved values are not used yet (may get used when more of 2D engine is
added sometimes) and clients normally only write to most of these
registers, nothing is kno
Signed-off-by: BALATON Zoltan
Reviewed-by: Peter Maydell
---
v3: Added local_mem_size_index to vmstate, add vmstate for sysbus version too
hw/display/sm501.c | 100 -
1 file changed, 99 insertions(+), 1 deletion(-)
diff --git a/hw/display/sm
Only the display controller part is created automatically on PCI
Signed-off-by: BALATON Zoltan
Reviewed-by: Peter Maydell
---
v2: Split off removing dependency on base address to separate patch
v3: Added reset function and PCI ID constant definitions in pci_ids.h
v4: Return error for invalid VR
Signed-off-by: BALATON Zoltan
Reviewed-by: Peter Maydell
---
hw/display/sm501.c | 8
1 file changed, 8 insertions(+)
diff --git a/hw/display/sm501.c b/hw/display/sm501.c
index 6b72964..6e74200 100644
--- a/hw/display/sm501.c
+++ b/hw/display/sm501.c
@@ -474,6 +474,7 @@ typedef struct S
Do not use the base address to access data in local memory. This is in
preparation to allow chip connected via PCI where base address depends
on where the BAR is mapped so it will be unknown.
Signed-off-by: BALATON Zoltan
Reviewed-by: Peter Maydell
---
hw/display/sm501.c | 6 ++
hw
Adding vmstate saving is not in this patch because the state structure
will be changed in further patches, then another patch will add
vmstate descriptor after those changes.
Signed-off-by: BALATON Zoltan
Reviewed-by: Peter Maydell
---
v2: Add memory regions to device state instead of allocatin
- Rename a variable
- Move variable declarations out of loop to the beginning in draw_hwc_line
Signed-off-by: BALATON Zoltan
Reviewed-by: Peter Maydell
---
hw/display/sm501.c | 10 +-
hw/display/sm501_template.h | 10 --
2 files changed, 9 insertions(+), 11 deletions(-)
Signed-off-by: BALATON Zoltan
Reviewed-by: Peter Maydell
---
v2: Split off renaming a variable to separate clean up patch
hw/display/sm501.c | 63 +++---
1 file changed, 32 insertions(+), 31 deletions(-)
diff --git a/hw/display/sm501.c b/hw/disp
Signed-off-by: BALATON Zoltan
Reviewed-by: Peter Maydell
---
v3: Fix initial value of misc_control register as Peter Maydell suggested
Also use M_BYTE constant from cutils.h
hw/display/sm501.c | 29 +++--
hw/display/sm501_template.h | 2 +-
2 files changed
Addressing all last review comments so hopefully this can get merged
now that tree is thawed.
BALATON Zoltan (13):
sm501: Fixed code style and a few typos in comments
sm501: Use defined constants instead of literal values where available
sm501: Add missing arbitration control register
sm50
We only emulate the sysbus device in its default LE mode and PCI is LE
as well so specify this for registers and framebuffer memory.
Signed-off-by: BALATON Zoltan
---
v2: Split off small clean up to other patch
v4: Set serial part to little endian as well
v5: Make framebuffer always LE as sugges
This is not used by default on any emulated machine yet but it is
still useful to have it compiled so it can be added from the command
line for clients that can use it (e.g. MorphOS has no driver for any
other emulated video cards but can output via SM501)
Signed-off-by: BALATON Zoltan
---
v5: A
On Thu, Apr 20, 2017 at 10:32:50PM +0200, Kevin Wolf wrote:
> Am 20.04.2017 um 17:30 hat Daniel P. Berrange geschrieben:
> > On Thu, Apr 20, 2017 at 12:00:03PM +0800, Fam Zheng wrote:
> > > Signed-off-by: Fam Zheng
> > > ---
> > > block/sheepdog.c | 1 +
> > > 1 file changed, 1 insertion(+)
> > >
Am 20.04.2017 um 17:30 hat Daniel P. Berrange geschrieben:
> On Thu, Apr 20, 2017 at 12:00:03PM +0800, Fam Zheng wrote:
> > Signed-off-by: Fam Zheng
> > ---
> > block/sheepdog.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/block/sheepdog.c b/block/sheepdog.c
> > index fb9203e..
On 04/19/2017 05:22 PM, Eric Blake wrote:
> Libvirt would like to be able to distinguish between a SHUTDOWN
> event triggered solely by guest request and one triggered by a
> SIGTERM or other action on the host. qemu_kill_report() is
> already able to tell whether a shutdown was triggered by a hos
On 04/20/2017 03:15 PM, Kevin Wolf wrote:
> We test for the presence of perl and bc and save their path in the
> variables PERL_PROG and BC_PROG, but never actually make use of them.
> Remove the checks and assignments so qemu-iotests can run even when
> bc isn't installed.
>
> Reported-by: Yash M
We test for the presence of perl and bc and save their path in the
variables PERL_PROG and BC_PROG, but never actually make use of them.
Remove the checks and assignments so qemu-iotests can run even when
bc isn't installed.
Reported-by: Yash Mankad
Signed-off-by: Kevin Wolf
---
tests/qemu-iote
Am 20.04.2017 um 16:08 hat Peter Lieven geschrieben:
> Am 20.04.2017 um 16:05 schrieb Fam Zheng:
> >On Tue, 02/28 14:35, Peter Lieven wrote:
> >>img_convert has been around before there was an ImgConvertState or
> >>a block backend, but it has never been modified to directly use
> >>these structs.
On Tue, Apr 11, 2017 at 7:56 AM, Dan Williams wrote:
> [ adding Christoph ]
>
> On Tue, Apr 11, 2017 at 1:41 AM, Haozhong Zhang
> wrote:
>> On 04/06/17 20:02 +0800, Xiao Guangrong wrote:
>>>
>>>
>>> On 04/06/2017 05:43 PM, Stefan Hajnoczi wrote:
>>> > On Fri, Mar 31, 2017 at 04:41:43PM +0800, Hao
On 04/20/2017 11:18 AM, Markus Armbruster wrote:
> Eric Blake writes:
>
>> On 04/20/2017 06:59 AM, Markus Armbruster wrote:
>>
>>>
>>> No objection to Alistair's idea to turn this into an enumeration.
>>
>> Question - should the enum be more than just 'guest' and 'host'? For
>> example, my patch
From: Krzysztof Kozlowski
Inside qdev_prop_set_drive() the value returned by blk_bs() is passed
only as pointer to const to bdrv_get_node_name() and pointed values is
not modified in other places so this can be made const for code
safeness.
Signed-off-by: Krzysztof Kozlowski
Message-Id: <201703
From: Peter Xu
Use the new interface to boost readability.
Signed-off-by: Peter Xu
Message-Id: <1489151370-15453-3-git-send-email-pet...@redhat.com>
Reviewed-by: Eduardo Habkost
Signed-off-by: Eduardo Habkost
---
backends/hostmem-file.c | 6 +++---
backends/hostmem.c | 10 +-
2
From: Thomas Huth
If the user currently tries to use the -kernel parameter, simply nothing
happens, and the user might get confused that there is nothing loaded
to memory, but also no error message has been issued. Since there is no
real generic way to load a kernel on all CPU types (but on some
The "hotplugged" property is user visible, but it was never meant
to be set by the user. There are probably multiple ways to break
or crash device code by overriding the property. For example, we
recently fixed a crash in rtc_set_memory() related to the
property (commit 26ef65beab852caf2b1ef4976e34
* Laurent Vivier (lviv...@redhat.com) wrote:
> If we close the QEMUFile descriptor in process_incoming_migration_co()
> while it has been stopped by an error, the postcopy_ram_listen_thread()
> can try to continue to use it. And as the memory has been freed
> it is working with an invalid pointer a
From: Krzysztof Kozlowski
The 'value' argument is not modified so this can be made const for code
safeness.
Signed-off-by: Krzysztof Kozlowski
Message-Id: <20170310200550.13313-2-k...@kernel.org>
Signed-off-by: Eduardo Habkost
---
include/hw/qdev-properties.h | 3 ++-
hw/core/qdev-properties.
From: Peter Xu
This patch is based on Aviv Ben-David ()'s patch
upstream:
"IOMMU: enable intel_iommu map and unmap notifiers"
https://lists.gnu.org/archive/html/qemu-devel/2016-11/msg01453.html
However I removed/fixed some content, and added my own codes.
Instead of translate() every page
From: Peter Xu
Originally we have one memory_region_iommu_replay() function, which is
the default behavior to replay the translations of the whole IOMMU
region. However, on some platform like x86, we may want our own replay
logic for IOMMU regions. This patch adds one more hook for IOMMUOps for
t
From: Peter Xu
We were checking this against memory region size of host memory
backend's mr field to see whether the mr has been inited. This is
efficient but less elegant. Let's make a helper for it to avoid
confusions, along with some notes.
Suggested-by: Peter Maydell
Signed-off-by: Peter Xu
From: Peter Xu
This is preparation work to finally enabled dynamic switching ON/OFF for
VT-d protection. The old VT-d codes is using static IOMMU address space,
and that won't satisfy vfio-pci device listeners.
Let me explain.
vfio-pci devices depend on the memory region listener and IOMMU repl
From: Peter Xu
The default replay() don't work for VT-d since vt-d will have a huge
default memory region which covers address range 0-(2^64-1). This will
normally consumes a lot of time (which looks like a dead loop).
The solution is simple - we don't walk over all the regions. Instead, we
jump
From: Peter Xu
A new macro is provided to iterate all the IOMMU notifiers hooked
under specific IOMMU memory region.
Reviewed-by: David Gibson
Reviewed-by: Eric Auger
Reviewed-by: \"Michael S. Tsirkin\"
Signed-off-by: Peter Xu
Message-Id: <1491562755-23867-3-git-send-email-pet...@redhat.com>
From: Peter Xu
This is an "global" version of existing memory_region_iommu_replay() -
we announce the translations to all the registered notifiers, instead of
a specific one.
Reviewed-by: David Gibson
Reviewed-by: \"Michael S. Tsirkin\"
Signed-off-by: Peter Xu
Message-Id: <1491562755-23867-4-
From: Peter Xu
In this patch, IOMMUNotifier.{start|end} are introduced to store section
information for a specific notifier. When notification occurs, we not
only check the notification type (MAP|UNMAP), but also check whether the
notified iova range overlaps with the range of specific IOMMU noti
From: Peter Xu
Generalizing the notify logic in memory_region_notify_iommu() into a
single function. This can be further used in customized replay()
functions for IOMMUs.
Reviewed-by: David Gibson
Reviewed-by: Eric Auger
Reviewed-by: \"Michael S. Tsirkin\"
Signed-off-by: Peter Xu
Message-Id:
From: Jason Wang
We have a specific memory region for DMAR now, so it's wrong to
trigger the notifier with the root region.
Cc: Michael S. Tsirkin
Cc: Paolo Bonzini
Cc: Richard Henderson
Cc: Eduardo Habkost
Signed-off-by: Jason Wang
Reviewed-by: Peter Xu
Reviewed-by: \"Michael S. Tsirkin\"
This includes a few IOMMU fixes because Michael is away this
week.
The following changes since commit da92ada855036c55bd08b0b0c64c7551d56f3586:
Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20170420'
into staging (2017-04-20 17:41:34 +0100)
are available
On Thu, Apr 20, 2017 at 12:14:18AM -0400, Pranith Kumar wrote:
> On Wed, Apr 19, 2017 at 10:26 PM, Eduardo Habkost wrote:
> > On Wed, Apr 19, 2017 at 06:03:01PM -0400, Pranith Kumar wrote:
> >> On Wed, Apr 19, 2017 at 5:33 PM, Eduardo Habkost
> >> wrote:
> >> > On Wed, Apr 19, 2017 at 05:25:23PM
On 04/20/2017 11:12 AM, Markus Armbruster wrote:
>>> Well technically /usr/sbin/halt just terminates all processes / kernel and
>>> halts CPUs, but the virtual machine is still active (and a 'reset' in the
>>> monitor can start it again. /usr/sbin/poweroff is what actually does the
>>> ACPI powero
On Thu, 20 Apr 2017, Paul Durrant wrote:
> > -Original Message-
> > From: Stefano Stabellini [mailto:sstabell...@kernel.org]
> > Sent: 20 April 2017 00:02
> > To: Paul Durrant
> > Cc: 'Stefano Stabellini' ; qemu-devel@nongnu.org;
> > Anthony Perard ; Wei Liu
> > ; jgr...@suse.com; julien.g
lable in the git repository at:
>
> git://git.linaro.org/people/pmaydell/qemu-arm.git
> tags/pull-target-arm-20170420
>
> for you to fetch changes up to f4e8e4edda875cab9df91dc4ae9767f7cb1f50aa:
>
> arm: Remove workarounds for old M-profile exception
On M profile, return from exceptions happen when code in Handler mode
executes one of the following function call return instructions:
* POP or LDM which loads the PC
* LDR to PC
* BX register
and the new PC value is 0xFFxx.
QEMU tries to implement this by not treating the instruction
speci
Now that we've rewritten M-profile exception return so that the magic
PC values are not visible to other parts of QEMU, we can delete the
special casing of them elsewhere.
Signed-off-by: Peter Maydell
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Richard Henderson
Message-id: 1491844419-1248
1 - 100 of 273 matches
Mail list logo
