Hi Gred/Philippe,
@Philippe Mathieu-Daudé, thanks I found the alternative "ldq_le_dma".
Moving forward, for testing the new model. I ran through
qtest:usb-hcd-xhci-test.c, are there any other test which I need to consider as
first level validation ?
Regards,
Sai Pavan
> -Original
On Fri, 17 Jan 2020 19:16:08 +1000
David Gibson wrote:
> On Thu, Jan 16, 2020 at 07:29:02PM +0100, Greg Kurz wrote:
> > On Thu, 16 Jan 2020 13:14:35 +0100
> > Greg Kurz wrote:
> >
> > > On Thu, 16 Jan 2020 11:37:24 +0100
> > > Laurent Vivier wrote:
> > >
> > > > On 16/01/2020 09:48, Greg
On 1/17/20 11:46 AM, Igor Mammedov wrote:
On Wed, 15 Jan 2020 22:33:46 +0100 (CET)
BALATON Zoltan wrote:
[...]
v2 basically works the same as original code, except of that
instead of fixing up ram_size, it ask user to fix CLI to
the same value.
but I've not yet given up to keep current
On 17/01/2020 12.05, Christian Borntraeger wrote:
>
>
> On 17.01.20 11:38, Thomas Huth wrote:
>> On 16/01/2020 21.26, Cornelia Huck wrote:
>>> On Thu, 16 Jan 2020 15:19:13 -0500
>>> Matthew Rosato wrote:
>>>
On 1/16/20 7:20 AM, Thomas Huth wrote:
> The AIS feature has been disabled
On 1/17/20 4:28 PM, Dr. David Alan Gilbert wrote:
* Philippe Mathieu-Daudé (phi...@redhat.com) wrote:
On 12/12/19 5:39 PM, Dr. David Alan Gilbert (git) wrote:
From: Stefan Hajnoczi
When running with multiple threads it can be tricky to handle
FUSE_INIT/FUSE_DESTROY in parallel with other
* Philippe Mathieu-Daudé (phi...@redhat.com) wrote:
> On 12/12/19 5:39 PM, Dr. David Alan Gilbert (git) wrote:
> > From: Stefan Hajnoczi
> >
> > When running with multiple threads it can be tricky to handle
> > FUSE_INIT/FUSE_DESTROY in parallel with other request types or in
> > parallel with
On Fri, 17 Jan 2020 13:01:30 +0100
Christian Schoenebeck wrote:
> On Freitag, 17. Januar 2020 11:24:21 CET Greg Kurz wrote:
> > On Thu, 16 Jan 2020 22:39:19 +0100
> >
> > Christian Schoenebeck wrote:
> > > On Donnerstag, 16. Januar 2020 19:07:48 CET Greg Kurz wrote:
> > > > > The point here
** Summary changed:
- arm gic: interrupt model never 1 on non-mpcore and race condition in
gic_acknowledge_irq
+ arm gic: gic_acknowledge_irq doesn't clear line level for other cores for 1-n
level-sensitive interrupts and gic_clear_pending uses GIC_DIST_TEST_MODEL (even
on v2 where it always
* Paolo Bonzini (pbonz...@redhat.com) wrote:
> On 17/01/20 14:40, Michael S. Tsirkin wrote:
> > We don't really need v2 just to add a field. Compatibility is maintained
> > using feature bits. Adding that is a subject for another patch.
> > But I'm not sure I understand why does remote need to
On 17/01/20 15:25, Michael S. Tsirkin wrote:
> On Fri, Jan 17, 2020 at 02:58:47PM +0100, Paolo Bonzini wrote:
>> On 17/01/20 14:40, Michael S. Tsirkin wrote:
>>> We don't really need v2 just to add a field. Compatibility is maintained
>>> using feature bits. Adding that is a subject for another
* Juan Quintela (quint...@redhat.com) wrote:
> We transmit ram_addr_t always as uint64_t. Be consistent in its
> use (on 64bit system, it is always uint64_t problem is 32bits).
>
> Signed-off-by: Juan Quintela
(Note typo in subject )
Reviewed-by: Dr. David Alan Gilbert
> ---
>
On Fri, 17 Jan 2020 at 00:54, Richard Henderson
wrote:
>
> The following changes since commit 28b58f19d269633b3d14b6aebf1e92b3cd3ab56e:
>
> ui/gtk: Get display refresh rate with GDK version 3.22 or later (2020-01-16
> 14:03:45 +)
>
> are available in the Git repository at:
>
>
10.01.2020 22:41, Vladimir Sementsov-Ogievskiy wrote:
> Signed-off-by: Vladimir Sementsov-Ogievskiy
> ---
>
> CC: Cornelia Huck
> CC: Eric Blake
> CC: Kevin Wolf
> CC: Max Reitz
> CC: Greg Kurz
> CC: Stefan Hajnoczi
> CC: Stefano Stabellini
> CC: Anthony Perard
> CC: Paul Durrant
> CC:
On Mon, 2 Dec 2019 at 14:06, Cleber Rosa wrote:
>
> RFC: QEMU Gating CI
> ===
>
> This RFC attempts to address most of the issues described in
> "Requirements/GatinCI"[1]. An also relevant write up is the "State of
> QEMU CI as we enter 4.0"[2].
>
> The general approach is one to
On Fri 17 Jan 2020 12:51:04 PM CET, Kevin Wolf wrote:
>> > Now, what's wrong about the logic to avoid the RMW is that it assumes
>> > a fixed required alignment of 512. What it should do is looking at
>> > bs->file->bl.request_alignment and rounding accordingly.
>>
>> Yes.
>
> Who'll write the
From: Richard Henderson
During the conversion to decodetree, the setting of
ISSIs16Bit got lost. This causes the guest os to
incorrectly adjust trapping memory operations.
Cc: qemu-sta...@nongnu.org
Fixes: 46beb58efbb8a2a32 ("target/arm: Convert T16, load (literal)")
Reported-by: Jeff Kubascik
From: Martin Kaiser
Add an emulation for the RNGC random number generator and the compatible
RNGB variant. These peripherals are included (at least) in imx25 and
imx35 chipsets.
The emulation supports the initial self test, reseeding the prng and
reading random numbers.
Signed-off-by: Martin
From: Philippe Mathieu-Daudé
By calling qdev_pass_gpios() we don't need to hold a copy of the
IRQs from the INTC into the SoC state.
Instead of filling an array of qemu_irq and passing it around, we
can now directly call qdev_get_gpio_in() on the SoC.
Signed-off-by: Philippe Mathieu-Daudé
From: Philippe Mathieu-Daudé
These definitions are specific to the A10 SoC and don't need
to be exported to the different Allwinner peripherals.
Signed-off-by: Philippe Mathieu-Daudé
Message-id: 20191230110953.25496-4-f4...@amsat.org
Signed-off-by: Peter Maydell
Reviewed-by: Peter Maydell
From: Jeff Kubascik
The IAR0/IAR1 register is used to acknowledge an interrupt - a read of the
register activates the highest priority pending interrupt and provides its
interrupt ID. Activating an interrupt can change the CPU's virtual interrupt
state - this change makes sure the virtual irq
From: Alistair Francis
Signed-off-by: Alistair Francis
Reviewed-by: Peter Maydell
Message-id:
1d145c4c13e5fa140caf131232a6f524c88fcd72.1576658572.git.alist...@alistair23.me
Signed-off-by: Peter Maydell
---
hw/arm/Makefile.objs | 1 +
include/hw/arm/stm32f405_soc.h | 73
From: Jeff Kubascik
The IL bit is set for 32-bit instructions, thus passing false
with the is_16bit parameter to syn_data_abort_with_iss() makes
a syn mask that always has the IL bit set.
Pass is_16bit as true to make the initial syn mask have IL=0,
so that the final IL value comes from or'ing
From: Masahiro Yamada
According to the specification "Semihosting for AArch32 and Aarch64",
the SYS_OPEN operation should return:
- A nonzero handle if the call is successful
- -1 if the call is not successful
So, it should never return 0.
Prior to commit 35e9a0a8ce4b ("target/arm/arm-semi:
From: Philippe Mathieu-Daudé
This test boots a Linux kernel on a CubieBoard and verify
the serial output is working.
The kernel image and DeviceTree blob are built by the Armbian
project (based on Debian):
https://docs.armbian.com/Developer-Guide_Build-Preparation/
The cpio image used comes
From: Philippe Mathieu-Daudé
We won't reuse the CPU IRQ/FIQ variables. Simplify by calling
qdev_get_gpio_in() in place.
Signed-off-by: Philippe Mathieu-Daudé
Message-id: 20191230110953.25496-6-f4...@amsat.org
Signed-off-by: Peter Maydell
Reviewed-by: Peter Maydell
---
hw/arm/allwinner-a10.c
From: Jeff Kubascik
The wfi instruction can be configured to be trapped by a higher exception
level, such as the EL2 hypervisor. When the instruction is trapped, the
program counter should contain the address of the wfi instruction that
caused the exception. The program counter is adjusted for
From: Alistair Francis
Signed-off-by: Alistair Francis
Reviewed-by: Peter Maydell
Message-id:
dad8d8d47f7625913e35e27a1c00f603a6b08f9a.1576658572.git.alist...@alistair23.me
Signed-off-by: Peter Maydell
---
hw/arm/Makefile.objs | 1 +
hw/arm/netduinoplus2.c | 52
From: Alistair Francis
Signed-off-by: Alistair Francis
Reviewed-by: Peter Maydell
Message-id:
49b01423a09cef2ca832ff73a84a996568f1a8fc.1576658572.git.alist...@alistair23.me
Signed-off-by: Peter Maydell
---
hw/misc/Makefile.objs | 1 +
include/hw/misc/stm32f4xx_syscfg.h | 61
From: Alistair Francis
Signed-off-by: Alistair Francis
Reviewed-by: Peter Maydell
Message-id:
ef941d59fd8658589d34ed432e1d6dfdcf7fb1d0.1576658572.git.alist...@alistair23.me
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: Peter Maydell
---
hw/misc/Makefile.objs| 1 +
From: Philippe Mathieu-Daudé
The kernel image and DeviceTree blob are built by the Armbian
project (based on Debian):
https://docs.armbian.com/Developer-Guide_Build-Preparation/
The cpio image used comes from the linux-build-test project:
https://github.com/groeck/linux-build-test
If ARM is a
at:
https://git.linaro.org/people/pmaydell/qemu-arm.git
tags/pull-target-arm-20200117-1
for you to fetch changes up to 1a1fbc6cbb34c26d43d8360c66c1d21681af14a9:
target/arm: Set ISSIs16Bit in make_issinfo (2020-01-17 14:27:16 +
On Fri, Jan 17, 2020 at 02:58:47PM +0100, Paolo Bonzini wrote:
> On 17/01/20 14:40, Michael S. Tsirkin wrote:
> > We don't really need v2 just to add a field. Compatibility is maintained
> > using feature bits. Adding that is a subject for another patch.
> > But I'm not sure I understand why does
On 1/10/20 1:41 PM, Vladimir Sementsov-Ogievskiy wrote:
It's wrong to use same err object as errp parameter for several
function calls without intermediate checking for error: we'll crash if
try to set err object twice.
Fix that, using new ERRP_AUTO_PROPAGATE macro.
Signed-off-by: Vladimir
On 1/10/20 1:41 PM, Vladimir Sementsov-Ogievskiy wrote:
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
Rather light on the commit message. If nothing else, a comment about
typical command-line usage would be helpful (yes, it's in the patch
body, but sometimes I just refer to git log).
On 1/10/20 1:41 PM, Vladimir Sementsov-Ogievskiy wrote:
Here is introduced ERRP_AUTO_PROPAGATE macro, to be used at start of
functions with errp OUT parameter.
s/with/with an/
It has three goals:
1. Fix issue with error_fatal & error_prepend/error_append_hint: user
maybe s/&/and/ so it
In many cases the target of a convert operation is a newly provisioned
target that the user knows is blank (filled with zeroes). In this
situation there is no requirement for qemu-img to wastefully zero out
the entire device.
Add a new option, --target-is-zero, allowing the user to indicate that
On Fri, 10 Jan 2020 at 16:16, Alex Bennée wrote:
>
> Bug: https://bugs.launchpad.net/bugs/1859021
>
> Signed-off-by: Alex Bennée
> ---
> tests/tcg/aarch64/system/vtimer.c | 80 +++
> tests/tcg/aarch64/Makefile.softmmu-target | 4 ++
> 2 files changed, 84
On 1/17/20 2:56 PM, Juan Quintela wrote:
We transmit ram_addr_t always as uint64_t. Be consistent in its
use (on 64bit system, it is always uint64_t problem is 32bits).
Signed-off-by: Juan Quintela
---
migration/ram.c | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
Am 17.01.2020 um 13:20 hat Markus Armbruster geschrieben:
> > @@ -579,9 +580,16 @@ void monitor_cleanup(void)
> > }
> > qemu_mutex_unlock(_lock);
> >
> > -/* QEMUBHs needs to be deleted before destroying the I/O thread */
> > -qemu_bh_delete(qmp_dispatcher_bh);
> > -
On Fri, 17 Jan 2020 14:52:35 +0100
Thomas Huth wrote:
> On 17/01/2020 14.33, Igor Mammedov wrote:
> > On Fri, 17 Jan 2020 12:14:11 +0100
> > Thomas Huth wrote:
> >
> >> On 16/01/2020 18.06, Igor Mammedov wrote:
> >>> On Thu, 16 Jan 2020 17:35:32 +0100
> >>> Thomas Huth wrote:
> >>>
>
On Thu, 19 Dec 2019 at 04:06, Gavin Shan wrote:
> This supports NMI injection for virtual machine and currently it's only
> supported on GICv3 controller, which is emulated by qemu or host kernel.
> The design is highlighted as below:
>
>* The NMI is identified by its priority (0x20). In the
On 12/12/19 5:37 PM, Dr. David Alan Gilbert (git) wrote:
From: Stefan Hajnoczi
Do not expose lo_dirp pointers to clients.
Signed-off-by: Stefan Hajnoczi
---
tools/virtiofsd/passthrough_ll.c | 103 +++
1 file changed, 76 insertions(+), 27 deletions(-)
diff
Hi
On Thu, Dec 12, 2019 at 10:05 PM Dr. David Alan Gilbert (git)
wrote:
>
> From: "Dr. David Alan Gilbert"
>
> If a new setmemtable command comes in once the vhost threads are
> running, it will remap the guests address space and the threads
> will now be looking in the wrong place.
>
>
On 17/01/20 14:40, Michael S. Tsirkin wrote:
> We don't really need v2 just to add a field. Compatibility is maintained
> using feature bits. Adding that is a subject for another patch.
> But I'm not sure I understand why does remote need to know about alignment.
> This patch seems to handle it
We transmit ram_addr_t always as uint64_t. Be consistent in its
use (on 64bit system, it is always uint64_t problem is 32bits).
Signed-off-by: Juan Quintela
---
migration/ram.c | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/migration/ram.c b/migration/ram.c
On 1/17/20 4:58 AM, Max Reitz wrote:
Add a test that all fields in "qemu-img snapshot -l"s output are
separated by spaces.
Signed-off-by: Max Reitz
---
tests/qemu-iotests/284 | 76 ++
tests/qemu-iotests/284.out | 8
tests/qemu-iotests/group |
On 12/12/19 5:38 PM, Dr. David Alan Gilbert (git) wrote:
From: Stefan Hajnoczi
This reference counter plays a specific role in the FUSE protocol. It's
not a generic object reference counter and the FUSE kernel code calls it
"nlookup".
Signed-off-by: Stefan Hajnoczi
---
On 17/01/2020 14.33, Igor Mammedov wrote:
> On Fri, 17 Jan 2020 12:14:11 +0100
> Thomas Huth wrote:
>
>> On 16/01/2020 18.06, Igor Mammedov wrote:
>>> On Thu, 16 Jan 2020 17:35:32 +0100
>>> Thomas Huth wrote:
>>>
On 15/01/2020 16.07, Igor Mammedov wrote:
> Use GString to pass
On 12/12/19 5:38 PM, Dr. David Alan Gilbert (git) wrote:
From: Stefan Hajnoczi
Introduce lo_dirp_put() so that FUSE_RELEASEDIR does not cause
use-after-free races with other threads that are accessing lo_dirp.
Also make lo_releasedir() atomic to prevent FUSE_RELEASEDIR racing with
itself.
On 1/17/20 4:58 AM, Max Reitz wrote:
When printing the snapshot list (e.g. with qemu-img snapshot -l), the VM
size field is only seven characters wide. As of de38b5005e9, this is
not necessarily sufficient: We generally print three digits, and this
may require a decimal point. Also, the unit
On 12/16/19 10:59 AM, Markus Armbruster wrote:
Extra nesting is merely another set of braces in QMP. It's bloody
annoying in QAPIfied CLI using dotted keys syntax. Example:
QMP command
{"execute": "chardev-add",
Let's start with trying to understand the sources of extra nesting.
On Fri, Jan 17, 2020 at 5:41 PM Stefan Berger wrote:
>
> On 1/17/20 8:31 AM, Marc-André Lureau wrote:
> > Hi
> >
> > On Wed, Jan 8, 2020 at 8:14 PM Stefan Berger wrote:
> >> From: Stefan Berger
> >>
> >> Extend the tpm_spapr frontend with VM suspend and resume support.
> >>
> >> Signed-off-by:
On Fri, 10 Jan 2020 at 20:39, Guenter Roeck wrote:
>
> The Exynos4210 serial driver uses an interrupt line to signal if receive
> data is available. Connect that interrupt with the DMA controller's
> 'peripheral busy' gpio pin.
>
> Signed-off-by: Guenter Roeck
> ---
> hw/arm/exynos4210.c | 39
On Fri, Jan 17, 2020 at 01:52:53PM +0100, Christian Schoenebeck wrote:
> On Freitag, 17. Januar 2020 07:09:26 CET pannengy...@huawei.com wrote:
> > From: Pan Nengyuan
> >
> > v->vq forgot to cleanup in virtio_9p_device_unrealize, the memory leak
> > stack is as follow:
> >
> > Direct leak of
On Fri, 10 Jan 2020 at 20:39, Guenter Roeck wrote:
>
> To support receive DMA, we need to inform the DMA controller if receive data
> is available. Otherwise the DMA controller keeps requesting data, causing
> receive errors.
>
> Implement this using an interrupt line. The instantiating code then
On 12/12/19 5:39 PM, Dr. David Alan Gilbert (git) wrote:
From: Stefan Hajnoczi
Now that lo_destroy() is serialized we can call unref_inode() so that
all inode resources are freed.
Signed-off-by: Stefan Hajnoczi
Signed-off-by: Dr. David Alan Gilbert
---
tools/virtiofsd/passthrough_ll.c |
On Fri, 10 Jan 2020 at 20:39, Guenter Roeck wrote:
The subject just says "implement receive FIFO", but the
existing code clearly has an "Exynos4210UartFIFO rx"
which it does some storing and retrieving data from.
Could the patch be more accurately described as something
like "Implement
On Fri, Jan 17, 2020 at 01:52:44PM +0100, Paolo Bonzini wrote:
> On 16/01/20 21:24, Dr. David Alan Gilbert (git) wrote:
> > +if (dev->vhost_ops->backend_type == VHOST_BACKEND_TYPE_USER) {
> > +/* Round the section to it's page size */
> > +/* First align the start down to a
On 1/17/20 8:31 AM, Marc-André Lureau wrote:
Hi
On Wed, Jan 8, 2020 at 8:14 PM Stefan Berger wrote:
From: Stefan Berger
Extend the tpm_spapr frontend with VM suspend and resume support.
Signed-off-by: Stefan Berger
---
hw/tpm/tpm_spapr.c | 67
On 12/12/19 5:39 PM, Dr. David Alan Gilbert (git) wrote:
From: Stefan Hajnoczi
When running with multiple threads it can be tricky to handle
FUSE_INIT/FUSE_DESTROY in parallel with other request types or in
parallel with themselves. Serialize FUSE_INIT and FUSE_DESTROY so that
malicious
On Fri, 17 Jan 2020 12:14:11 +0100
Thomas Huth wrote:
> On 16/01/2020 18.06, Igor Mammedov wrote:
> > On Thu, 16 Jan 2020 17:35:32 +0100
> > Thomas Huth wrote:
> >
> >> On 15/01/2020 16.07, Igor Mammedov wrote:
> >>> Use GString to pass argument to make_cli() so that it would be easy
> >>>
On 12/12/19 5:39 PM, Dr. David Alan Gilbert (git) wrote:
From: "Dr. David Alan Gilbert"
lo_destroy was relying on some implicit knowledge of the locking;
we can avoid this if we create an unref_inode that doesn't take
the lock and then grab it for the whole of the lo_destroy.
Suggested-by:
We can unref both old/new inodes with the same mutex lock.
Signed-off-by: Philippe Mathieu-Daudé
---
Based-on: <20191212163904.159893-1-dgilb...@redhat.com>
"virtiofs daemon"
https://www.mail-archive.com/qemu-devel@nongnu.org/msg664652.html
tools/virtiofsd/passthrough_ll.c | 6 --
1 file
On 12/12/19 5:39 PM, Dr. David Alan Gilbert (git) wrote:
From: Stefan Hajnoczi
Add an option to control the size of the thread pool. Requests are now
processed in parallel by default.
Signed-off-by: Stefan Hajnoczi
---
tools/virtiofsd/fuse_i.h| 1 +
The following registers are given in QEMU debug trace with "-d cpu"
parameter.
pc 1000
mhartid
mstatus
mip 0x0
mie
mideleg
medeleg
mtvec
mepc
On Wed, Jan 8, 2020 at 8:13 PM Stefan Berger wrote:
>
> From: Stefan Berger
>
> Signed-off-by: Stefan Berger
(trivial conflict on master)
Reviewed-by: Marc-André Lureau
> ---
> hw/ppc/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/hw/ppc/Kconfig b/hw/ppc/Kconfig
> index
On Fri, 10 Jan 2020 at 20:39, Guenter Roeck wrote:
>
> Replace debug code with tracing to aid debugging.
>
> Signed-off-by: Guenter Roeck
> ---
> hw/char/exynos4210_uart.c | 96 ---
> hw/char/trace-events | 17 +++
> 2 files changed, 47
Hi
On Wed, Jan 8, 2020 at 8:14 PM Stefan Berger wrote:
>
> From: Stefan Berger
>
> Extend the tpm_spapr frontend with VM suspend and resume support.
>
> Signed-off-by: Stefan Berger
> ---
> hw/tpm/tpm_spapr.c | 67 -
> hw/tpm/trace-events | 2 ++
>
On Fri, 10 Jan 2020 at 20:39, Guenter Roeck wrote:
>
> First parameter to exynos4210_get_irq() is not the SPI port number,
> but the interrupt group number. Interrupt groups are 20 for mdma
> and 21 for pdma. Interrupts are not inverted. Controllers support 32
> events (pdma) or 31 events (mdma).
On Fri, 10 Jan 2020 at 20:39, Guenter Roeck wrote:
>
> Replace debug logging code with tracing.
>
> Signed-off-by: Guenter Roeck
> ---
> hw/dma/pl330.c | 88 +++--
> hw/dma/trace-events | 24 +
> +static void pl330_hexdump(uint8_t *buf,
On Thu, Jan 16, 2020 at 06:36:38PM +0100, Kashyap Chamarthy wrote:
[...]
> (2) There are _three_ variants[+] of CascadeLake CPUs, with different
> stepping levels: 5, 6, and 7. To quite wikichip.org[*]:
s/quite/quote/
>
> "note that while steppings 6 & 7 are fully mitigated,
On Thu, Jan 16, 2020 at 19:25:52 +0100, Philippe Mathieu-Daudé wrote:
> On 1/16/20 6:42 PM, Leif Lindholm wrote:
> > Update address to reflect new employer.
> >
> > Signed-off-by: Leif Lindholm
> > ---
> > MAINTAINERS | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff
On 1/10/20 1:41 PM, Vladimir Sementsov-Ogievskiy wrote:
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
Sparse commit message; it might be nice (for future 'git log'
greppability) to at least mention the names of the functions being added.
+/*
+ * Functions to clean Error **errp: call
On Fri, 17 Jan 2020 12:11:47 +0100
Cornelia Huck wrote:
> If the kernel irqchip has been disabled, we don't want the
> {add,release}_adapter_routes routines to call any kvm_irqchip_*
> interfaces, as they may rely on an irqchip actually having been
> created. Just take a quick exit in that case
On Thu, 16 Jan 2020 at 01:40, Richard Henderson
wrote:
>
> For version 2, drop the -static and -pie changes,
> i.e. patches 1-7 from version 1.
>
> I'll come back to those after the required linux-user changes are
> upstream. In the meantime, it's still a large enough set of patches.
>
>
> r~
>
On 1/17/20 10:50 AM, Igor Mammedov wrote:
On Thu, 16 Jan 2020 19:22:08 +0100
Philippe Mathieu-Daudé wrote:
On 1/16/20 6:26 PM, Igor Mammedov wrote:
If the user provided too large a RAM size, the code used to
complain and trim it to the max size. Now tht RAM is allocated by
generic code,
Am Fri, 17 Jan 2020 11:27:59 +0100
schrieb Paolo Bonzini :
> It doesn't even try to be compatible for all existing and future guests.
This looks like the underlying bug.
What would future domUs lose if 'xenfv' would be locked to 'pc-i440fx-3.0'?
Olaf
pgpcvh3cEqCHz.pgp
Description: Digitale
On Freitag, 17. Januar 2020 07:09:27 CET pannengy...@huawei.com wrote:
> From: Pan Nengyuan
>
> Use virtio_delete_queue to make it more clear.
>
> Signed-off-by: Pan Nengyuan
> ---
> Changes V2 to V1:
> - replace virtio_del_queue to virtio_delete_queue to make it more clear.
> ---
>
On Wed, Jan 8, 2020 at 8:11 PM Stefan Berger wrote:
>
> From: Stefan Berger
>
> For devices that cannot be statically initialized, implement a
> get_dt_compatible() callback that allows us to ask the device for
> the 'compatible' value.
>
> Signed-off-by: Stefan Berger
Reviewed-by: Marc-André
On Freitag, 17. Januar 2020 07:09:26 CET pannengy...@huawei.com wrote:
> From: Pan Nengyuan
>
> v->vq forgot to cleanup in virtio_9p_device_unrealize, the memory leak
> stack is as follow:
>
> Direct leak of 14336 byte(s) in 2 object(s) allocated from:
> #0 0x7f819ae43970
On 16/01/20 21:24, Dr. David Alan Gilbert (git) wrote:
> +if (dev->vhost_ops->backend_type == VHOST_BACKEND_TYPE_USER) {
> +/* Round the section to it's page size */
> +/* First align the start down to a page boundary */
> +size_t mrs_page =
* no-re...@patchew.org (no-re...@patchew.org) wrote:
> Patchew URL:
> https://patchew.org/QEMU/20200116202414.157959-1-dgilb...@redhat.com/
>
>
>
> Hi,
>
> This series seems to have some coding style problems. See output below for
> more information:
>
> Message-id:
On 1/17/20 10:46 AM, David Gibson wrote:
> On Thu, Jan 09, 2020 at 05:33:45PM +0100, Cédric Le Goater wrote:
>> The Processor Control facility POWER8 processors and later provides
>> a mechanism for the hypervisor to send messages to other threads
>> in the system (msgsnd instruction) and cause
Juan Quintela wrote:
> Peter Maydell wrote:
>> On Tue, 14 Jan 2020 at 12:53, Juan Quintela wrote:
>>
>> I think you need to find a system which has 32-bit ram_addr_t
>> and test this, because this is about the fourth time round
>> for this patchset failing on this configuration.
>
> That is
* Paolo Bonzini (pbonz...@redhat.com) wrote:
> On 13/01/20 18:36, Dr. David Alan Gilbert (git) wrote:
> >
> > Hyperv's synic (that we emulate) is a feature that allows the guest
> > to place some magic (4k) pages of RAM anywhere it likes in GPA.
> > This confuses vhost's RAM section merging when
On Fri, Jan 17, 2020 at 07:27:48PM +1000, David Gibson wrote:
> On Fri, Jan 10, 2020 at 12:13:43PM -0300, Fabiano Rosas wrote:
> > For single stepping (via KVM) of a guest vcpu to work, KVM needs not
> > only to support the SET_GUEST_DEBUG ioctl but to also recognize the
> >
On 17/01/2020 13.26, Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert"
>
> vhost-user-bridge isn't actually a test, it's just a helper
> (that should probably move somewhere else) - but the build was
> broken in the qtest move.
>
> Fixes: 833884f37adc9f125fa2
> Signed-off-by:
On Thu, Jan 16, 2020 at 07:29:02PM +0100, Greg Kurz wrote:
> On Thu, 16 Jan 2020 13:14:35 +0100
> Greg Kurz wrote:
>
> > On Thu, 16 Jan 2020 11:37:24 +0100
> > Laurent Vivier wrote:
> >
> > > On 16/01/2020 09:48, Greg Kurz wrote:
> > > > On Wed, 15 Jan 2020 19:10:37 +0100
> > > > Laurent
On Thu, Jan 09, 2020 at 05:33:46PM +0100, Cédric Le Goater wrote:
> The privileged message send and clear instructions (msgsndp & msgclrp)
> are privileged, but will generate a hypervisor facility unavailable
> exception if not enabled in the HFSCR and executed in privileged
> non-hypervisor
From: "Dr. David Alan Gilbert"
vhost-user-bridge isn't actually a test, it's just a helper
(that should probably move somewhere else) - but the build was
broken in the qtest move.
Fixes: 833884f37adc9f125fa2
Signed-off-by: Dr. David Alan Gilbert
---
tests/Makefile.include | 1 +
On Fri, Jan 10, 2020 at 12:13:42PM -0300, Fabiano Rosas wrote:
> The kvm_handle_debug function can return 0 to go back into the guest
> or return 1 to notify the gdbstub thread and pass control to GDB.
>
> Signed-off-by: Fabiano Rosas
Good change regardless of the rest of the series. Applied
On Thu, Jan 09, 2020 at 05:33:45PM +0100, Cédric Le Goater wrote:
> The Processor Control facility POWER8 processors and later provides
> a mechanism for the hypervisor to send messages to other threads
> in the system (msgsnd instruction) and cause hypervisor-level
> exceptions. Privileged
On Fri, Jan 10, 2020 at 12:13:43PM -0300, Fabiano Rosas wrote:
> For single stepping (via KVM) of a guest vcpu to work, KVM needs not
> only to support the SET_GUEST_DEBUG ioctl but to also recognize the
> KVM_GUESTDBG_SINGLESTEP bit in the control field of the
> kvm_guest_debug struct.
>
> This
Peter Maydell wrote:
> On Tue, 14 Jan 2020 at 12:53, Juan Quintela wrote:
>>
>> The following changes since commit 3c8a6575985b1652b45bfa670b5e1907d642cfa0:
>>
>> Merge remote-tracking branch
>> 'remotes/kraxel/tags/usb-20200113-pull-request' into staging
>> (2020-01-13 14:19:57 +)
>>
>>
Kevin Wolf writes:
> This moves the QMP dispatcher to a coroutine and runs all QMP command
> handlers that declare 'coroutine': true in coroutine context so they
> can avoid blocking the main loop while doing I/O or waiting for other
> events.
>
> For commands that are not declared safe to run
On Fri, Jan 17, 2020 at 11:09:07AM +, Peter Maydell wrote:
> On Fri, 17 Jan 2020 at 07:22, Philippe Mathieu-Daudé
> wrote:
> >
> > Hi Peter,
> >
> > On 1/16/20 5:46 PM, Peter Maydell wrote:
> > > On Wed, 8 Jan 2020 at 11:32, Dongjiu Geng wrote:
> > >>
> > >> I and Xiang are willing to
Am 16.01.20 um 21:26 schrieb Dr. David Alan Gilbert:
> * Peter Lieven (p...@kamp.de) wrote:
>> Am 16.01.20 um 13:47 schrieb Peter Lieven:
>>> Am 13.01.20 um 17:25 schrieb Peter Lieven:
Am 09.01.20 um 19:44 schrieb Dr. David Alan Gilbert:
> * Peter Lieven (p...@kamp.de) wrote:
>> Am
On Tue, 14 Jan 2020 at 16:02, Greg Kurz wrote:
>
> The following changes since commit 3c8a6575985b1652b45bfa670b5e1907d642cfa0:
>
> Merge remote-tracking branch
> 'remotes/kraxel/tags/usb-20200113-pull-request' into staging (2020-01-13
> 14:19:57 +)
>
> are available in the Git repository
On 17/01/2020 12:49, Greg Kurz wrote:
> On Wed, 15 Jan 2020 19:26:18 +0100
> Laurent Vivier wrote:
>
>> On 15/01/2020 19:10, Laurent Vivier wrote:
>>> Hi,
>>>
>>> On 15/01/2020 18:48, Greg Kurz wrote:
Migration can potentially race with CAS reboot. If the migration thread
completes
On Tue, Jan 7, 2020 at 10:21 PM Alex Bennée wrote:
>
>
> Georg Kotheimer writes:
>
> > The size of the FPU registers depends solely on the floating point
> > extensions supported by the target architecture.
> > However, in the previous implementation the floating point register
> > size was
101 - 200 of 282 matches
Mail list logo
