Ok, sorry, got that wrong - we sometimes get bug reports about the
android emulator (which is a fork of QEMU) here, and at a first glance,
your bug report looked like one of these misguided bug tickets, too.
Anyway, please provide some more information: Which version of QEMU are
you using? Which o
On Wed, 22 May 2019 06:11:12 +1000
Anton Blanchard wrote:
> Hi,
>
> > I've now had a bit of time to look through this and I believe it is
> > correct, so:
> >
> > Reviewed-by: Mark Cave-Ayland
>
> Thanks Mark. David: any chance we could get this merged? I can't run a
> recent Ubuntu image s
Today, when a reset occurs on a pseries machine using the 'dual'
interrupt mode, the KVM devices are released and recreated depending
on the interrupt mode selected by CAS. If XIVE is selected, the SysBus
memory regions of the SpaprXive model are initialized by the KVM
backend initialization routin
Hello,
Here is a little series fixing multiple resets when in 'dual'
interrupt mode and changing the default mode to 'dual'.
Thanks,
C.
Cédric Le Goater (2):
spapr/xive: fix multiple resets when using the 'dual' interrupt mode
spapr: change default interrupt mode to 'dual'
hw/intc/spapr_x
Now that XIVE support is complete (QEMU emulated and KVM devices),
change the pseries machine to advertise both interrupt modes: XICS
(P7/P8) and XIVE (P9).
The machine default interrupt modes depends on the version. Current
settings are:
pseries default interrupt mode
4.1 dual
Looking through old bug tickets... can this issue still be reproduced
with the latest version of QEMU? Or could we close this ticket nowadays?
** Changed in: qemu
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is su
On Wed, 22 May 2019 14:45:43 +1000
David Gibson wrote:
> spapr machine capabilities are supposed to be sent in the migration stream
> so that we can sanity check the source and destination have compatible
> configuration. Unfortunately, when we added the hpt-max-page-size
> capability, we forgot
On 21/05/19 22:37, Eduardo Habkost wrote:
>> But this is the one we're going with? Do we have a plan for teaching it
>> not to panic for our use of named custom types?
>
> If I understood correctly, the patch from Paolo that I have
> forwarded to this thread is all we need. Are there other issues
I tested many qemu & linux versions
in case of qemu,
2.12
3.10
3.12
4.0.0
All versions I tested have same problem
also I tested many versions of linux
ubuntu 18.04 18.10
centos 7
fedora 18 19
rhel
Actually it is not only problem of windows rotation, if home launcher
refreshed, vram usag
On Tue, 21 May 2019 10:34:03 -0400
"Michael S. Tsirkin" wrote:
> On Tue, May 21, 2019 at 04:29:58PM +0200, Igor Mammedov wrote:
> > On Mon, 20 May 2019 23:37:22 -0400
> > "Michael S. Tsirkin" wrote:
> >
> > > On Tue, May 21, 2019 at 11:32:49AM +0800, Wei Yang wrote:
> > > > build_append_foo
From: Marc-André Lureau
That should fix the following warning:
/home/pm215/qemu/contrib/libvhost-user/libvhost-user.c: In function
‘vu_set_mem_table_exec_postcopy’:
/home/pm215/qemu/contrib/libvhost-user/libvhost-user.c:666:9: error:
format ‘%llx’ expects argument of type ‘long long unsigned int
From: Marc-André Lureau
Fixes warnings:
warning: cast to pointer from integer of different size
[-Wint-to-pointer-cast]
Signed-off-by: Marc-André Lureau
Reviewed-by: Philippe Mathieu-Daudé
Message-id: 20190514104126.6294-2-marcandre.lur...@redhat.com
Signed-off-by: Gerd Hoffmann
---
contri
From: Marc-André Lureau
Add a vhost-user input backend example, based on virtio-input-host
device. It takes an evdev path as argument, and can be associated with
a vhost-user-input device via a UNIX socket:
$ vhost-user-input -p /dev/input/eventX -s /tmp/vui.sock
$ qemu ... -chardev socket,id=v
On 21/05/19 15:30, Li Qiang wrote:
> Ping
>
> Paolo, could you merge these to your misc tree?
Queued now, thanks.
Paolo
> Thanks,
> Li Qiang
>
> Li Qiang mailto:liq...@163.com>> 于2019年5月11日周六 上
> 午12:44写道：
>
> Recently I am considering write a driver for edu device.
> After readin
On Fri, May 10, 2019 at 17:32:03 -0300, Eduardo Habkost wrote:
> On Thu, May 09, 2019 at 06:36:18PM +0200, Jiri Denemark wrote:
> > On Thu, May 09, 2019 at 18:06:03 +0200, Igor Mammedov wrote:
> > > On Thu, 9 May 2019 10:56:17 -0300
> > > Eduardo Habkost wrote:
> > >
> > > > On Thu, May 09, 2019
The following changes since commit a4f667b6714916683408b983cfe0a615a725775f:
Merge remote-tracking branch 'remotes/cohuck/tags/s390x-20190521-3' into
staging (2019-05-21 16:30:13 +0100)
are available in the Git repository at:
git://git.kraxel.org/qemu tags/input-20190522-pull-re
On Wed, 22 May 2019 09:40:15 +0200
Cédric Le Goater wrote:
> Today, when a reset occurs on a pseries machine using the 'dual'
> interrupt mode, the KVM devices are released and recreated depending
> on the interrupt mode selected by CAS. If XIVE is selected, the SysBus
> memory regions of the Spa
On Tue, 21 May 2019 at 21:07, John Snow wrote:
>
> Sphinx, through Pygments, does not like annotated json examples very
> much. In some versions of Sphinx (1.7), it will render the non-json
> portions of code blocks in red, but in newer versions (2.0) it will
> throw an exception and not highlight
On Wed, May 8, 2019 at 1:44 PM Markus Armbruster wrote:
>
> Stefano Garzarella writes:
>
> > On Tue, May 07, 2019 at 08:34:51AM +0200, Markus Armbruster wrote:
> >> Cc: Peter for a libvirt perspective.
> >>
> >> Stefano Garzarella writes:
> >>
> >> > This patch adds the support of preallocation
On Fri, May 10, 2019 at 17:23:13 -0300, Eduardo Habkost wrote:
> On Fri, May 10, 2019 at 01:33:03PM +0200, Jiri Denemark wrote:
> > On Thu, May 09, 2019 at 13:08:25 -0300, Eduardo Habkost wrote:
> > > On Thu, May 09, 2019 at 05:26:16PM +0200, Jiri Denemark wrote:
> > > > On Thu, May 09, 2019 at 10:
This will allow running the tests in Patchew, which has two runners
that might choose concurrently the same VM build for two different
series.
Signed-off-by: Paolo Bonzini
---
tests/vm/Makefile.include | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/vm/Makefile.include
On Wed, 22 May 2019 at 03:25, Jonathan Behrens wrote:
>
> Hesham,
>
> I don't think this is quite right. If I understand correctly, PMP permissions
> are only validated on TLB fills, not on all accesses. (Is anyone able to
> confirm this?) If so, this function can't just validate the range of a
On 14/05/2019 16:53, Chen-Yu Tsai wrote:
From: Chen-Yu Tsai
Since Linux 2.6 the stat syscalls have mostly supported nanosecond
components for each of the file-related timestamps.
QEMU user mode emulation currently does not pass through the nanosecond
portion of the timestamp, even when the hos
On Tue, 21 May 2019 14:28:35 +0800
Wei Yang wrote:
> Now we have two identical build_mcfg functions.
>
> Consolidate them in acpi/pci.c.
>
> Signed-off-by: Wei Yang
Reviewed-by: Igor Mammedov
>
> v4:
> * ACPI_PCI depends on both ACPI and PCI
> * rebase on latest master, adjust arm Kcon
On 5/22/19 10:52 AM, Greg Kurz wrote:
> On Wed, 22 May 2019 09:40:15 +0200
> Cédric Le Goater wrote:
>
>> Today, when a reset occurs on a pseries machine using the 'dual'
>> interrupt mode, the KVM devices are released and recreated depending
>> on the interrupt mode selected by CAS. If XIVE is s
On 19/05/2019 18:15, Aleksandar Markovic wrote:
From: Aleksandar Markovic
Fix support for the SIOCATMARK and SIOCGPGRP ioctls for xtensa by
correcting corresponding macro definition.
Values for TARGET_SIOCATMARK and TARGET_SIOCGPGRP are determined by
Linux kernel. Following relevant lines (obt
The current implementation unnecessarily checks for PMP even if MMU translation
failed. This may trigger a wrong PMP access exception instead of
a page exception.
For example, the very first instruction fetched after the first satp write in
S-Mode will trigger a PMP access fault instead of an inst
The current implementation returns 1 (PMP check success) if the address is in
range even if the PMP entry is off. This is a bug.
For example, if there is a PMP check in S-Mode which is in range, but its PMP
entry is off, this will succeed, which it should not.
The patch fixes this bug by only che
On 19/05/2019 18:15, Aleksandar Markovic wrote:
From: Aleksandar Markovic
Add support for setting the process (or process group) to receive SIGIO
or SIGURG signals when I/O becomes possible or urgent data is available,
using SIOCSPGRP ioctl.
The ioctl numeric values for SIOCSPGRP are platform-
On 19/05/2019 18:15, Aleksandar Markovic wrote:
From: Neng Chen
Add support for getting and setting extended private flags of a
network device via SIOCSIFPFLAGS and SIOCGIFPFLAGS ioctls.
The ioctl numeric values are platform-independent and determined by
the file include/uapi/linux/sockios.h i
On 19/05/2019 18:15, Aleksandar Markovic wrote:
From: Daniel Santos
Sanitize interp_info structure in load_elf_binary() and, for MIPS only,
init its field fp_abi to MIPS_ABI_FP_UNKNOWN. This fixes appearances of
"Unexpected FPU mode" message in some MIPS use cases. Currently, this
bug is a comp
On 19/05/2019 18:15, Aleksandar Markovic wrote:
From: Neng Chen
Add support for options IPV6_ADD_MEMBERSHIP and IPV6_DROP_MEMPEMBERSHIP
of the syscall setsockopt(). These options control membership in
multicast groups. Their argument is a pointer to a struct ipv6_mreq,
which is in turn defined
Am 22.05.2019 um 02:51 hat Aarushi Mehta geschrieben:
> On Tue, 2019-05-21 at 19:39 -0500, Eric Blake wrote:
> > On 5/21/19 6:52 PM, Aarushi Mehta wrote:
> > > Signed-off-by: Aarushi Mehta
> >
> > Sparse on the details. The subject line says what, but without a
> > 'why'
> > for how io_uring is d
On 19/05/2019 18:15, Aleksandar Markovic wrote:
From: Neng Chen
Add support for options IPV6_ADD_MEMBERSHIP and IPV6_DROP_MEMPEMBERSHIP
of the syscall setsockopt(). These options control membership in
multicast groups. Their argument is a pointer to a struct ipv6_mreq,
which is in turn defined
Add dashes, so they don't look like two separate things when printed.
Signed-off-by: Gerd Hoffmann
---
hw/usb/dev-hub.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/hw/usb/dev-hub.c b/hw/usb/dev-hub.c
index 7e9339b8a83d..9b04b6a6ec2d 100644
--- a/hw/usb/dev-hub.
Add usb_hub_port_set() and usb_hub_port_clear() helpers which care about
updating the change bits (port->wPortChange) properly, so we don't need
to have that logic sprinkled all over the place ;)
Signed-off-by: Gerd Hoffmann
---
hw/usb/dev-hub.c | 84 ++---
Helper function to update port status bits which depends on the
connected device. We need the same logic for device attach and
port reset, so factor it out.
---
hw/usb/dev-hub.c | 29 +
1 file changed, 17 insertions(+), 12 deletions(-)
diff --git a/hw/usb/dev-hub.c b/
Add num_ports property which allows configure the number of downstream
ports. Valid range is 1-8, default is 8.
Signed-off-by: Gerd Hoffmann
---
hw/usb/dev-hub.c | 45 +
1 file changed, 29 insertions(+), 16 deletions(-)
diff --git a/hw/usb/dev-hub.c
Gerd Hoffmann (5):
usb-hub: tweak feature names
usb-hub: make number of ports runtime-configurable
usb-hub: add helpers to update port state
usb-hub: add usb_hub_port_update()
usb-hub: emulate per port power switching
hw/usb/dev-hub.c | 221 +--
On Tue, 21 May 2019 at 23:40, Alistair Francis wrote:
>
> On Tue, May 21, 2019 at 3:44 AM Hesham Almatary
> wrote:
> >
> > The PMP should be checked when doing a page table walk, and report access
> > fault exception if the to-be-read PTE failed the PMP check.
> >
> > Suggested-by: Jonathan Behre
Add support for per port power switching.
Virtual power of course ;)
Use port-power=on property to enable this.
Signed-off-by: Gerd Hoffmann
---
hw/usb/dev-hub.c | 63
1 file changed, 63 insertions(+)
diff --git a/hw/usb/dev-hub.c b/hw/usb/dev-h
On Wed, May 22, 2019 at 02:23:23AM +0300, Aaro Koskinen wrote:
> Hi,
>
> On Mon, May 20, 2019 at 09:05:33PM +0200, Corentin Labbe wrote:
> > Hello
> >
> > I am working on adding a maximum set of qemu machine on kernelCI.
>
> That's cool.
>
> > For OMAP, five machine exists and I fail to boot an
On 19/05/2019 22:19, Richard Henderson wrote:
For those hosts with SHMLBA > getpagesize, we don't automatically
select a guest address that is compatible with the host. We can
achieve this by boosting the alignment of guest_base and by adding
an extra alignment argument to mmap_find_vma.
Signed
On 19/05/2019 22:19, Richard Henderson wrote:
This can avoid stack allocation failures for i386 guest
on ppc64 (64k page) host.
Suggested-by: Laurent Vivier
Signed-off-by: Richard Henderson
---
linux-user/mmap.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/linux-user/mmap.c b/linux
On Wed, May 22, 2019 at 5:08 PM Laurent Vivier wrote:
>
> On 14/05/2019 16:53, Chen-Yu Tsai wrote:
> > From: Chen-Yu Tsai
> >
> > Since Linux 2.6 the stat syscalls have mostly supported nanosecond
> > components for each of the file-related timestamps.
> >
> > QEMU user mode emulation currently d
That way the device reset handler can see what
the before-reset state of the device is.
Signed-off-by: Gerd Hoffmann
---
hw/usb/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/usb/core.c b/hw/usb/core.c
index 8fbd9c7d573b..3ab48a16074b 100644
--- a/hw/usb/core.c
+++
Seems some devices become confused when we call
libusb_set_configuration(). So before calling the function check
whenever the device has multiple configurations in the first place, and
in case it hasn't (which is the case for the majority of devices) simply
skip the call as it will have no effect
Gerd Hoffmann (3):
usb: call reset handler before updating state
usb-host: skip reset for untouched devices
usb-host: avoid libusb_set_configuration calls
hw/usb/core.c| 2 +-
hw/usb/host-libusb.c | 21 +
2 files changed, 14 insertions(+), 9 deletions(-)
--
If the guest didn't talk to the device yet, skip the reset.
Without this usb-host devices get resetted a number of times
at boot time for no good reason.
Signed-off-by: Gerd Hoffmann
---
hw/usb/host-libusb.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/hw/usb/host-libusb.c b/hw/usb/hos
Add modifier parameter to egl_get_fd_for_texture(), to return the used
modifier on dmabuf exports.
Check and use QemuDmaBuf->modifier in egl_dmabuf_import_texture() for
dmabuf imports.
Signed-off-by: Gerd Hoffmann
---
include/ui/egl-helpers.h | 3 ++-
ui/egl-helpers.c | 37
dmabufs can have a format modifier (DRM_FORMAT_MOD_*) which is used for
tiled layouts for example. Add a field to QemuDmaBuf so we can carry
around that information.
Signed-off-by: Gerd Hoffmann
---
include/ui/console.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/ui/console.h b/
Fill the new QemuDmaBuf->modifier field properly from plane info.
Signed-off-by: Gerd Hoffmann
---
hw/vfio/display.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/hw/vfio/display.c b/hw/vfio/display.c
index a3d9c8f5beac..13969180b2dd 100644
--- a/hw/vfio/display.c
+++ b/hw/vfio/display.c
@
Gerd Hoffmann (3):
console: add dmabuf modifier field.
vfio/display: set dmabuf modifier field
egl-helpers: add dmabuf modifier support.
include/ui/console.h | 1 +
include/ui/egl-helpers.h | 3 ++-
hw/vfio/display.c| 1 +
ui/egl-helpers.c | 37
On 16/05/19 14:50, Peter Maydell wrote:
> On Wed, 15 May 2019 at 10:48, Stefan Hajnoczi wrote:
>> 1. It's required for Intel Control-flow Enforcement Technology (CET).
>>The existing ucontext backend doesn't work with CET.
>> 2. It's faster than the existing ucontext implementation.
>
> Mmm,
Patchew URL: https://patchew.org/QEMU/20190522092351.17920-1-kra...@redhat.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Subject: [Qemu-devel] [PATCH 0/5] usb-hub: cleanups, configurable port count,
per-port power switching emulation.
Ty
Am 13.05.2019 um 17:06 hat John Snow geschrieben:
> If the bitmap can't be used for whatever reason, we skip putting down
> the reference. Fix that.
>
> In practice, this means that if you attempt to gracefully exit QEMU
> after a backup command being rejected, bdrv_close_all will fail and
> tell
On Tue, 21 May 2019 16:51:27 -0400
Farhan Ali wrote:
> On 05/21/2019 12:32 PM, Cornelia Huck wrote:
> > On Mon, 20 May 2019 12:29:56 -0400
> > Eric Farman wrote:
> >
> >> On 5/7/19 11:47 AM, Cornelia Huck wrote:
> >>> A vfio-ccw device may provide an async command subregion for
> >>> issuin
On Tue, 21 May 2019 16:50:47 -0400
Farhan Ali wrote:
> On 05/07/2019 11:47 AM, Cornelia Huck wrote:
> > A vfio-ccw device may provide an async command subregion for
> > issuing halt/clear subchannel requests. If it is present, use
> > it for sending halt/clear request to the device; if not, fall
On Wed, 22 May 2019 09:40:16 +0200
Cédric Le Goater wrote:
> Now that XIVE support is complete (QEMU emulated and KVM devices),
> change the pseries machine to advertise both interrupt modes: XICS
> (P7/P8) and XIVE (P9).
>
> The machine default interrupt modes depends on the version. Current
>
On 20/05/19 23:05, Eduardo Habkost wrote:
> What if enable_cpu_pm is false but we're running TCG, or if
> enable_cpu_pm is true but we're not using -cpu host?
>
> Shouldn't this be conditional on
> (env->features[FEAT_1_ECX] & CPUID_EXT_MONITOR)
> instead?
Yes, it should. I fixed it locally.
Am 08.04.2019 um 18:26 hat Vladimir Sementsov-Ogievskiy geschrieben:
> drv_co_block_status digs bs->file for additional, more accurate search
> for hole inside region, reported as DATA by bs since 5daa74a6ebc.
>
> This accuracy is not free: assume we have qcow2 disk. Actually, qcow2
> knows, where
On Mon 20 May 2019 08:20:23 AM CEST, Denis Plotnikov wrote:
> +/* Compression type extension */
> +if (s->compression_type != 0) {
> +Qcow2CompressionTypeExt comp_header = {
> +.compression_type = cpu_to_be32(s->compression_type),
> +};
Shouldn't we have an enum
On Tue, May 21, 2019 at 10:48:21AM +0200, Thomas Huth wrote:
> On 21/05/2019 10.20, Stefan Hajnoczi wrote:
> > QEMU 4.0 ships the core micro:bit emulation that was implemented during
> > Outreachy and GSoC 2018. This blog posts explains how to use it and
> > describes the current status.
> [...]
>
QEMU 4.0 ships the core micro:bit emulation that was implemented during
Outreachy and GSoC 2018. This blog posts explains how to use it and
describes the current status.
Signed-off-by: Stefan Hajnoczi
---
v2:
* Used git format-patch --binary to include .png file contents [thuth]
* s/runtime/ru
On Wed, May 22, 2019 at 12:05 PM Gerd Hoffmann wrote:
>
> Fill the new QemuDmaBuf->modifier field properly from plane info.
>
> Signed-off-by: Gerd Hoffmann
Reviewed-by: Marc-André Lureau
> ---
> hw/vfio/display.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/hw/vfio/display.c b/hw
On Wed, May 22, 2019 at 12:05 PM Gerd Hoffmann wrote:
>
> dmabufs can have a format modifier (DRM_FORMAT_MOD_*) which is used for
> tiled layouts for example. Add a field to QemuDmaBuf so we can carry
> around that information.
>
> Signed-off-by: Gerd Hoffmann
Reviewed-by: Marc-André Lureau
>
Hi
On Wed, May 22, 2019 at 12:04 PM Gerd Hoffmann wrote:
>
> Add modifier parameter to egl_get_fd_for_texture(), to return the used
> modifier on dmabuf exports.
But nothing uses it yet?
>
> Check and use QemuDmaBuf->modifier in egl_dmabuf_import_texture() for
> dmabuf imports.
That could be a
Am 08.04.2019 um 18:26 hat Vladimir Sementsov-Ogievskiy geschrieben:
> Hi!
>
> It's a continuation for
> "[PATCH] qcow2: avoid lseek on block_status if possible"
> https://lists.gnu.org/archive/html/qemu-devel/2019-01/msg06598.html
>
> performance results for block-status on tmpfs [tests original
On Tue, May 21, 2019 at 01:30:59PM +0200, Kevin Wolf wrote:
> Am 21.05.2019 um 13:04 hat Paolo Bonzini geschrieben:
> > On 21/05/19 12:36, Stefan Hajnoczi wrote:
> > > This is RFC because I am waiting for a test result on the system where
> > > the bug was originally discovered. I'm also open to n
On 5/21/19 11:04 AM, Daniel P. Berrangé wrote:
> On Thu, May 16, 2019 at 07:39:01PM -0700, Richard Henderson wrote:
>> For user-only, we require only the random number bits of the
>> crypto subsystem. Rename crypto-aes-obj-y to crypto-user-obj-y,
>> and add the random number objects, plus init.o t
On Wed, May 22, 2019 at 06:52:45AM -0400, Richard Henderson wrote:
> On 5/21/19 11:04 AM, Daniel P. Berrangé wrote:
> > On Thu, May 16, 2019 at 07:39:01PM -0700, Richard Henderson wrote:
> >> For user-only, we require only the random number bits of the
> >> crypto subsystem. Rename crypto-aes-obj-
On Thu, May 16, 2019 at 07:39:01PM -0700, Richard Henderson wrote:
> For user-only, we require only the random number bits of the
> crypto subsystem. Rename crypto-aes-obj-y to crypto-user-obj-y,
> and add the random number objects, plus init.o to handle any
> extra stuff the crypto library requir
On Thu, May 16, 2019 at 07:38:59PM -0700, Richard Henderson wrote:
> The change in v8 is to which objects are linked in to user-only
> from the crypto directory. Daniel asked for all of crypto-obj-y
> to be added, but I have been unable to find a solution that works.
>
> If I add crypto-obj-y, th
On 5/22/19 6:56 AM, Daniel P. Berrangé wrote:
>> I have a working configuration here in v8. Can we please leave the bikeshed
>> unpainted for the moment and you can adjust the makefiles as you see fit
>> afterward?
>
> Yep, ok. I'll be away on holiday for a while so don't have time to look
> int
> I also think that, if we create a bunch more of these wrappers:
>
>> +DEF_VFAE_HELPER(8)
>> +DEF_VFAE_HELPER(16)
>> +DEF_VFAE_HELPER(32)
>
> then RT and ZS can be passed in as constant parameters to the above, and then
> the compiler will fold away all of the stuff that's not needed for each
On 5/10/19 6:43 PM, Li Qiang wrote:
> The dma related variable dma.dst/src/cnt is dma_addr_t, it is
> uint64_t in x64 platform. Change these usage from uint32_to
> uint64_t to avoid trancation in edu_dma_timer.
>
> Signed-off-by: Li Qiang
Reviewed-by: Philippe Mathieu-Daudé
> ---
> Change sinc
On 22/05/2019 12.43, Stefan Hajnoczi wrote:
> QEMU 4.0 ships the core micro:bit emulation that was implemented during
> Outreachy and GSoC 2018. This blog posts explains how to use it and
> describes the current status.
>
> Signed-off-by: Stefan Hajnoczi
> ---
> v2:
> * Used git format-patch --
On 5/22/19 7:01 AM, David Hildenbrand wrote:
>
>> I also think that, if we create a bunch more of these wrappers:
>>
>>> +DEF_VFAE_HELPER(8)
>>> +DEF_VFAE_HELPER(16)
>>> +DEF_VFAE_HELPER(32)
>>
>> then RT and ZS can be passed in as constant parameters to the above, and then
>> the compiler will fo
On 22.05.19 13:09, Richard Henderson wrote:
> On 5/22/19 7:01 AM, David Hildenbrand wrote:
>>
>>> I also think that, if we create a bunch more of these wrappers:
>>>
+DEF_VFAE_HELPER(8)
+DEF_VFAE_HELPER(16)
+DEF_VFAE_HELPER(32)
>>>
>>> then RT and ZS can be passed in as constant para
On 21.05.19 21:16, Kevin Wolf wrote:
> Instead of just asserting that no requests are in flight in
> bdrv_replace_node(), which is a requirement that most callers ignore, we
> can just drain the source node right there. This fixes at least starting
> a commit job while I/O is active on the backing
[Adding the mailing list back in.]
On 5/22/19 2:47 AM, Aleksandar Markovic wrote:
>> > Version 6 was
>> > https://lists.gnu.org/archive/html/qemu-devel/2019-01/msg04794.html
>> >
>> > Since v5, I've fixed the ioctl failure that Laurent found, and
>> > have done a few more syscalls.
>> >
>> > I've
On Wed, May 22, 2019 at 12:47:47PM +0200, Marc-André Lureau wrote:
> Hi
>
> On Wed, May 22, 2019 at 12:04 PM Gerd Hoffmann wrote:
> >
> > Add modifier parameter to egl_get_fd_for_texture(), to return the used
> > modifier on dmabuf exports.
>
> But nothing uses it yet?
WIP still. Sneak preview
22.05.2019 13:47, Kevin Wolf wrote:
> Am 08.04.2019 um 18:26 hat Vladimir Sementsov-Ogievskiy geschrieben:
>> Hi!
>>
>> It's a continuation for
>> "[PATCH] qcow2: avoid lseek on block_status if possible"
>> https://lists.gnu.org/archive/html/qemu-devel/2019-01/msg06598.html
>>
>> performance result
On Thu 16 May 2019 04:27:49 PM CEST, Anton Nefedov wrote:
> If COW areas of the newly allocated clusters are zeroes on the backing
> image, efficient bdrv_write_zeroes(flags=BDRV_REQ_NO_FALLBACK) can be
> used on the whole cluster instead of writing explicit zero buffers later
> in perform_cow().
>
On 22/05/2019 12:56, Daniel P. Berrangé wrote:
On Wed, May 22, 2019 at 06:52:45AM -0400, Richard Henderson wrote:
On 5/21/19 11:04 AM, Daniel P. Berrangé wrote:
On Thu, May 16, 2019 at 07:39:01PM -0700, Richard Henderson wrote:
For user-only, we require only the random number bits of the
crypt
On 22/05/2019 12:58, Daniel P. Berrangé wrote:
On Thu, May 16, 2019 at 07:38:59PM -0700, Richard Henderson wrote:
The change in v8 is to which objects are linked in to user-only
from the crypto directory. Daniel asked for all of crypto-obj-y
to be added, but I have been unable to find a solutio
On 5/21/19 5:28 PM, Cornelia Huck wrote:
> commit a188339ca5a396acc588e5851ed7e19f66b0ebd9
>
> Signed-off-by: Cornelia Huck
> ---
[...]
> #define __NR_mq_notify 184
> __SC_COMP(__NR_mq_notify, sys_mq_notify, compat_sys_mq_notify)
> #define __NR_mq_getsetattr 185
> @@ -536,8 +567,10 @@ __SC_COM
On 21.05.19 21:16, Kevin Wolf wrote:
> This tests that concurrent requests are correctly drained before making
> graph modifications instead of running into assertions in
> bdrv_replace_node().
>
> Signed-off-by: Kevin Wolf
> ---
> tests/qemu-iotests/255| 83 +
On 05/22/2019 06:17 AM, Cornelia Huck wrote:
On Tue, 21 May 2019 16:50:47 -0400
Farhan Ali wrote:
On 05/07/2019 11:47 AM, Cornelia Huck wrote:
A vfio-ccw device may provide an async command subregion for
issuing halt/clear subchannel requests. If it is present, use
it for sending halt/clea
On Wed, May 22, 2019 at 09:58:29AM +0200, Greg Kurz wrote:
> On Wed, 22 May 2019 14:45:43 +1000
> David Gibson wrote:
>
> > spapr machine capabilities are supposed to be sent in the migration stream
> > so that we can sanity check the source and destination have compatible
> > configuration. Unf
On Wed, 22 May 2019 13:47:25 +0200
Philippe Mathieu-Daudé wrote:
> On 5/21/19 5:28 PM, Cornelia Huck wrote:
> > commit a188339ca5a396acc588e5851ed7e19f66b0ebd9
> >
> > Signed-off-by: Cornelia Huck
> > ---
> [...]
> > #define __NR_mq_notify 184
> > __SC_COMP(__NR_mq_notify, sys_mq_notify, co
On 22/05/2019 11:45, Chen-Yu Tsai wrote:
On Wed, May 22, 2019 at 5:08 PM Laurent Vivier wrote:
On 14/05/2019 16:53, Chen-Yu Tsai wrote:
From: Chen-Yu Tsai
Since Linux 2.6 the stat syscalls have mostly supported nanosecond
components for each of the file-related timestamps.
QEMU user mode e
On 22/05/2019 14:07, Cornelia Huck wrote:
On Wed, 22 May 2019 13:47:25 +0200
Philippe Mathieu-Daudé wrote:
On 5/21/19 5:28 PM, Cornelia Huck wrote:
commit a188339ca5a396acc588e5851ed7e19f66b0ebd9
Signed-off-by: Cornelia Huck
---
[...]
#define __NR_mq_notify 184
__SC_COMP(__NR_mq_notif
On Wed, 22 May 2019 21:10:35 +1000
David Gibson wrote:
> On Wed, May 22, 2019 at 09:58:29AM +0200, Greg Kurz wrote:
> > On Wed, 22 May 2019 14:45:43 +1000
> > David Gibson wrote:
> >
> > > spapr machine capabilities are supposed to be sent in the migration stream
> > > so that we can sanity c
On Wed, 22 May 2019 14:10:39 +0200
Laurent Vivier wrote:
> On 22/05/2019 14:07, Cornelia Huck wrote:
> > On Wed, 22 May 2019 13:47:25 +0200
> > Philippe Mathieu-Daudé wrote:
> >
> >> On 5/21/19 5:28 PM, Cornelia Huck wrote:
> >>> commit a188339ca5a396acc588e5851ed7e19f66b0ebd9
> >>>
> >>> S
Public bug reported:
Docker throws float32nan errors when running alpine container on a
CentOS 7.6 ppc64le Distro VM, when using Fedora 30 Host qemu 3.1. I
Compiled qemu 2.11.2 on the Fedora 30 and using this qemu-system-ppc64
we don't see the error. Even using qemu 3.1 and machine 2.11 we still
g
On Tue, May 21, 2019 at 03:39:40PM +0100, Peter Maydell wrote:
> Hi; I have on my todo list the idea of some experimentation/prototyping
> of whether being able to write some components of QEMU in Rust would
> be (a) feasible (b) beneficial (c) fun to play around with even if
> it is likely that it
Thomas Huth writes:
> On 14/05/2019 20.41, Thomas Huth wrote:
>> On 14/05/2019 20.03, Markus Armbruster wrote:
>>> vubr_set_host() passes char values to isdigit(). Undefined behavior
>>> when the value is negative.
>>>
>>> Fix by using qemu_isdigit() instead.
>>>
>>> Signed-off-by: Markus Armbru
Hi
On Wed, May 22, 2019 at 7:23 AM Gerd Hoffmann wrote:
>
> On Tue, May 14, 2019 at 02:33:41PM +0200, Marc-André Lureau wrote:
> > Hi
> >
> > On Tue, May 14, 2019 at 2:10 PM Philippe Mathieu-Daudé
> > wrote:
> > >
> > > Hi Marc-André,
> > >
> > > On 5/14/19 12:41 PM, Marc-André Lureau wrote:
> >
On Tue, 21 May 2019 09:26:16 -0400
"Michael S. Tsirkin" wrote:
> On Tue, May 21, 2019 at 12:49:48PM +0100, Peter Maydell wrote:
> > On Tue, 21 May 2019 at 00:10, Michael S. Tsirkin wrote:
> > >
> > > The following changes since commit
> > > 2259637b95bef3116cc262459271de08e038cc66:
> > >
> >
1 - 100 of 326 matches
Mail list logo
