Hi Gerd,
> -Original Message-
> From: Gerd Hoffmann
> Sent: Monday, September 28, 2020 6:45 PM
> To: Edgar Iglesias
> Cc: Sai Pavan Boddu ; Peter Maydell
> ; Markus Armbruster ;
> 'Marc-André Lureau' ; Paolo Bonzini
> ; Edgar Iglesias ; Francisco
> Eduardo Iglesias ; qemu-devel@nongnu.or
Public bug reported:
I currently run qemu with the following options
`qemu-system-aarch64 -machine mps2-an505 -cpu cortex-m33 -m 16`
For some reason, memory address over 0x2000_7ffc is not accessible.
It can be tested in gdb as follow.
(gdb) x/x 0x20007ffc
0x20007ffc: 0x
(gdb) x/x 0x
On Fri, Sep 18, 2020 at 02:11:11PM +0530, Ani Sinha wrote:
> This change adds a new DSDT golden master table blob to test disabling
> hotplug on both pci root bus and pci bridges. Also reverts the change
> in file bios-tables-test-allowed-diff.h to make sure its now empty so that
> future modificat
On Sun, Sep 27, 2020 at 09:48:28AM +0300, Dima Stepanov wrote:
> On Thu, Sep 24, 2020 at 07:26:14AM -0400, Michael S. Tsirkin wrote:
> > On Fri, Sep 11, 2020 at 11:39:42AM +0300, Dima Stepanov wrote:
> > > v4 -> v5:
> > > - vhost: check queue state in the vhost_dev_set_log routine
> > > tests
Changes from v3:
- dropped reconnect tests
- added more fixes, an smbios feature
The following changes since commit 74504514b154ebebdff577d88e4bf5c13074e9ed:
Merge remote-tracking branch 'remotes/alistair/tags/pull-register-20200927'
into staging (2020-09-28 16:49:10 +0100)
are available in t
From: Dima Stepanov
If the vhost-user-blk daemon provides only one virtqueue, but device was
added with several queues, then QEMU will send more VHOST-USER command
than expected by daemon side. The vhost_virtqueue_start() routine
handles such case by checking the return value from the
virtio_queu
From: Jason Wang
To speed up the memory mapping updating between vhost-vDPA and vDPA
device driver, this patch passes the IOTLB batching flags via IOTLB
API. Two new flags was introduced, VHOST_IOTLB_BATCH_BEGIN is a hint
that a bathced IOTLB updating may be initiated from the
userspace. VHOST_IO
From: Dima Stepanov
vhost-user devices can get a disconnect in the middle of the VHOST-USER
handshake on the migration start. If disconnect event happened right
before sending next VHOST-USER command, then the vhost_dev_set_log()
call in the vhost_migration_log() function will return error. This
From: Li Qiang
If error occurs while processing the virtio request we should call
'virtqueue_detach_element' to detach the element from the virtqueue
before free the elem.
Signed-off-by: Li Qiang
Message-Id: <20200816142245.17556-1-liq...@163.com>
Fixes: 910b25766b ("virtio-mem: Paravirtualized
From: David Hildenbrand
Unfortunately, a typo sneeked in: we want to set
auto_enable_numa_with_memdev to false, not auto_enable_numa_with_memhp.
Cc: qemu-sta...@nongnu.org # v5.1
Fixes: 195784a0cfad (numa: Auto-enable NUMA when any memory devices are
possible)
Reported-by: Dr. David Alan Gilber
From: Laurent Vivier
Dumping one line of hexadecimal/ASCII from a buffer is often needed.
Move this part from qemu_hexdump() and use it
Acked-by: Stefan Hajnoczi
Signed-off-by: Laurent Vivier
Message-Id: <20200925091055.186023-2-lviv...@redhat.com>
Reviewed-by: Michael S. Tsirkin
Signed-off-b
From: Igor Mammedov
These were deprecated since 4.0, remove both HMP and QMP variants.
Users should use device_add command instead. To get list of
possible CPUs and options, use 'info hotpluggable-cpus' HMP
or query-hotpluggable-cpus QMP command.
Signed-off-by: Igor Mammedov
Reviewed-by: Thoma
From: Dima Stepanov
For now only vhost-user-net device is supported by the test. Other
vhost-user devices are not tested. As a first step make source code
refactoring so new devices can reuse the same test routines. To make
this provide a new vhost_user_ops structure with the methods to
initializ
From: Laurent Vivier
Add trace functions in vhost-vdpa.c.
All traces from this file can be enabled with '-trace vhost_vdpa*'.
Acked-by: Stefan Hajnoczi
Signed-off-by: Laurent Vivier
Message-Id: <20200925091055.186023-3-lviv...@redhat.com>
Acked-by: Jason Wang
Reviewed-by: Michael S. Tsirkin
From: Stefano Garzarella
virtio-vsock was introduced after the release of VIRTIO 1.0
specifications, so it should be 'modern-only'.
This patch forces virtio version 1 as done for vhost-vsock-pci.
To avoid migration issues, we force virtio version 1 only when
legacy check is enabled in the new m
From: Laurent Vivier
Following the same logic as for vhost-net-user and vhost-kernel,
enable vhost-net if vhost-net-vdpa is enabled and vhost-net is not
explicitly disabled.
See 299e6f19b3e2 ("vhost-net: revamp configure logic")
Autoselect VHOST if VHOST_VDPA is set
See 21c6b0c87e85 ("configure:
From: Eric Auger
If realize fails, domains and endpoints trees may be NULL. On
unrealize(), this produces assertions:
"GLib: g_tree_destroy: assertion 'tree != NULL' failed"
Check that the trees are non NULL before destroying them.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Eric Auger
Reviewed
From: Stefano Garzarella
Commit 9b3a35ec82 ("virtio: verify that legacy support is not
accidentally on") added a safety check that requires to set
'disable-legacy=on' on vhost-vsock-pci device:
$ ./qemu-system-x86_64 ... -device vhost-vsock-pci,guest-cid=5
qemu-system-x86_64: -device
From: Igor Mammedov
... to let tests pass until binary blobs are updated with new AML
Signed-off-by: Igor Mammedov
Message-Id: <20200923094650.1301166-6-imamm...@redhat.com>
Reviewed-by: Michael S. Tsirkin
Signed-off-by: Michael S. Tsirkin
---
tests/qtest/bios-tables-test-allowed-diff.h | 19
From: Igor Mammedov
Expose the "smi_negotiated_features" field of ICH9LPCState as
a QOM property.
Signed-off-by: Igor Mammedov
Reviewed-by: Laszlo Ersek
Tested-by: Laszlo Ersek
Message-Id: <20200923094650.1301166-7-imamm...@redhat.com>
Reviewed-by: Michael S. Tsirkin
Signed-off-by: Michael S
From: Eric Auger
Commit 9b3a35ec82 ("virtio: verify that legacy support is not
accidentally on") added a safety check that requires to set
'disable-legacy=on' on virtio-iommu-pci:
qemu-system-aarch64: -device virtio-iommu-pci: device is modern-only,
use disable-legacy=on
virtio-iommu was introd
From: Igor Mammedov
When CPU hotplug with SMI has been negotiated, describe the SMI
register block in the DSDT. Pass the ACPI name of the SMI control
register to build_cpus_aml(), so that CPU_SCAN_METHOD can access the
register in the next patch.
Signed-off-by: Igor Mammedov
Reviewed-by: Laszlo
From: Stefano Garzarella
Commit 9b3a35ec82 ("virtio: verify that legacy support is not
accidentally on") added a safety check that requires to set
'disable-legacy=on' on vhost-user-vsock-pci device:
$ ./qemu-system-x86_64 ... \
-chardev socket,id=char0,reconnect=0,path=/tmp/vhost4.socket
From: Daniel P. Berrangé
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: Daniel P. Berrangé
Message-Id: <20200923133804.2089190-4-berra...@redhat.com>
Reviewed-by: Michael S. Tsirkin
Signed-off-by: Michael S. Tsirkin
---
qemu-options.hx | 41 +
1 fi
From: Igor Mammedov
It will allow firmware to notify QEMU that firmware requires SMI
being triggered on CPU hot[un]plug, so that it would be able to account
for hotplugged CPU and relocate it to new SMM base and/or safely remove
CPU on unplug.
Using negotiated features, follow up patches will in
From: Daniel P. Berrangé
Some applications want to pass quite large values for the OEM strings
entries. Rather than having huge strings on the command line, it would
be better to load them from a file, as supported with -fw_cfg.
This introduces the "path" parameter allowing for:
$ echo -n "th
From: Ani Sinha
This patch adds a binary blob corresponding to the DSDT acpi table. It is used
to unit test the flag 'acpi-pci-hotplug-with-bridge-support' used with pci
bridges.
This change also clears the file tests/qtest/bios-tables-test-allowed-diff.h
so that future changes which affect the
From: Stefano Garzarella
Commit 9b3a35ec82 ("virtio: verify that legacy support is not accidentally
on") added a check that returns an error if legacy support is on, but the
device does not support legacy.
Unfortunately some devices were wrongly declared legacy capable even if
they were not (e.g
From: Igor Mammedov
Signed-off-by: Igor Mammedov
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Laszlo Ersek
Tested-by: Laszlo Ersek
Message-Id: <20200923094650.1301166-5-imamm...@redhat.com>
Reviewed-by: Michael S. Tsirkin
Signed-off-by: Michael S. Tsirkin
---
include/hw/acpi/aml-build.
From: Igor Mammedov
There were reports of guest crash on CPU hotplug, when using q35 machine
type and OVMF with SMM, due to hotplugged CPU trying to process SMI at
default SMI handler location without it being relocated by firmware first.
Fix it by refusing hotplug if firmware hasn't negotiated
From: Daniel P. Berrangé
The SMBIOS 2.1 entry point uses a uint16 data type for reporting the
total length of the tables. If the user passes -smbios configuration to
QEMU that causes the table size to exceed this limit then various bad
behaviours result, including
- firmware hangs in an infinit
From: Ani Sinha
When acpi hotplug is turned off for both root pci bus as well as for pci
bridges, we should not generate the related ACPI code for DSDT table or
initialize related hw ports or reserve hw resources. This change makes
sure all those operations are turned off in the case ACPI pci hot
From: Igor Mammedov
Translate the "CPU hotplug with SMI" feature bit, from the property
added in the last patch, to a dedicated boolean in AcpiPmInfo.
Signed-off-by: Igor Mammedov
Reviewed-by: Laszlo Ersek
Tested-by: Laszlo Ersek
Message-Id: <20200923094650.1301166-8-imamm...@redhat.com>
Revi
From: Igor Mammedov
In case firmware has negotiated CPU hotplug SMI feature, generate
AML to describe SMI IO port region and send SMI to firmware
on each CPU hotplug SCI in case new CPUs were hotplugged.
Since new CPUs can be hotplugged while CPU_SCAN_METHOD is running
we can't send SMI before n
From: haibinzhang(张海斌)
Fore-commit(c6beefd674) only saves features of queue0,
this makes wrong features of other queues in multiqueues
situation.
For examples:
qemu-system-aarch64 ... \
-chardev socket,id=charnet0,path=/var/run/vhost_sock \
-netdev vhost-user,chardev=charnet0,queues=2,id=ho
From: Ani Sinha
A new binary acpi table tests/data/acpi/pc/DSDT.roothp is added in order to
unit test the feature flag that can disable/enable root pci bus hotplug on
i440fx. This feature was added with the commit:
3d7e78aaf0 ("Introduce a new flag for i440fx to disable PCI hotplug on
the roo
From: Jason Wang
Update against Linux 5.9-rc4.
Cc: Cornelia Huck
Cc: Paolo Bonzini
Signed-off-by: Jason Wang
Message-Id: <20200907104903.31551-2-jasow...@redhat.com>
Reviewed-by: Michael S. Tsirkin
Signed-off-by: Michael S. Tsirkin
---
include/standard-headers/drm/drm_fourcc.h | 140 ++
From: Ani Sinha
The file 'tests/data/acpi/pc/DSDT.hpbridge' is a newly added acpi table file
for testing the pci bridge option 'acpi-pci-hotplug-with-bridge-support' under
i440fx. This change documents this fact.
Signed-off-by: Ani Sinha
Reviewed-by: Igor Mammedov
Message-Id: <20200918084111.1
From: Ani Sinha
Ability to turn hotplug off on the pci root bus for i440fx was added in commit:
3d7e78aaf0 ("Introduce a new flag for i440fx to disable PCI hotplug on the
root bus")
This change adds a unit test in order to test this feature.
Signed-off-by: Ani Sinha
Reviewed-by: Igor Mamme
From: Li Qiang
Current the 'virtio_set_features' only update the 'MemorRegionCaches'
when the 'virtio_set_features_nocheck' return '0' which means it is
not bad features. However the guest can still trigger the access of the
used vring after set bad features. In this situation it will cause asser
From: Ani Sinha
Cold plugged bridges are not hot unpluggable, even when their hotplug
property (acpi-pci-hotplug-with-bridge-support) is turned off. Please see
the function acpi_pcihp_pc_no_hotplug(). However, with
the current implementaton, Windows would try to hot-unplug a pci bridge when
it's
From: Ani Sinha
When ACPI hotplug for the root bus is disabled, the bsel property for that
bus is not set. Please see the following commit:
3d7e78aaf ("Introduce a new flag for i440fx to disable PCI hotplug on the
root bus").
As a result, when acpi_pcihp_find_hotplug_bus() is called
with bs
On Tue, Sep 29, 2020 at 12:53:17PM +0530, Ani Sinha wrote:
> On Tue, Sep 29, 2020 at 12:42 PM Michael S. Tsirkin wrote:
> >
> > On Fri, Sep 18, 2020 at 02:11:11PM +0530, Ani Sinha wrote:
> > > This change adds a new DSDT golden master table blob to test disabling
> > > hotplug on both pci root bus
From: Ani Sinha
A new binary ACPI table tests/data/acpi/pc/DSDT.roothp is added in order
to unit test hotplug on/off capability on the root pci bus for i440fx.
The diff between the table DSDT.bridge and DSDT.roothp is listed below:
@@ -1,30 +1,30 @@
/*
* Intel ACPI Component Architecture
*
From: Ani Sinha
This change adds a new unit test for the global flag
'acpi-pci-hotplug-with-bridge-support' which is available for cold plugged pci
bridges in i440fx. The flag can be used to turn off ACPI based hotplug support
on all pci bridges.
Signed-off-by: Ani Sinha
Reviewed-by: Igor Mamme
Hi
On Tue, Sep 22, 2020 at 9:08 PM Paolo Bonzini wrote:
> On 22/09/20 18:35, Marc-André Lureau wrote:
> > The D-Bus specification doesn't detail versioning much. What is
> > recommended is to have the version number as part of the interface name
> > (kinda like soname):
> > http://0pointer.de/bl
From: Ani Sinha
The following patch ("piix4: don't reserve hw resources when
hotplug is off globally") modifies certain ACPI tables for q35 machines.
This patch adds those table names to tests/qtest/bios-tables-test-allowed-diff.h
so that unit tests continue to pass and bisection is not broken.
From: Jason Wang
This patch tries to switch to use new kernel IOTLB format V2. Previous
version may have inconsistent ABI between 32bit and 64bit machines
because of the hole after type field. Refer kernel commit
("429711aec282 vhost: switch to use new message format") for more
information.
To e
Stefan Hajnoczi writes:
> On Sun, Aug 16, 2020 at 12:46:10PM -0500, dubo...@gmail.com wrote:
>> From: Josh DuBois
>>
>> Tracing can be enabled at the command line or via the
>> monitor. Command-line trace options are recorded during
>> trace_opt_parse(), but tracing is not enabled until the var
From: Stefan Hajnoczi
vu_panic() is not guaranteed to exit the program. Return early when
errors are encountered.
Note that libvhost-user does not have an "unmap" operation for mapped
descriptors. Therefore it is correct to return without explicit cleanup.
Signed-off-by: Stefan Hajnoczi
Messag
From: Li Qiang
If error occurs while processing the virtio request we should call
'virtqueue_detach_element' to detach the element from the virtqueue
before free the elem.
Signed-off-by: Li Qiang
Message-Id: <20200813165125.59928-1-liq...@163.com>
Reviewed-by: Michael S. Tsirkin
Signed-off-by:
On Sun, Sep 27, 2020 at 08:17:10PM +0800, Guoqing Zhang wrote:
> hello Gerd and Michael Michael S. Tsirkin
>
> ping
Queued up now (not much activity for vga/ui these days ...).
>
> http://patchwork.ozlabs.org/project/qemu-devel/list/?series=202680
>
> On Fri, Sep 18, 2020 at 7:16 PM Guoqing
From: Stefan Hajnoczi
vu_panic() is not guaranteed to exit the program. Return early when
errors are encountered.
Signed-off-by: Stefan Hajnoczi
Message-Id: <20200921113420.154378-3-stefa...@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Michael S. Tsirkin
Signed-off-by: Michael
On Sun, Sep 27, 2020 at 06:57:45PM +0400, marcandre.lur...@redhat.com wrote:
> From: Marc-André Lureau
>
> Hi,
>
> This series improves the support for HiDPI displays with Spice.
> The related spice series have already been merged.
>
> v3:
> - simplify the handling of Spice monitor configurat
On Tue, Sep 29, 2020 at 12:42 PM Michael S. Tsirkin wrote:
>
> On Fri, Sep 18, 2020 at 02:11:11PM +0530, Ani Sinha wrote:
> > This change adds a new DSDT golden master table blob to test disabling
> > hotplug on both pci root bus and pci bridges. Also reverts the change
> > in file bios-tables-tes
Thanks James, but now I'm unsure where to go from here as it isn't
reproducible with many tries at different scales that James and I did.
@Sean/Lee
Since you wondered if it might be due to Ubuntu Delta on top of 4.2 - there are
two things we could compare Ubuntu's qemu to then:
1. qemu 4.2 as re
From: Pankaj Gupta
Qemu fails with below error when trying to run with virtio pmem:
(qemu) qemu-system-x86_64: -device virtio-pmem-pci,memdev=mem1,id=nv1:
device is modern-only, use disable-legacy=on
This patch fixes this by forcing virtio 1 with virtio-pmem.
fixes: adf0748a49 ("virtio-pc
From: Igor Mammedov
CPU hot-unplug with SMM requires firmware participation to prevent
guest crash (i.e. CPU can be removed only after OS _and_ firmware
were prepared for the action).
Previous patches introduced ICH9_LPC_SMI_F_CPU_HOT_UNPLUG_BIT
feature bit, which is advertised by firmware when i
Missed in commit 41fba1618b "docs/system: convert the documentation of
deprecated features to rST."
Signed-off-by: Markus Armbruster
---
target/i386/cpu.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/target/i386/cpu.c b/target/i386/cpu.c
index 3ffd877dd5..aa0c38c793 1006
From: Igor Mammedov
here is diff against tests/data/acpi/q35/DSDT
for currently shipped ovmf binary.
(once firmware blob is updated, it will negotiate CPU hotplug
feature which will ad extra hunk sending SMI and Q35 tests will
need to be updated), but otherwise diff shows new CPU hotplug
AML that
Missed in 3c95fdef94 "Update comments in .hx files that mention
Texinfo".
Signed-off-by: Markus Armbruster
---
qemu-img-cmds.hx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/qemu-img-cmds.hx b/qemu-img-cmds.hx
index b89c019b76..cab8234235 100644
--- a/qemu-img-cmds.hx
+++ b
Markus Armbruster (2):
qemu-img-cmds.hx: Update comment that mentions Texinfo
target/i386/cpu: Update comment that mentions Texinfo
target/i386/cpu.c | 3 ++-
qemu-img-cmds.hx | 2 +-
2 files changed, 3 insertions(+), 2 deletions(-)
--
2.26.2
Peter Maydell writes:
> Convert qemu-ga-ref to rST format. This includes dropping
> the plain-text, pdf and info format outputs for this document;
> as with all our other Sphinx-based documentation, we provide
> HTML and manpage only.
>
> The qemu-ga-ref.rst is somewhat more stripped down than
>
On Tue, Sep 29, 2020 at 12:56 PM Michael S. Tsirkin wrote:
>
> On Tue, Sep 29, 2020 at 12:53:17PM +0530, Ani Sinha wrote:
> > On Tue, Sep 29, 2020 at 12:42 PM Michael S. Tsirkin wrote:
> > >
> > > On Fri, Sep 18, 2020 at 02:11:11PM +0530, Ani Sinha wrote:
> > > > This change adds a new DSDT golde
On Fri, May 29, 2020 at 02:00:46AM +0530, Kirti Wankhede wrote:
> * 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 marked as
> dirty during migr
Peter Maydell writes:
> Convert qemu-qmp-ref to rST format. This includes dropping
> the plain-text, pdf and info format outputs for this document;
> as with all our other Sphinx-based documentation, we provide
> HTML and manpage only.
>
> The qemu-qmp-ref.rst is somewhat more stripped down than
Peter Maydell writes:
> Add some section headings to the QGA json; this is purely so that we
> have some H1 headings, as otherwise each command ends up being
> visible in the interop/ manual's table of contents. In an ideal
> world there might be a proper 'Introduction' section the way there is
Peter Maydell writes:
> doc-good.json currently uses the old *strong* and _emphasis_ markup.
> As part of the conversion to rST this needs to switch to **strong**
> and *emphasis*, because rST uses underscores as part of its markup
> of hyperlinks and will otherwise warn about the syntax error.
>
Appears to break documented make target html:
$ make -C bld-x86 html
make: Entering directory '/work/armbru/qemu/bld-x86'
make: *** No rule to make target 'html'. Stop.
make: Leaving directory '/work/armbru/qemu/bld-x86'
Peter Maydell writes:
> We're going to want to use SPHINX_ARGS in both docs/meson.build
> and tests/qapi-schema/meson.build. Move the definition up to the
> top level file so it is available to both subdirectories.
>
> Signed-off-by: Peter Maydell
> ---
> docs/meson.build | 8
> meson.
Patchew URL: https://patchew.org/QEMU/20200929071948.281157-1-...@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 Tue, Sep 29, 2020 at 1:53 PM Ani Sinha wrote:
>
> On Tue, Sep 29, 2020 at 12:56 PM Michael S. Tsirkin wrote:
> >
> > On Tue, Sep 29, 2020 at 12:53:17PM +0530, Ani Sinha wrote:
> > > On Tue, Sep 29, 2020 at 12:42 PM Michael S. Tsirkin
> > > wrote:
> > > >
> > > > On Fri, Sep 18, 2020 at 02:11
Peter Maydell writes:
> The automatic dependency handling for Sphinx manuals only makes the output
> depend on the input documentation files. This means that if you edit
> the Python source of an extension then the documentation won't be
> rebuilt.
>
> Create a list of all the source files for th
On Mon, 28 Sep 2020 at 20:16, Markus Armbruster wrote:
>
> Peter Maydell writes:
> > +Descriptions of arguments can span multiple lines. The description
> > +text can start on the line following the '@argname:', in which case
> > +it must not be indented at all. It can also start on the same line
The current IOVA allocator allocates within the [0x1, 1ULL << 39]
window, without paying attention to the host IOVA reserved regions.
This prevents NVMe passthtrough from working on ARM as the fixed
IOVAs rapidly grow up to the MSI reserved region [0x800, 0x810]
causing some VFIO MAP DM
The IOVA allocator currently ignores host reserved regions.
As a result some chosen IOVAs may collide with some of them,
resulting in VFIO MAP_DMA errors later on. This happens on ARM
where the MSI reserved window quickly is encountered:
[0x800, 0x810]. since 5.4 kernel, VFIO returns the us
On Mon, 28 Sep 2020 at 23:02, Kamil Rytarowski wrote:
>
> Personally, I prefer using the system headers. but if you want to use
> the GCC builtins, please go for it.
I'd agree if the system header approach was cross-platform
or if this was a BSD-only program or if we were aiming for
complete comp
Introduce the qemu_vfio_find_fixed/temp_iova helpers which
respectively allocate IOVAs from the bottom/top parts of the
usable IOVA range, without picking within host IOVA reserved
windows. The allocation remains basic: if the size is too big
for the remaining of the current usable IOVA range, we j
On Tue, Sep 29, 2020 at 02:09:55AM -0400, Michael S. Tsirkin wrote:
> On Mon, Sep 28, 2020 at 10:25:37AM +0100, Stefan Hajnoczi wrote:
> > Why extend vhost-user with vDPA?
> >
> > Reusing VIRTIO emulation code for vhost-user backends
> >
On 9/29/20 4:46 AM, no-re...@patchew.org wrote:
> Patchew URL: https://patchew.org/QEMU/20200928171539.788309-1-f4...@amsat.org/
> time make docker-test-quick@centos7 SHOW_ENV=1 J=14 NETWORK=1
> ---
> qemu-system-aarch64: falling back to tcg
> socket_accept failed: Resource temporarily unavailable
On Tue, 29 Sep 2020 at 07:54, Markus Armbruster wrote:
>
> Peter Maydell writes:
>
> > Some of our documentation is auto-generated from documentation
> > comments in the JSON schema.
> >
> > For Sphinx, rather than creating a file to include, the most natural
> > way to handle this is to have a s
+Alex/Daniel
On 9/28/20 10:33 PM, Willian Rampazzo wrote:
> On Mon, Sep 28, 2020 at 2:31 PM Philippe Mathieu-Daudé
> wrote:
>>
>> Add a test for the mipssim machine, based on the recommended
>> test setup from Thomas Huth:
>> https://www.mail-archive.com/qemu-devel@nongnu.org/msg606846.html
>>
>
On 9/29/20 9:58 AM, Markus Armbruster wrote:
> Markus Armbruster (2):
> qemu-img-cmds.hx: Update comment that mentions Texinfo
> target/i386/cpu: Update comment that mentions Texinfo
>
> target/i386/cpu.c | 3 ++-
> qemu-img-cmds.hx | 2 +-
> 2 files changed, 3 insertions(+), 2 deletions(-)
This is expected behaviour. The memory at 0x2000_ in this board is
the "FPGA block RAM", and there is only 32K of it, so it finishes at
0x2000_7fff, and attempts to access beyond that will fail because there
is no device or memory at the address immediately after it in the memory
map.
--
You
PS: you don't need to pass "-cpu cortex-m33" as it is the default for
the mps2-an505 board, and you don't need to pass a -m argument either,
as 16MB is the fixed value for this board.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
ht
(If you were just interested in having a large area of contiguous RAM,
the "PSRAM" is the largest lump on this board: it's 16MB starting at
0x8000_.)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/
On Tue, 29 Sep 2020 at 09:20, Markus Armbruster wrote:
>
> Peter Maydell writes:
>
> > Convert qemu-ga-ref to rST format. This includes dropping
> > the plain-text, pdf and info format outputs for this document;
> > as with all our other Sphinx-based documentation, we provide
> > HTML and manpage
On Mon, 28 Sep 2020 at 14:23, Gerd Hoffmann wrote:
>
> The following changes since commit 8d16e72f2d4df2c9e631393adf1669a1da7efe8a:
>
> Merge remote-tracking branch
> 'remotes/dgilbert/tags/pull-migration-20200925a' into staging (2020-09-25
> 14:46:18 +0100)
>
> are available in the Git reposi
Philippe Mathieu-Daudé writes:
> +Alex/Daniel
>
> On 9/28/20 10:33 PM, Willian Rampazzo wrote:
>> On Mon, Sep 28, 2020 at 2:31 PM Philippe Mathieu-Daudé
>> wrote:
>>>
>>> Add a test for the mipssim machine, based on the recommended
>>> test setup from Thomas Huth:
>>> https://www.mail-archive
On Tue, 29 Sep 2020 at 09:28, Markus Armbruster wrote:
>
> Peter Maydell writes:
> > diff --git a/qapi/meson.build b/qapi/meson.build
> > index 2b2872a41d8..a287ca5d9d7 100644
> > --- a/qapi/meson.build
> > +++ b/qapi/meson.build
> > @@ -97,7 +97,7 @@ foreach module : qapi_all_modules
> > endfor
On 9/29/20 8:57 AM, Changho Choi wrote:
> Public bug reported:
>
> I currently run qemu with the following options
> `qemu-system-aarch64 -machine mps2-an505 -cpu cortex-m33 -m 16`
>
> For some reason, memory address over 0x2000_7ffc is not accessible.
> It can be tested in gdb as follow.
>
> (g
On Tue, Sep 29, 2020 at 02:21:06PM +0530, Ani Sinha wrote:
> On Tue, Sep 29, 2020 at 1:53 PM Ani Sinha wrote:
> >
> > On Tue, Sep 29, 2020 at 12:56 PM Michael S. Tsirkin wrote:
> > >
> > > On Tue, Sep 29, 2020 at 12:53:17PM +0530, Ani Sinha wrote:
> > > > On Tue, Sep 29, 2020 at 12:42 PM Michael
Original commit did not allocate IRQs for the SMMUv3 in the irqmap
effectively using irq 0->3 (shared with other devices). Assuming
original intent was to allocate unique IRQs then add an allocation
to the irqmap.
Fixes: e9fdf453240 ("hw/arm: Add arm SBSA reference machine, devices part")
Signed-o
Fix two issues with the smmuv3 initialisation, first where a previous
patch had transposed an i to a 1. The second an assumption that the
IRQs allocated were meant to be unique and not 0 based.
Graeme Gregory (2):
hw/arm/sbsa-ref : Fix SMMUv3 Initialisation
hw/arm/sbsa-ref : allocate IRQs for
SMMUv3 has an error in previous patch where a i was transposed to a 1
meaning interrupts would not have been correctly assigned to the SMMUv3
instance.
Fixes: 48ba18e6d3f3 ("hw/arm/sbsa-ref: Simplify by moving the gic in the
machine state")
Signed-off-by: Graeme Gregory
---
hw/arm/sbsa-ref.c |
On Tue, 29 Sep 2020 at 09:42, Markus Armbruster wrote:
>
> Appears to break documented make target html:
>
> $ make -C bld-x86 html
> make: Entering directory '/work/armbru/qemu/bld-x86'
> make: *** No rule to make target 'html'. Stop.
> make: Leaving directory '/work/armbru/qemu/bld-x86'
Whoops
On 2020/9/28 18:57, Kevin Wolf wrote:
> Am 27.09.2020 um 15:04 hat Ying Fang geschrieben:
>> A VM in the cloud environment may use a virutal disk as the backend storage,
>> and there are usually filesystems on the virtual block device. When backend
>> storage is temporarily down, any I/O issued t
On Tue, Sep 29, 2020 at 03:13:09AM -0400, Michael S. Tsirkin wrote:
> On Sun, Sep 27, 2020 at 09:48:28AM +0300, Dima Stepanov wrote:
> > On Thu, Sep 24, 2020 at 07:26:14AM -0400, Michael S. Tsirkin wrote:
> > > On Fri, Sep 11, 2020 at 11:39:42AM +0300, Dima Stepanov wrote:
> > > > v4 -> v5:
> > > >
On 9/29/20 11:38 AM, Alex Bennée wrote:
>
> Philippe Mathieu-Daudé writes:
>
>> +Alex/Daniel
>>
>> On 9/28/20 10:33 PM, Willian Rampazzo wrote:
>>> On Mon, Sep 28, 2020 at 2:31 PM Philippe Mathieu-Daudé
>>> wrote:
Add a test for the mipssim machine, based on the recommended
test
On 9/29/20 11:42 AM, Graeme Gregory wrote:
> Original commit did not allocate IRQs for the SMMUv3 in the irqmap
> effectively using irq 0->3 (shared with other devices). Assuming
> original intent was to allocate unique IRQs then add an allocation
> to the irqmap.
>
> Fixes: e9fdf453240 ("hw/arm:
1 - 100 of 568 matches
Mail list logo
