On 09/18/2018 08:54 PM, Peter Maydell wrote:
> On 31 August 2018 at 11:38, Cédric Le Goater wrote:
>> When doing calibration, the SPI clock rate in the CE0 Control Register
>> and the read delay cycles in the Read Timing Compensation Register are
>> replaced by bit[11:4] of the DMA Control Registe
No comment?
在 2018/9/4 下午5:15, Yi Min Zhao 写道:
Common function measurement block is used to report counters of
successfully issued pcilg/stg/stb and rpcit instructions. This patch
introduces a new struct ZpciFmb and schedules a timer callback to
copy fmb to the guest memory at a interval time w
On 09/18/2018 08:53 PM, Peter Maydell wrote:
> On 31 August 2018 at 11:38, Cédric Le Goater wrote:
>> The FMC controller on the Aspeed SoCs support DMA to access the flash
>> modules. It can operate in a normal mode, to copy to or from the flash
>> module mapping window, or in a checksum calculati
Hi,
On 09/19/2018 08:57 AM, Mark Cave-Ayland wrote:
On 18/09/2018 22:12, Mark Cave-Ayland wrote:
Roman, can you reproduce this locally at all? My setup is nothing
special, just Debian Stretch on amd64.
I've just realised that because this bug is still dependent upon queued
patches, it
would
Am 19.09.18 um 00:23 schrieb Halil Pasic:
>
>
> On 09/18/2018 06:59 PM, Tony Krowiak wrote:
>> I've discussed this with Halil -- Pierre is out until next week. We
>> are in agreement that while these changes are viable, they result in
>> a slightly more complicated implementation compared to prev
On 2018-09-19 09:08, Yi Min Zhao wrote:
> No comment?
Since the zPCI spec is not available to the public, it's quite hard to
give any valuable comments here... I'll try anyway...
> 在 2018/9/4 下午5:15, Yi Min Zhao 写道:
>> Common function measurement block is used to report counters of
>> successfull
>>
>> Apart from that, looks good to me.
>
> Let me summarize what I think you are suggesting.
>
> For KVM:
> 1. Get rid of KVM_S390_VM_CPU_FEAT_AP in KVM
> 2. Make AP instruction interception the default.
> 3. Provide the KVM_S390_VM_CRYPTO_ENABLE_APIE attribute in KVM if the
> AP instructio
** Changed in: qemu
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1486278
Title:
'info vnc' monitor command does not show websocket information
Status in QEMU:
** Changed in: qemu
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1502613
Title:
[Feature Request] Battery Status / Virtual Battery
Status in QEMU:
New
Bug
I think this has been fixed sometime in the past already. Or can you
still reproduce this problem with the latest version of QEMU?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
h
Recent clean-ups moved these tests directly to the check-qtest-y variable,
but this variable gets completely overwritten at the end of the Makefile by:
check-qtest-y=$(foreach TARGET,$(TARGETS), $(check-qtest-$(TARGET)-y))
So the endianness-, wdt_ib700- and the vmxnet3-test are currently not run
Public bug reported:
Host OS: Archlinux
Host Architecture: AMD64
Guest OS: FreeBSD-11.2 (x2) and Archlinux (x1)
Guest Architecture: AMD64
I have been using QEMU 2.x without issue for a number of years but since
updating to QEMU 3.0 my guests do not complete startup.
FreeBSD 11.2 guest failure sy
On Thu 06 Sep 2018 11:37:08 AM CEST, Alberto Garcia wrote:
> 'discard' is one of the basic BlockdevOptions available for all
> drivers, but it's not handled by bdrv_reopen_prepare() so any attempt
> to change it results in an error:
>
>(qemu) qemu-io virtio0 "reopen -o discard=on"
>Cannot
Hi Geert,
On 9/13/18 5:44 PM, Geert Uytterhoeven wrote:
> From: Auger Eric
>
> Up to now we have relied on the device type to identify a device tree
> node creation function. Since we would like the vfio-platform device to
> be instantiatable with different compatible strings we introduce the
s
Hi Geert,
On 9/13/18 5:44 PM, Geert Uytterhoeven wrote:
> Allow the instantation of generic dynamic vfio-platform devices again,
> without the need to create a new device-specific vfio type.
>
> This is more or less a partial revert of commit 6f2062b9758ebc64
> ("hw/arm/virt: Allow only supported
On 9/13/18 5:44 PM, Geert Uytterhoeven wrote:
> From: Auger Eric
>
> Up to now the vfio-platform device has been abstract and could not be
> instantiated. The integration of a new vfio platform device required
> creating a dummy derived device which only set the compatible string.
>
> Follow
On 9/19/18 10:58 AM, Thomas Huth wrote:
> Recent clean-ups moved these tests directly to the check-qtest-y variable,
> but this variable gets completely overwritten at the end of the Makefile by:
>
> check-qtest-y=$(foreach TARGET,$(TARGETS), $(check-qtest-$(TARGET)-y))
>
> So the endianness-, wd
On 9/18/18 8:26 PM, Maciej W. Rozycki wrote:
> Hi Fredrik,
>
>> I agree, that is important too. I will post an updated v5 soon. Another
>> alternative change is to define check_insn_opc_user_only as
>>
>> static inline void check_insn_opc_user_only(DisasContext *ctx, int flags)
>> {
>> #ifndef CON
Cc'ing Linux user maintainers (you can see the entry in the MAINTAINERS
file in the source tree).
On 9/17/18 4:51 PM, m.mar...@voestalpine.com wrote:
> Hello everyone,
>
> My name is Michael. I'm working for voestalpine in an embedded software
> project for railways diagnostics.
>
> Before fili
On 9/17/18 10:26 AM, Gerd Hoffmann wrote:
> This patch adds edid support to the qemu stdvga. It is turned off by
> default and can be enabled with the new edid property. The patch also
> adds xres and yres properties to specify the video mode you want the
> guest use. Works only with edid enable
On 9/17/18 10:40 AM, damien.he...@greensocs.com wrote:
> From: Damien Hedde
>
> Replace the zynq_slcr registers enum and macros using the
> hw/registerfields.h macros.
This looks cleaner, indeed.
>
> Signed-off-by: Damien Hedde
Reviewed-by: Philippe Mathieu-Daudé
> ---
> hw/misc/zynq_slcr
Have we got this the right way around
So you're saying the one with spec-ctrl disabled is faster, but has a lot more
kvm-exits?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1788665
Title:
Low
On Sat, 1 Sep 2018 20:33:20 -0400
Pavel Zbitskiy wrote:
> In a few places translate.c contains non-breaking spaces (0xc2 0xa0)
> instead of regular ones (0x20):
>
> 7c 7c c2 a0 63 63
> 7c 7c 2063 63
> | |c c
>
> This confuses some text editors.
>
> Signed-off-by: Pavel Zbi
On 09/19/2018 08:51 AM, Cédric Le Goater wrote:
> On 09/18/2018 08:44 PM, Peter Maydell wrote:
>> On 31 August 2018 at 11:38, Cédric Le Goater wrote:
>>> Now that MMIO execution is supported, introduce a 'mmio-exec' property
>>> to boot directly from CE0 of the FMC controller using a memory region
On Tue, Sep 18, 2018 at 11:19:38AM -0300, Eduardo Habkost wrote:
> On Tue, Sep 18, 2018 at 03:23:03PM +0200, Kashyap Chamarthy wrote:
> > Eduardo Habkost mentioned on IRC that the intended functionality of QMP
> > 'cpu-add' is replaced with a combination of 'query-hotpluggable-cpus'
> > and 'device
Hi
On Tue, Sep 18, 2018 at 7:49 PM Dr. David Alan Gilbert
wrote:
>
> * Marc-André Lureau (marcandre.lur...@gmail.com) wrote:
> > Hi
> >
> > On Tue, Sep 11, 2018 at 6:19 PM Laszlo Ersek wrote:
> > >
> > > +Alex, due to mention of 21e00fa55f3fd
> > >
> > > On 09/10/18 15:03, Marc-André Lureau wrot
On 9/18/18 11:28 AM, Paolo Bonzini wrote:
> Signed-off-by: Paolo Bonzini
> ---
> target/i386/hvf/hvf.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/target/i386/hvf/hvf.c b/target/i386/hvf/hvf.c
> index 5db167df98..9f52bc413a 100644
> --- a/target/i386/hvf/hvf.c
> +++ b/target/i386/hvf
When processing monitor config from guest store head0 width and height
for single-head configurations. Use these when creating the
DisplaySurface in the local renderer.
This fixes a rendering issue with wayland. Wayland rounds up the
framebuffer width and height to a multiple of 64, so with odd
On 8/31/18 12:38 PM, Cédric Le Goater wrote:
> In file included from /home/thuth/devel/qemu/hw/timer/aspeed_timer.c:16:
> /home/thuth/devel/qemu/include/hw/misc/aspeed_scu.h:37:3: error:
> redefinition of typedef 'AspeedSCUState' is a C11 feature
> [-Werror,-Wtypedef-redefinition]
> } AspeedS
Hi
On Wed, Sep 19, 2018 at 2:33 PM Gerd Hoffmann wrote:
>
> When processing monitor config from guest store head0 width and height
> for single-head configurations. Use these when creating the
> DisplaySurface in the local renderer.
>
> This fixes a rendering issue with wayland. Wayland rounds
Add zhangyi
-Original Message-
From: Marc-André Lureau [mailto:marcandre.lur...@gmail.com]
Sent: Wednesday, September 19, 2018 6:30 PM
To: Dr. David Alan Gilbert
Cc: He, Junyan ; Laszlo Ersek ; Eduardo
Habkost ; Michael S. Tsirkin ; Stefan
Berger ; QEMU ; Paolo
Bonzini ; Igor Mammedov
* Marc-André Lureau (marcandre.lur...@gmail.com) wrote:
> Hi
>
> On Tue, Sep 18, 2018 at 7:49 PM Dr. David Alan Gilbert
> wrote:
> >
> > * Marc-André Lureau (marcandre.lur...@gmail.com) wrote:
> > > Hi
> > >
> > > On Tue, Sep 11, 2018 at 6:19 PM Laszlo Ersek wrote:
> > > >
> > > > +Alex, due to
On 2018-09-19 12:30, Philippe Mathieu-Daudé wrote:
> On 9/18/18 11:28 AM, Paolo Bonzini wrote:
>> Signed-off-by: Paolo Bonzini
>> ---
>> target/i386/hvf/hvf.c | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/target/i386/hvf/hvf.c b/target/i386/hvf/hvf.c
>> index 5db167df98..9f52bc413a 1
Public bug reported:
I have already tested lots of versions of QEMU. Since qemu-2.3.0 -- qemu-3.0.0.
I find weird phenomena about windows's paint software cross-shaped cursor
offset a pixel since qemu-2.10.0, but it is ok before the version of
qemu-2.10.0. Only spice agent and service are runni
On Wed, 19 Sep 2018 11:58:22 +0100
"Dr. David Alan Gilbert" wrote:
> * Marc-André Lureau (marcandre.lur...@gmail.com) wrote:
> > Hi
> >
> > On Tue, Sep 18, 2018 at 7:49 PM Dr. David Alan Gilbert
> > wrote:
> > >
> > > * Marc-André Lureau (marcandre.lur...@gmail.com) wrote:
> > > > Hi
> > >
* Igor Mammedov (imamm...@redhat.com) wrote:
> On Wed, 19 Sep 2018 11:58:22 +0100
> "Dr. David Alan Gilbert" wrote:
>
> > * Marc-André Lureau (marcandre.lur...@gmail.com) wrote:
> > > Hi
> > >
> > > On Tue, Sep 18, 2018 at 7:49 PM Dr. David Alan Gilbert
> > > wrote:
> > > >
> > > > * Marc-And
Could be merged via qemu-trivial (cc'ed).
Li Qiang writes:
> Found by reading the code.
>
> Signed-off-by: Li Qiang
> ---
> include/qom/cpu.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/qom/cpu.h b/include/qom/cpu.h
> index dc130cd307..5bb94a9f86 100644
> -
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
include/block/block_backup.h | 13
block/backup.c | 38 +++-
2 files changed, 7 insertions(+), 44 deletions(-)
diff --git a/include/block/block_backup.h b/include/block/block_backup.h
index
Hi all!
We finally implemented fleecing scheme, create a test case for it (222)
and even made it safe (f8d59dfb40).
However, fleecing is used inside block-replication long ago, and to make
the scheme safe it uses direct interface to backup-job copy requests
synchronization, which can be dropped n
After commit f8d59dfb40
"block/backup: fix fleecing scheme: use serialized writes" fleecing
(specifically reading from backup target, when backup source is in
backing chain of backup target) is safe, because all backup-job writes
to target are serialized. Therefore we don't need additional
sync
In preparation for adding user mode emulation support for the
Linux usbfs interface, check for its kernel header.
Signed-off-by: Cortland Tölva
---
configure | 21 -
1 file changed, 20 insertions(+), 1 deletion(-)
diff --git a/configure b/configure
index 58862d2ae8..5d36f454
This patch series aims to let programs running under QEMU Linux user mode
emulation implement user-space USB drivers via the USBFS ioctl()s. First
I check for the necessary header files, then I define some types, and
last I implement the submit, discard, and reap functions, which involve
USB reque
Userspace submits a USB Request Buffer to the kernel, optionally
discards it, and finally reaps the URB. Thunk buffers from target
to host and back.
Tested by running an i386 scanner driver on ARMv7. Neither the
discardurb ioctl nor the kernel's updating the argument to the
reap ioctl with a poi
Provide ioctl definitions for the generic thunk mechanism to
convert most usbfs calls.
Signed-off-by: Cortland Tölva
---
linux-user/ioctls.h| 38 ++
linux-user/syscall.c | 3 ++
linux-user/syscall_defs.h | 32 ++
linux-user/syscall_type
The value from twoD_foreground (which is in host endian format) must
be converted to the endianness of the framebuffer (currently always
little endian) before it can be used to perform the fill operation.
Signed-off-by: Marcus Comstedt
---
Hi.
I noticed when running AmigaOS 4.1 as a guest that
Thomas Huth writes:
> The part of the documentation of DeviceClass that talks about instance_init
> is partly wrong: instance_init() functions must not abort or exit, since
> the function is also called during introspection of the device already.
I figure it was correct back when the comment was
Li Qiang writes:
> Also make the definition and declare of this function's argument name
> the same.
>
> Signed-off-by: Li Qiang
> ---
> include/qom/qom-qobject.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/qom/qom-qobject.h b/include/qom/qom-qobject.h
>
Gerd Hoffmann writes:
> Hi,
>
>> OK, so now I've found the bit about the magic 42; commit 7b074a22 of
>> yours; recommended checking for 42 for knowing we had autosuspend;
>> what's actually in the current fedora hid rules is serial!=1 - I wonder
>> what others have.
>
> Whatever upstream syste
Add a new Error parameter for vnc_display_init() to handle errors
in its caller: vnc_init_func(), just like vnc_display_open() does.
And let the call trace propagate the Error.
Besides, make vnc_start_worker_thread() return a bool to indicate
whether it succeeds instead of returning nothing.
Sign
The caller of qemu_init_vcpu() already passed the **errp to handle
errors. In view of this, add a new Error parameter to the following
call trace to propagate the error and let the further caller check it.
Besides, make qemu_init_vcpu() return a Boolean value to let its
callers know whether it suc
Currently, when qemu_signal_init() fails it only returns a non-zero
value but without propagating any Error. But its callers need a
non-null err when runs error_report_err(err), or else 0->msg occurs.
To avoid such segmentation fault, add a new Error parameter to make
the call trace to propagate t
Add judgement in compress_threads_save_cleanup() to check whether the
static CompressParam *comp_param has been allocated. If not, just
return; or else Segmentation fault will occur when using the
NULL comp_param's parameters in terminate_compression_threads().
One test case can reproduce this erro
Hi,
This idea comes from BiteSizedTasks, and this patch series implement
the error checking of qemu_thread_create: make qemu_thread_create
return a flag to indicate if it succeeded rather than failing with an
error; make all callers check it.
The first three patches apply to those call traces who
When multifd is used during migration, if there is an error before
the destination receives all new channels, the destination does not
exit but keeps waiting in our current code. However, a segmentaion
fault will occur in the source when multifd_save_cleanup() is called
again as the multifd_send_st
Peter Xu writes:
> On Wed, Sep 05, 2018 at 05:05:10PM +0200, Wolfgang Bumiller wrote:
>> On Mon, Jun 18, 2018 at 04:08:53PM +0200, Markus Armbruster wrote:
>> > From: Peter Xu
>> >
>> > Before this patch, monitor fd helpers might be called even earlier than
>> > monitor_init_globals(). This ca
To avoid the segmentation fault in qemu_thread_join(), just directly
return when the QemuThread *thread was failed to be created in both
qemu-thread-posix.c and qemu-thread-win32.c.
Signed-off-by: Fei Li
---
util/qemu-thread-posix.c | 3 +++
util/qemu-thread-win32.c | 2 +-
2 files changed, 4 in
Make qemu_thread_create() return a Boolean to indicate if it succeeds
rather than failing with an error. And add an Error parameter to hold
the error message and let the callers handle it.
Signed-off-by: Fei Li
---
cpus.c | 45 +++--
dump.
Le 19/09/2018 à 10:04, Cortland Tölva a écrit :
> In preparation for adding user mode emulation support for the
> Linux usbfs interface, check for its kernel header.
>
> Signed-off-by: Cortland Tölva
> ---
> configure | 21 -
> 1 file changed, 20 insertions(+), 1 deletion(-)
"Dr. David Alan Gilbert" writes:
> * Markus Armbruster (arm...@redhat.com) wrote:
>> Daniel P. Berrangé writes:
>>
>> > On Tue, Sep 04, 2018 at 08:39:27AM +0200, Markus Armbruster wrote:
>> >> Daniel P. Berrangé writes:
>> >>
>> >> > On Mon, Sep 03, 2018 at 09:30:52AM -0500, Eric Blake wrote:
Le 19/09/2018 à 15:39, Laurent Vivier a écrit :
> Le 19/09/2018 à 10:04, Cortland Tölva a écrit :
>> In preparation for adding user mode emulation support for the
>> Linux usbfs interface, check for its kernel header.
>>
>> Signed-off-by: Cortland Tölva
>> ---
>> configure | 21 ++
Hi
On Wed, Sep 19, 2018 at 4:14 PM Dr. David Alan Gilbert
wrote:
>
> * Igor Mammedov (imamm...@redhat.com) wrote:
> > On Wed, 19 Sep 2018 11:58:22 +0100
> > "Dr. David Alan Gilbert" wrote:
> >
> > > * Marc-André Lureau (marcandre.lur...@gmail.com) wrote:
> > > > Hi
> > > >
> > > > On Tue, Sep 18
On Wed, 19 Sep 2018, Marcus Comstedt wrote:
The value from twoD_foreground (which is in host endian format) must
be converted to the endianness of the framebuffer (currently always
little endian) before it can be used to perform the fill operation.
Signed-off-by: Marcus Comstedt
Reviewed-by:
Hi,
On 09/19/2018 08:57 AM, Mark Cave-Ayland wrote:
On 18/09/2018 22:12, Mark Cave-Ayland wrote:
Roman, can you reproduce this locally at all? My setup is nothing
special, just Debian Stretch on amd64.
Ok, so I am able to reproduce it with your image and --enable-debug, but
I was not able t
This patch replaces the bdrv_reopen() calls that set and remove the
BDRV_O_RDWR flag with the new bdrv_reopen_set_read_only() function.
Signed-off-by: Alberto Garcia
---
blockdev.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/blockdev.c b/blockdev.c
index 58e057b0d9..2f2
This patch replaces the bdrv_reopen() calls that set and remove the
BDRV_O_RDWR flag with the new bdrv_reopen_set_read_only() function.
Signed-off-by: Alberto Garcia
---
blockdev.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/blockdev.c b/blockdev.c
index 72f5347df
Most callers of bdrv_reopen() only use it to switch a BlockDriverState
between read-only and read-write, so this patch adds a new function
that does just that.
We also want to get rid of the flags parameter in the bdrv_reopen()
API, so this function sets the "read-only" option and passes the
origi
This patch replaces the bdrv_reopen() calls that set and remove the
BDRV_O_RDWR flag with the new bdrv_reopen_set_read_only() function.
Signed-off-by: Alberto Garcia
---
block/commit.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/block/commit.c b/block/commit.c
inde
When reopen_f() puts a block device in the reopen queue, some of the
new options are passed using a QDict, but others ("read-only" and the
cache options) are passed as flags.
This patch puts those flags in the QDict. This way the flags parameter
becomes redundant and we'll be able to get rid of it
This patch replaces the bdrv_reopen() calls that set and remove the
BDRV_O_RDWR flag with the new bdrv_reopen_set_read_only() function.
Signed-off-by: Alberto Garcia
---
block.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/block.c b/block.c
index e023945c8e..ac9
Hi,
in the description of my "Misc reopen-related patches" I said that the
next series after that one would be the implementation of the
blockdev-reopen QMP command. That's not going to be the case after all
because I have a dozen of new patches that I wanted to publish now.
So here's what's goin
If qemu_opts_absorb_qdict() fails and we carry on and call
update_flags_from_options() then that can result on a failed
assertion:
$ qemu-io -c 'reopen -o read-only=foo' hd.qcow2
block.c:1101: update_flags_from_options: Assertion `qemu_opt_find(opts,
BDRV_OPT_CACHE_DIRECT)' failed.
Abort
No one is using this function anymore, so we can safely remove it
Signed-off-by: Alberto Garcia
---
block.c | 21 -
include/block/block.h | 1 -
2 files changed, 22 deletions(-)
diff --git a/block.c b/block.c
index ac945b4bc8..3751167434 100644
--- a/block.c
+
The 'block-commit' QMP command is implemented internally using two
different drivers. If the source image is the active layer then the
mirror driver is used (commit_active_start()), otherwise the commit
driver is used (commit_start()).
In both cases the destination image must be put temporarily in
This function is used to put the hidden and secondary disks in
read-write mode before launching the backup job, and back in read-only
mode afterwards.
This patch does the following changes:
- Use an options QDict with the "read-only" option instead of
passing the changes as flags only.
-
This patch replaces the bdrv_reopen() calls that set and remove the
BDRV_O_RDWR flag with the new bdrv_reopen_set_read_only() function.
Signed-off-by: Alberto Garcia
---
block/stream.c | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/block/stream.c b/blo
Now that all callers are passing all flag changes as QDict options,
the flags parameter is no longer necessary, so we can get rid of it.
Signed-off-by: Alberto Garcia
---
block.c | 5 +++--
block/replication.c | 6 ++
include/block/block.h | 3 +--
qemu-io-cmds.c| 2 +
This patch replaces the bdrv_reopen() calls that set and remove the
BDRV_O_RDWR flag with the new bdrv_reopen_set_read_only() function.
Signed-off-by: Alberto Garcia
---
block/commit.c | 16 ++--
1 file changed, 6 insertions(+), 10 deletions(-)
diff --git a/block/commit.c b/block/co
On Wed, 09/19 21:35, Fei Li wrote:
> Add a new Error parameter for vnc_display_init() to handle errors
> in its caller: vnc_init_func(), just like vnc_display_open() does.
> And let the call trace propagate the Error.
>
> Besides, make vnc_start_worker_thread() return a bool to indicate
> whether
Now that all callers are passing the new options using the QDict we no
longer need the 'flags' parameter.
This patch makes the following changes:
1) The update_options_from_flags() call is no longer necessary
so it can be removed.
2) The update_flags_from_options() call is now used i
On Tue, Sep 18, 2018 at 14:04:35 -0700, Richard Henderson wrote:
> On 9/17/18 9:30 AM, Emilio G. Cota wrote:
> > cpu_reset(cs);
> > -cs->interrupt_request = sipi;
> > +atomic_mb_set(&cs->interrupt_request, sipi);
> > memcpy(&env->start_init_save, &save->start_init_save,
>
> Why d
On Wed, Sep 19, 2018 at 03:36:02PM +0200, Markus Armbruster wrote:
> Peter Xu writes:
>
> > On Wed, Sep 05, 2018 at 05:05:10PM +0200, Wolfgang Bumiller wrote:
> >> On Mon, Jun 18, 2018 at 04:08:53PM +0200, Markus Armbruster wrote:
> >> > From: Peter Xu
> >> >
> >> > Before this patch, monitor f
On Wed, 09/19 21:35, Fei Li wrote:
> Currently, when qemu_signal_init() fails it only returns a non-zero
> value but without propagating any Error. But its callers need a
> non-null err when runs error_report_err(err), or else 0->msg occurs.
>
> To avoid such segmentation fault, add a new Error pa
* Markus Armbruster (arm...@redhat.com) wrote:
> "Dr. David Alan Gilbert" writes:
>
> > * Markus Armbruster (arm...@redhat.com) wrote:
> >> Daniel P. Berrangé writes:
> >>
> >> > On Tue, Sep 04, 2018 at 08:39:27AM +0200, Markus Armbruster wrote:
> >> >> Daniel P. Berrangé writes:
> >> >>
> >>
On Tue 11 Sep 2018 02:32:56 PM CEST, Alberto Garcia wrote:
> If qemu_opts_absorb_qdict() fails and we carry on and call
> update_flags_from_options() then that can result on a failed
> assertion:
>
>$ qemu-io -c 'reopen -o read-only=foo' hd.qcow2
>block.c:1101: update_flags_from_options: As
On Wed, 09/19 21:35, Fei Li wrote:
> The caller of qemu_init_vcpu() already passed the **errp to handle
> errors. In view of this, add a new Error parameter to the following
> call trace to propagate the error and let the further caller check it.
>
> Besides, make qemu_init_vcpu() return a Boolean
On Wed, 09/19 21:35, Fei Li wrote:
> To avoid the segmentation fault in qemu_thread_join(), just directly
> return when the QemuThread *thread was failed to be created in both
> qemu-thread-posix.c and qemu-thread-win32.c.
Per English grammar, I think "when the QemuThread *thread failed to be crea
On 9/19/18 1:46 AM, lampahome wrote:
All images are on the RAID0(3 SSD).
Below is the performance:
image numberseq. read(MB/s)seq. write(MB/s)
11480 60
16 1453 36
32 1450
On 19 September 2018 at 07:47, Roman Kapl wrote:
> It seems that the `dcbz` instruction is not emulated correctly (which may
> lead to some garbage in inittab?). However, if I manualy inline the
> `helper_dcbz_common` code into `helper dcbz`, it starts to work.
This is because helper_dcbz_common(
On Wed, 19 Sep 2018 13:14:05 +0100
"Dr. David Alan Gilbert" wrote:
> * Igor Mammedov (imamm...@redhat.com) wrote:
> > On Wed, 19 Sep 2018 11:58:22 +0100
> > "Dr. David Alan Gilbert" wrote:
> >
> > > * Marc-André Lureau (marcandre.lur...@gmail.com) wrote:
> > > > Hi
> > > >
> > > > On Tue,
On Wed, 19 Sep 2018 18:36:14 +0400
Marc-André Lureau wrote:
> Hi
>
> On Wed, Sep 19, 2018 at 4:14 PM Dr. David Alan Gilbert
> wrote:
> >
> > * Igor Mammedov (imamm...@redhat.com) wrote:
> > > On Wed, 19 Sep 2018 11:58:22 +0100
> > > "Dr. David Alan Gilbert" wrote:
> > >
> > > > * Marc-Andr
Richard Henderson writes:
> This is something we talked about in the context of enabling sve in
> system mode. We don't want to replicate info between these two locations.
>
> I'm not 100% happy with this, thus the RFC. In particular, there are
> several places in id_isar0, id_isar2, and id_i
On Wed, 09/19 21:35, Fei Li wrote:
> Make qemu_thread_create() return a Boolean to indicate if it succeeds
> rather than failing with an error. And add an Error parameter to hold
> the error message and let the callers handle it.
>
> Signed-off-by: Fei Li
> ---
> cpus.c | 45
On Wed, 09/19 21:35, Fei Li wrote:
> Hi,
>
> This idea comes from BiteSizedTasks, and this patch series implement
> the error checking of qemu_thread_create: make qemu_thread_create
> return a flag to indicate if it succeeded rather than failing with an
> error; make all callers check it.
Looks g
On 19 September 2018 at 08:44, Alex Bennée wrote:
>
> Richard Henderson writes:
>
>> This is something we talked about in the context of enabling sve in
>> system mode. We don't want to replicate info between these two locations.
>>
>> I'm not 100% happy with this, thus the RFC. In particular,
On 19 September 2018 at 07:46, BALATON Zoltan wrote:
> On Wed, 19 Sep 2018, Marcus Comstedt wrote:
>>
>> The value from twoD_foreground (which is in host endian format) must
>> be converted to the endianness of the framebuffer (currently always
>> little endian) before it can be used to perform th
On Tue, Sep 18, 2018 at 05:35:20PM +0200, Paolo Bonzini wrote:
> On 18/09/2018 16:22, Eduardo Habkost wrote:
> > On Tue, Sep 18, 2018 at 04:02:54PM +0200, Paolo Bonzini wrote:
> >> On 18/09/2018 15:14, Eduardo Habkost wrote:
> >>> If it broke something, we should restore the option names and
> >>>
On Mon, 17 Sep 2018 12:30:33 -0400
"Emilio G. Cota" wrote:
> From: Paolo Bonzini
>
> It will be changed to an atomic operation soon.
>
> Cc: Cornelia Huck
> Cc: Richard Henderson
> Cc: Alexander Graf
> Cc: David Hildenbrand
> Cc: qemu-s3...@nongnu.org
> Signed-off-by: Paolo Bonzini
> Sign
On Mon, 17 Sep 2018 12:30:51 -0400
"Emilio G. Cota" wrote:
> From: Paolo Bonzini
>
> Cc: Cornelia Huck
> Cc: Christian Borntraeger
> Cc: Alexander Graf
> Cc: Richard Henderson
> Cc: David Hildenbrand
> Cc: qemu-s3...@nongnu.org
> Signed-off-by: Paolo Bonzini
> Signed-off-by: Emilio G. Cot
On Mon, 17 Sep 2018 12:31:02 -0400
"Emilio G. Cota" wrote:
> From: Paolo Bonzini
>
> cpu->do_interrupt can now be called with BQL held (from
> cpu->cpu_exec_interrupt) or without (from cpu_handle_exception).
>
> Only a few targets rely on global device state in cc->do_interrupt;
> add checks t
On Wed, Sep 19, 2018 at 12:22:19PM +0200, Kashyap Chamarthy wrote:
> On Tue, Sep 18, 2018 at 11:19:38AM -0300, Eduardo Habkost wrote:
> > On Tue, Sep 18, 2018 at 03:23:03PM +0200, Kashyap Chamarthy wrote:
> > > Eduardo Habkost mentioned on IRC that the intended functionality of QMP
> > > 'cpu-add'
1 - 100 of 196 matches
Mail list logo
