Patchew URL: https://patchew.org/QEMU/20200529134523.8477-1-arm...@redhat.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 20200529134523.8477-1-arm...@redhat.com
Subject: [PATCH v2 00/58] qdev: Rework how we plug into the
Markus Armbruster writes:
> Replace
>
> dev = isa_create(bus, type_name);
> ...
> qdev_init_nofail(dev);
>
> by
>
> dev = isa_new(type_name);
> ...
> isa_realize_and_unref(dev, bus, _fatal);
>
> Recent commit "qdev: New qdev_new(), qdev_realize(), etc." explains
> why.
>
Patchew URL: https://patchew.org/QEMU/20200529134523.8477-1-arm...@redhat.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 20200529134523.8477-1-arm...@redhat.com
Subject: [PATCH v2 00/58] qdev: Rework how we plug into the
Patchew URL: https://patchew.org/QEMU/20200529134523.8477-1-arm...@redhat.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 20200529134523.8477-1-arm...@redhat.com
Subject: [PATCH v2 00/58] qdev: Rework how we plug into the
Patchew URL: https://patchew.org/QEMU/20200529221450.26673-1-alx...@bu.edu/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 20200529221450.26673-1-alx...@bu.edu
Subject: [PATCH v3 0/2] fuzz: Skip QTest serialization
Type: series
Patchew URL: https://patchew.org/QEMU/20200529134523.8477-1-arm...@redhat.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 20200529134523.8477-1-arm...@redhat.com
Subject: [PATCH v2 00/58] qdev: Rework how we plug into the
Tied again with same .vdi as block device for 4 hours, didn't experience
further problems. don't know how to reproduce the issue again, even
don't know if has been fixed with any software update.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
Initialize the CPU interface registers also
for Cortex-A15 and Cortex-A7 CPU models, in
the same way as done for 64bit CPU models.
This fixes usage of GICv3 in virtualization
contexts in 32bit configurations.
Signed-off-by: Adam Lackorzynski
---
target/arm/cpu.c | 6 ++
1 file changed, 6
outl 0xcf8 0x8000fa24
outl 0xcfc 0xe106c000 (Writes e106c00 to BAR5 for 0:31:2)
outl 0xcf8 0x8000fa04
outw 0xcfc 0x7 (Enables BM, Memory IO and PIO for 0:31:2)
outl 0xcf8 0x8000fb20 (Enables 0:31:3, I guess? My PCI knowledge is
iffy. We set the enable bit and select BAR4, but then we don't
Patchew URL:
https://patchew.org/QEMU/20200529180025.169097-1-...@tribudubois.net/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 20200529180025.169097-1-...@tribudubois.net
Subject: [PATCH] hw/net/imx_fec.c: Convert debug
On 5/29/20 3:28 PM, Stefan Berger wrote:
From: Stefan Berger
Do not build a TCPA table for TPM 2 anymore but create the log area when
building the TPM2 table. The TCPA table is only needed for TPM 1.2.
Specs are here:
On Fri, 29 May 2020, Richard W.M. Jones wrote:
> On Fri, May 29, 2020 at 08:58:06AM -0500, Eric Blake wrote:
> > On 5/29/20 8:50 AM, Daniel P. Berrangé wrote:
> >
> > >>>(2) You need to persuade qemu's NBD client to read from a WebSocket.
> > >>>I didn't really know anything about WebSockets
On Thu, May 21, 2020 at 01:42:46PM +1000, David Gibson wrote:
> A number of hardware platforms are implementing mechanisms whereby the
> hypervisor does not have unfettered access to guest memory, in order
> to mitigate the security impact of a compromised hypervisor.
>
> AMD's SEV implements
The QTest server usually parses ASCII commands from clients. Since we
fuzz within the QEMU process, skip the QTest serialization and server
for most QTest commands. Leave the option to use the ASCII protocol, to
generate readable traces for crash reproducers.
Inspired-by: Philippe Mathieu-Daudé
Signed-off-by: Alexander Bulekov
---
tests/qtest/fuzz/fuzz.c | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/tests/qtest/fuzz/fuzz.c b/tests/qtest/fuzz/fuzz.c
index 88ac88bca9..21cdee53db 100644
--- a/tests/qtest/fuzz/fuzz.c
+++ b/tests/qtest/fuzz/fuzz.c
@@ -94,7
In the same vein as Philippe's patch:
https://patchew.org/QEMU/20200528165303.1877-1-f4...@amsat.org/
This uses linker trickery to wrap calls to libqtest functions and
directly call the corresponding read/write functions, rather than
relying on the ASCII-serialized QTest protocol.
v2: applies
This is missing the actual wrapper functions... Sending v3
On 200529 1402, Alexander Bulekov wrote:
> The QTest server usually parses ASCII commands from clients. Since we
> fuzz within the QEMU process, skip the QTest serialization and server
> for most QTest commands. Leave the option to use
On Thu, May 21, 2020 at 4:23 AM LIU Zhiwei wrote:
>
> Signed-off-by: LIU Zhiwei
> Reviewed-by: Richard Henderson
Reviewed-by: Alistair Francis
Alistair
> ---
> target/riscv/helper.h | 3 ++
> target/riscv/insn32.decode | 2 ++
>
On Thu, May 21, 2020 at 4:21 AM LIU Zhiwei wrote:
>
> Signed-off-by: LIU Zhiwei
> Reviewed-by: Richard Henderson
Reviewed-by: Alistair Francis
Alistair
> ---
> target/riscv/helper.h | 10 +++
> target/riscv/insn32.decode | 4 +++
>
On Fri, 29 May 2020 02:00:46 +0530
Kirti Wankhede wrote:
> Hi,
>
> This patch set adds:
> * IOCTL VFIO_IOMMU_DIRTY_PAGES to get dirty pages bitmap with
> respect to IOMMU container rather than per device. All pages pinned by
> vendor driver through vfio_pin_pages external API has to be
On Thu, May 21, 2020 at 4:19 AM LIU Zhiwei wrote:
>
> Signed-off-by: LIU Zhiwei
> Reviewed-by: Richard Henderson
Reviewed-by: Alistair Francis
Alistair
> ---
> target/riscv/helper.h | 7 +++
> target/riscv/insn32.decode | 2 ++
>
On Thu, May 21, 2020 at 4:17 AM LIU Zhiwei wrote:
>
> Signed-off-by: LIU Zhiwei
> Reviewed-by: Richard Henderson
Reviewed-by: Alistair Francis
Alistair
> ---
> target/riscv/helper.h | 33 +++
> target/riscv/insn32.decode | 8 +++
>
On Thu, May 21, 2020 at 4:15 AM LIU Zhiwei wrote:
>
> Signed-off-by: LIU Zhiwei
> Reviewed-by: Richard Henderson
Reviewed-by: Alistair Francis
Alistair
> ---
> target/riscv/helper.h | 11 ++
> target/riscv/insn32.decode | 5 +++
>
SafeStack is a stack protection technique implemented in llvm. It is
enabled with a -fsanitize flag.
iotests are currently disabled when any -fsanitize option is used,
because such options tend to produce additional warnings and false
positives.
While common -fsanitize options are used to verify
On Thu, May 21, 2020 at 4:13 AM LIU Zhiwei wrote:
>
> Signed-off-by: LIU Zhiwei
> Reviewed-by: Richard Henderson
Reviewed-by: Alistair Francis
Alistair
> ---
> target/riscv/helper.h | 11 ++
> target/riscv/insn32.decode | 5 +++
>
On Thu, May 21, 2020 at 4:09 AM LIU Zhiwei wrote:
>
> Signed-off-by: LIU Zhiwei
Reviewed-by: Alistair Francis
Alistair
> ---
> target/riscv/helper.h | 4 +++
> target/riscv/insn32.decode | 2 ++
> target/riscv/insn_trans/trans_rvv.inc.c | 38
This adds support to basevm.py so that we always
drain the console chars. This makes use of
support added in an earlier commit that allows
QEMUMachine to use the ConsoleSocket.
This is a workaround we found was needed since
there is a known issue where QEMU will hang waiting
for console
This patch adds a flag to enable/disable the SafeStack instrumentation
provided by LLVM.
On enable, make sure that the compiler supports the flags, and that we
are using the proper coroutine implementation (coroutine-ucontext).
On disable, explicitly disable the option if it was enabled by
LLVM's SafeStack instrumentation does not yet support programs that make
use of the APIs in ucontext.h
With the current implementation of coroutine-ucontext, the resulting
binary is incorrect, with different coroutines sharing the same unsafe
stack and producing undefined behavior at runtime.
This
We add the ConsoleSocket object, which has a socket interface
and which will consume all arriving characters on the
socket, placing them into an in memory buffer.
This will also provide those chars via recv() as
would a regular socket.
ConsoleSocket also has the option of dumping
the console bytes
Current implementation of LLVM's SafeStack is not compatible with
code that uses an alternate stack created with sigaltstack().
Since coroutine-sigaltstack relies on sigaltstack(), it is not
compatible with SafeStack. The resulting binary is incorrect, with
different coroutines sharing the same
LLVM supports SafeStack instrumentation to protect against stack buffer
overflows, since version 3.7
>From https://clang.llvm.org/docs/SafeStack.html:
"It works by separating the program stack into two distinct regions: the
safe stack and the unsafe stack. The safe stack stores return addresses,
ubuntu.aarch64 provides a script to create an Ubuntu 18.04 VM.
Another new file is also added aarch64vm.py, which is a module with
common methods used by aarch64 VMs, such as how to create the
flash images.
Signed-off-by: Robert Foley
Reviewed-by: Peter Puhov
---
configure |
This change converts existing scripts to using for example self.ROOT_PASS,
to self._config['root_pass'].
We made similar changes for GUEST_USER, and GUEST_PASS.
This allows us also to remove the change in basevm.py,
which adds __getattr__ for backwards compatibility.
Signed-off-by: Robert Foley
On Thu, May 21, 2020 at 4:11 AM LIU Zhiwei wrote:
>
> Signed-off-by: LIU Zhiwei
> Reviewed-by: Richard Henderson
Reviewed-by: Alistair Francis
Alistair
> ---
> target/riscv/helper.h | 13 ++
> target/riscv/insn32.decode | 4 +++
>
centos.aarch64 creates a CentOS 8 image.
Also added a new kickstart script used to build the centos.aarch64 image.
Signed-off-by: Robert Foley
Reviewed-by: Peter Puhov
Reviewed-by: Alex Bennée
---
tests/vm/Makefile.include| 3 +-
tests/vm/centos-8-aarch64.ks | 51
This allows for waiting for completion of arbitrary commands.
Signed-off-by: Robert Foley
Reviewed-by: Peter Puhov
Reviewed-by: Alex Bennée
---
tests/vm/basevm.py | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/tests/vm/basevm.py b/tests/vm/basevm.py
index
Added a new special variable QEMU_LOCAL=1, which
will indicate to take the QEMU binary from the current
build.
Signed-off-by: Robert Foley
Reviewed-by: Peter Puhov
Reviewed-by: Alex Bennée
---
tests/vm/Makefile.include | 4
tests/vm/basevm.py| 23 ---
2 files
This helps debug issues that occur during the boot sequence.
Signed-off-by: Robert Foley
Reviewed-by: Peter Puhov
Reviewed-by: Alex Bennée
---
tests/vm/Makefile.include | 1 +
1 file changed, 1 insertion(+)
diff --git a/tests/vm/Makefile.include b/tests/vm/Makefile.include
index
Changes to tests/vm/basevm.py to allow accepting a configuration file
as a parameter. Allows for specifying VM options such as
cpu, machine, memory, and arbitrary qemu arguments for specifying options
such as NUMA configuration.
Also added an example conf_example_aarch64.yml and
Added use of a configuration to tests/vm/basevm.py.
The configuration provides parameters used to configure a VM.
This allows for providing alternate configurations to the VM being
created/launched. cpu, machine, memory, and NUMA configuration are all
examples of configuration which we might want
Adding the args parameter to BaseVM's __init__.
We will shortly need to pass more parameters to the class
so let's just pass args rather than growing the parameter list.
Signed-off-by: Robert Foley
Reviewed-by: Alex Bennée
---
tests/vm/basevm.py | 13 ++---
1 file changed, 6
Add a common Ubuntu python module and make use of
it with the ubuntu.i386 script.
This is preparation for adding an Ubuntu script
ubuntu.aarch64. Splitting out the common
logic such as build_image() will reduce duplication.
Signed-off-by: Robert Foley
---
tests/vm/ubuntu.i386 | 46
Patchew URL: https://patchew.org/QEMU/cover.1590753455.git.mpriv...@redhat.com/
Hi,
This series failed the asan build test. Please find the testing commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ===
#!/bin/bash
This is version 8 of the patch series to
add support for aarch64 VMs in the vm-build infrastructure.
- Ubuntu 18.04 aarch64 VM
- CentOS 8 aarch64 VM
v7: https://lists.gnu.org/archive/html/qemu-devel/2020-05/msg05286.html
Changes in v8:
- Added Ubuntu common module in tests/vm.
- Changed
Patchew URL: https://patchew.org/QEMU/20200529140620.28759-1-l...@redhat.com/
Hi,
This series failed the docker-mingw@fedora build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ===
#!
Patchew URL: https://patchew.org/QEMU/20200529140620.28759-1-l...@redhat.com/
Hi,
This series failed the asan build test. Please find the testing commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ===
#!/bin/bash
export
Patchew URL: https://patchew.org/QEMU/20200529140620.28759-1-l...@redhat.com/
Hi,
This series failed the docker-quick@centos7 build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ===
On Thu, May 21, 2020 at 4:07 AM LIU Zhiwei wrote:
>
> Signed-off-by: LIU Zhiwei
> Reviewed-by: Richard Henderson
Reviewed-by: Alistair Francis
Alistair
> ---
> target/riscv/fpu_helper.c | 33 +
> target/riscv/helper.h | 4 ++
>
Patchew URL: https://patchew.org/QEMU/cover.1590753455.git.mpriv...@redhat.com/
Hi,
This series failed the docker-quick@centos7 build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ===
Hi
On Fri, May 29, 2020 at 6:13 PM Stefan Hajnoczi wrote:
>
> libvhost-user implements several vring features without advertising
> them. There is no way for the vhost-user master to detect support for
> these features.
>
> Things more or less work today because QEMU assumes the vhost-user
>
On Thu, May 21, 2020 at 3:45 AM LIU Zhiwei wrote:
>
> For scalar float instruction, round mode is encoded in instruction,
> so fp_status is updating dynamiclly.
>
> For vector float instruction, round mode is always frm, so
> update fp_status when frm changes is enough.
>
> Signed-off-by: LIU
On Fri, May 29, 2020 at 9:28 PM Stefan Berger
wrote:
> From: Stefan Berger
>
> Do not build a TCPA table for TPM 2 anymore but create the log area when
> building the TPM2 table. The TCPA table is only needed for TPM 1.2.
>
> Signed-off-by: Stefan Berger
>
Reviewed-by: Marc-André Lureau
---
On 5/27/20 2:50 PM, Vladimir Sementsov-Ogievskiy wrote:
>
> Hmm. Actually, I think, it's not a problem to continue support ranges of
> tests for number test names, if you need it.
>
> Note a new paramter --start-from, which is here to re-run failed
> ./check run from the middle of the
From: Stefan Berger
Do not build a TCPA table for TPM 2 anymore but create the log area when
building the TPM2 table. The TCPA table is only needed for TPM 1.2.
Signed-off-by: Stefan Berger
---
hw/i386/acpi-build.c | 12
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git
On 5/28/20 3:51 PM, Tobin Feldman-Fitzthum wrote:
From: Tobin Feldman-Fitzthum
In addition to using QMP to provide the guest memory address
that the launch secret blob will be injected into, the
secret address can also be specified in the guest ROM. This
patch adds sev_find_secret_gpa, which
* Vivek Goyal (vgo...@redhat.com) wrote:
> On Thu, May 14, 2020 at 04:07:36PM +0200, Miklos Szeredi wrote:
> > Path lookup in the kernel has special rules for looking up magic symlinks
> > under /proc. If a filesystem operation is instructed to follow symlinks
> > (e.g. via AT_SYMLINK_FOLLOW or
On Fri, May 29, 2020 at 7:03 AM Markus Armbruster wrote:
>
> We commonly plug devices into their bus right when we create them,
> like this:
>
> dev = qdev_create(bus, type_name);
>
> Note that @dev is a weak reference. The reference from @bus to @dev
> is the only strong one.
>
> We realize
On Mon, 4 May 2020 23:24:20 +0530
Kirti Wankhede wrote:
> This patch makes mtty device migration capable. Purpose od this code is
> to test migration interface. Only stop-and-copy phase is implemented.
> Postcopy migration is not supported.
>
> Actual data for mtty device migration is very
I agree, the program doesn't stop you from doing such things. It should
work without error, but it might be slow. Just offering some advice you
may not want to use it like this.
Try to reproduce with qcow2 and qemu-nbd to see if the problem is with
our support of the disk image format or if it's
* Dr. David Alan Gilbert (git) (dgilb...@redhat.com) wrote:
> From: "Dr. David Alan Gilbert"
>
> HMP has had a qom-set for a long time, but not a matching qom-get;
> various attempts have been made to add one over the last 5 years.
> Here's another go.
>
> It's got simpler due to a suggestion
On Wed, 27 May 2020 at 15:54, Alex Bennée wrote:
>
> The following changes since commit ddc760832fa8cf5e93b9d9e6e854a5114ac63510:
>
> Merge remote-tracking branch 'remotes/gkurz/tags/9p-next-2020-05-26' into
> staging (2020-05-26 14:05:53 +0100)
>
> are available in the Git repository at:
>
>
On 2020-05-28 17:00, James Bottomley wrote:
On Thu, 2020-05-28 at 16:51 -0400, Tobin Feldman-Fitzthum wrote:
--- a/qapi/misc-target.json
+++ b/qapi/misc-target.json
@@ -200,6 +200,26 @@
{ 'command': 'query-sev-capabilities', 'returns': 'SevCapability',
'if': 'defined(TARGET_I386)' }
+##
+#
On 2020-05-28 17:42, Eric Blake wrote:
On 5/28/20 3:51 PM, Tobin Feldman-Fitzthum wrote:
From: Tobin Feldman-Fitzthum
AMD SEV allows a guest owner to inject a secret blob
into the memory of a virtual machine. The secret is
encrypted with the SEV Transport Encryption Key and
integrity is
Signed-off-by: Alexander Bulekov
---
tests/qtest/fuzz/fuzz.c | 8
1 file changed, 8 insertions(+)
diff --git a/tests/qtest/fuzz/fuzz.c b/tests/qtest/fuzz/fuzz.c
index cf76a6636f..4842fbe7c7 100644
--- a/tests/qtest/fuzz/fuzz.c
+++ b/tests/qtest/fuzz/fuzz.c
@@ -95,6 +95,9 @@ static void
The QTest server usually parses ASCII commands from clients. Since we
fuzz within the QEMU process, skip the QTest serialization and server
for most QTest commands. Leave the option to use the ASCII protocol, to
generate readable traces for crash reproducers.
Inspired-by: Philippe Mathieu-Daudé
In the same vein as Philippe's patch:
https://patchew.org/QEMU/20200528165303.1877-1-f4...@amsat.org/
This uses linker trickery to wrap calls to libqtest functions and
directly call the corresponding read/write functions, rather than
relying on the ASCII-serialized QTest protocol.
v2: applies
Signed-off-by: Jean-Christophe Dubois
---
hw/net/imx_fec.c| 101 ++--
hw/net/trace-events | 18
2 files changed, 58 insertions(+), 61 deletions(-)
diff --git a/hw/net/imx_fec.c b/hw/net/imx_fec.c
index 7adcc9df654..823dac0603b 100644
---
Some bits of the CCM registers are non writable.
This was left undone in the initial commit (all bits of registers were
writable).
This patch add the required code to protect non writable bits.
Signed-off-by: Jean-Christophe Dubois
---
hw/misc/imx6ul_ccm.c | 81
On 5/29/2020 4:29 AM, Alex Williamson wrote:
On Wed, 27 May 2020 09:48:22 +0100
"Dr. David Alan Gilbert" wrote:
* Yan Zhao (yan.y.z...@intel.com) wrote:
BTW, for viommu, the downtime data is as below. under the same network
condition and guest memory size, and no running dirty data/memory
Background: The ia-32/ia-64 fxsave64 instruction saves fp80 or legacy SSE mmx
registers. The mmx registers are saved as if they were fp80 values. The lower
64 bits of the constructed fp80 value is the mmx register. The upper 16 bits
of the constructed fp80 value are reserved; see the last row
* Pan Nengyuan (pannengy...@huawei.com) wrote:
> When error happen in initializing 'rdma_return_path', we should cleanup rdma
> context
> before g_free(rdma) to avoid some memleaks. This patch fix that.
>
> Reported-by: Euler Robot
> Signed-off-by: Pan Nengyuan
Queued.
> ---
>
* Juan Quintela (quint...@redhat.com) wrote:
> Pan Nengyuan wrote:
> > 'rdma' is NULL when taking the first error branch in
> > rdma_start_incoming_migration.
> > And it will cause a null pointer access in label 'err'. Fix that.
> >
> > Fixes: 59c59c67ee6b0327ae932deb303caa47919aeb1e
> >
In the same vein as Philippe's patch:
https://patchew.org/QEMU/20200528165303.1877-1-f4...@amsat.org/
This uses linker trickery to wrap calls to libqtest functions and
directly call the corresponding read/write functions, rather than
relying on the ASCII-serialized QTest protocol.
Alexander
On Fri, May 29, 2020 at 11:35:50AM +0100, Daniel P. Berrangé wrote:
> The following changes since commit b8bee16e94df0fcd03bdad9969c30894418b0e6e:
>
> Merge remote-tracking branch 'remotes/kraxel/tags/vga-20200528-pull-request=
> ' into staging (2020-05-28 18:13:20 +0100)
>
> are available in
Signed-off-by: Alexander Bulekov
---
tests/qtest/fuzz/fuzz.c | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/tests/qtest/fuzz/fuzz.c b/tests/qtest/fuzz/fuzz.c
index ea630ddb9b..2c9e2ee7b7 100644
--- a/tests/qtest/fuzz/fuzz.c
+++ b/tests/qtest/fuzz/fuzz.c
@@ -94,7
The QTest server usually parses ASCII commands from clients. Since we
fuzz within the QEMU process, skip the QTest serialization and server
for most QTest commands. Leave the option to use the ASCII protocol, to
generate readable traces for crash reproducers.
Inspired-by: Philippe Mathieu-Daudé
While replacing fprintf() by qemu_log_mask() in commit
2b55f4d3504, we incorrectly used a 'tab = 4 spaces'
alignment, leading to misindented new code. Fix now.
Reported-by: Peter Maydell
Signed-off-by: Philippe Mathieu-Daudé
---
hw/display/cirrus_vga.c | 6 +++---
1 file changed, 3
On 5/29/20 6:36 PM, Peter Maydell wrote:
> On Fri, 29 May 2020 at 17:15, Philippe Mathieu-Daudé wrote:
>> On 5/29/20 12:29 PM, Peter Maydell wrote:
>>> Could somebody send a followup patch to fix the indentation
>>> error checkpatch notices, please?
>>
>> If this is part of your scripts, this is
On Fri, 29 May 2020 at 17:23, Christophe de Dinechin
wrote:
> On 2020-05-26 at 20:51 CEST, Eric Blake wrote...
> > diff --git a/hw/openrisc/openrisc_sim.c b/hw/openrisc/openrisc_sim.c
> > index d08ce6181199..95011a8015b4 100644
> > --- a/hw/openrisc/openrisc_sim.c
> > +++
On Fri, 29 May 2020 at 17:15, Philippe Mathieu-Daudé wrote:
> On 5/29/20 12:29 PM, Peter Maydell wrote:
> > Could somebody send a followup patch to fix the indentation
> > error checkpatch notices, please?
>
> If this is part of your scripts, this is a nice feature :)
No, I just noticed the
On 2020-05-26 at 20:51 CEST, Eric Blake wrote...
> On my Fedora 32 machine, gcc 10.1.1 at -O2 (the default for a bare
> './configure') has a false-positive complaint:
>
> CC or1k-softmmu/hw/openrisc/openrisc_sim.o
> /home/eblake/qemu/hw/openrisc/openrisc_sim.c: In function
On Fri, May 29, 2020 at 03:53:37PM +, Derrick, Jonathan wrote:
> On Fri, 2020-05-29 at 11:33 +0100, Lorenzo Pieralisi wrote:
> > On Wed, May 27, 2020 at 11:02:39PM -0400, Jon Derrick wrote:
> > > Versions of VMD with the Host Physical Address shadow register use this
> > > register to
Hi Peter,
On 5/29/20 12:29 PM, Peter Maydell wrote:
> On Thu, 28 May 2020 at 13:36, Gerd Hoffmann wrote:
>>
>> The following changes since commit 06539ebc76b8625587aa78d646a9d8d5fddf84f3:
>>
>> Merge remote-tracking branch
>> 'remotes/philmd-gitlab/tags/mips-hw-next-20200526' into staging
libvhost-user implements several vring features without advertising
them. There is no way for the vhost-user master to detect support for
these features.
Things more or less work today because QEMU assumes the vhost-user
backend always implements certain feature bits like
VIRTIO_RING_F_EVENT_IDX.
On Thu 28 May 2020 09:11:07 PM CEST, Eric Blake wrote:
>> I think the problem also exists in the current code (without my
>> patches). If you zeroize 10 clusters and the last one is compressed
>> you have to repeat the request after having zeroized 9 clusters.
>
> Hmm. In the pre-patch code,
On Fri, 2020-05-29 at 11:33 +0100, Lorenzo Pieralisi wrote:
> On Wed, May 27, 2020 at 11:02:39PM -0400, Jon Derrick wrote:
> > Versions of VMD with the Host Physical Address shadow register use this
> > register to calculate the bus address offset needed to do guest
> > passthrough of the domain.
Hi Ye,
Thank you for your test and report, I will try to fix this issue.
Thanks
Zhang Chen
> -Original Message-
> From: Qemu-devel bounces+chen.zhang=intel@nongnu.org> On Behalf Of ye.zou
> Sent: Friday, May 29, 2020 5:47 PM
> To: qemu-devel@nongnu.org
> Subject: [Bug 1881231] Re:
On Fri, May 29, 2020 at 03:15:59PM +0800, Jason Wang wrote:
>
> On 2020/5/23 上午1:17, Stefan Hajnoczi wrote:
> > The packed virtqueue layout was introduced in VIRTIO 1.1. It is a single
> > ring instead of a split avail/used ring design. There are CPU cache
> > advantages to this layout and it is
On Fri, 29 May 2020 15:33:46 +0200
Michal Privoznik wrote:
> The documentation to `-numa hmat-cache` says that @node-id, @size
> and @level are the only required attributes. The rest
> (@associativity, @policy and @line) is optional. Well, not quite
> - if I try to start QEMU with only the three
On 5/29/20 5:09 PM, Igor Mammedov wrote:
On Fri, 29 May 2020 15:33:48 +0200
Michal Privoznik wrote:
The initiator attribute of a NUMA node is documented as the 'NUMA
node that has best performance to given NUMA node'. If a NUMA
node has at least one CPU there can hardly be a different node
On 5/29/20 4:59 PM, Igor Mammedov wrote:
On Fri, 29 May 2020 15:33:47 +0200
Michal Privoznik wrote:
Currently, when defining a HMAT cache for a NUMA node (in
parse_numa_hmat_cache()) there is this check that forces users to
define HMAT latency/bandwidth first. There is no real need for
this,
On Wed, May 27, 2020 at 04:28:41PM +0200, Marc-André Lureau wrote:
> Hi Stefan
>
> On Fri, May 22, 2020 at 7:18 PM Stefan Hajnoczi wrote:
> >
> > Many vhost devices in QEMU currently do not involve the device backend
> > in feature negotiation. This seems fine at first glance for device types
>
To figure out which register gdb is complaining about, you could step through
the code in gdb or selectively remove parts of the xml file until the error
goes away.
The unaligned start address sounds like a problem with the executable you are
trying to debug, not qemu or gdb.
Taylor
From:
On 5/29/20 10:07 AM, Alberto Garcia wrote:
On Wed 27 May 2020 08:30:06 PM CEST, Eric Blake wrote:
+offset=$(($offset + 8))
+bitmap=`peek_file_be "$TEST_IMG" $offset 8`
+
+expected_bitmap=0
+for bit in $expected_alloc; do
+expected_bitmap=$(($expected_bitmap | (1 <<
On Fri, 29 May 2020 15:33:48 +0200
Michal Privoznik wrote:
> The initiator attribute of a NUMA node is documented as the 'NUMA
> node that has best performance to given NUMA node'. If a NUMA
> node has at least one CPU there can hardly be a different node
> with better performace and thus all
On Wed 27 May 2020 08:30:06 PM CEST, Eric Blake wrote:
>> +offset=$(($offset + 8))
>> +bitmap=`peek_file_be "$TEST_IMG" $offset 8`
>> +
>> +expected_bitmap=0
>> +for bit in $expected_alloc; do
>> +expected_bitmap=$(($expected_bitmap | (1 << $bit)))
>> +done
>> +for
On Fri, 29 May 2020 15:33:47 +0200
Michal Privoznik wrote:
> Currently, when defining a HMAT cache for a NUMA node (in
> parse_numa_hmat_cache()) there is this check that forces users to
> define HMAT latency/bandwidth first. There is no real need for
> this, because nothing in the parse
On Fri, 29 May 2020 at 09:51, Eric Blake wrote:
>
> On 5/29/20 8:23 AM, Robert Foley wrote:
> > From: Lingfeng Yang
> >
> > We tried running QEMU under tsan in 2016, but tsan's lack of support for
> > longjmp-based fibers was a blocker:
> >
On 29/05/20 16:34, Peter Xu wrote:
> On Fri, May 29, 2020 at 02:53:25PM +0200, Philippe Mathieu-Daudé wrote:
>> @@ -2920,35 +2916,46 @@ static void mtree_print_mr(const MemoryRegion *mr,
>> unsigned int level,
>> ml->mr = mr->alias;
>>
1 - 100 of 319 matches
Mail list logo