Peter Xu writes:
> On Thu, May 25, 2023 at 03:08:35PM +0200, Markus Armbruster wrote:
>> Andrei Gudkov writes:
>>
>> > Rewrote calc-dirty-rate documentation. Briefly described
>> > different modes of dirty page rate measurement. Added some
>> > examples. Fixed obvious grammar errors.
>> >
>> >
writes:
> On Thu, May 25, 2023 at 03:08:35PM +0200, Markus Armbruster wrote:
>> Andrei Gudkov writes:
>>
>> > Rewrote calc-dirty-rate documentation. Briefly described
>> > different modes of dirty page rate measurement. Added some
>> > examples. Fixed obvious grammar errors.
>> >
>> > Signed-of
GTK3 provides the infrastructure to receive and process multi-touch
events through the "touch-event" signal and the GdkEventTouch type.
Make use of it to transpose events from the host to the guest.
This allows users of machines with hardware capable of receiving
multi-touch events to run guests t
This series adds a virtio-multitouch device to the family of devices emulated
by virtio-input implementing the Multi-touch protocol as descripted here:
https://www.kernel.org/doc/html/latest/input/multi-touch-protocol.html?highlight=multi+touch
It also extends the GTK UI backend to be able to rec
Add the required infrastructure to support generating multitouch events.
Signed-off-by: Sergio Lopez
Reviewed-by: Marc-André Lureau
Reviewed-by: Markus Armbruster
---
include/ui/input.h| 3 ++
qapi/ui.json | 68 +--
replay/replay-input.c |
As there are other bitmap-based config properties that need to be dealt in a
similar fashion as VIRTIO_INPUT_CFG_EV_BITS, generalize the function to
receive select and subsel as arguments, and rename it to
virtio_input_extend_config()
Signed-off-by: Sergio Lopez
Reviewed-by: Marc-André Lureau
--
Add helpers for generating Multi-touch events from the UI backends that
can be sent to the guest through a virtio-multitouch device.
Signed-off-by: Sergio Lopez
Reviewed-by: Marc-André Lureau
---
include/ui/input.h | 5 +
ui/input.c | 36
2 file
Add virtio-multitouch-pci, a Multitouch-capable input device, to the
list of devices that can be provided by virtio-input-pci.
Signed-off-by: Sergio Lopez
Reviewed-by: Marc-André Lureau
---
hw/virtio/virtio-input-pci.c | 25 +
1 file changed, 21 insertions(+), 4 deletion
Add a virtio-multitouch device to the family of devices emulated by
virtio-input implementing the Multi-touch protocol as descripted here:
https://www.kernel.org/doc/html/latest/input/multi-touch-protocol.html?highlight=multi+touch
This patch just add the device itself, without connecting it to a
Queued, thanks.
Paolo
On Fri, May 26, 2023 at 10:19:21AM +0200, Paolo Bonzini wrote:
> Queued, thanks.
The second patch looks incomplete to me.
With regards,
Daniel
--
|: https://berrange.com -o-https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o-https://fstop138.berrang
Am 26.05.23 um 10:55 schrieb Juan Quintela:
> Fiona Ebner wrote:
>> Am 18.05.23 um 19:13 schrieb Juan Quintela:
>>> diff --git a/migration/migration-stats.c b/migration/migration-stats.c
>>> index feec7d7369..97759a45f3 100644
>>> --- a/migration/migration-stats.c
>>> +++ b/migration/migration-sta
A few code paths exist in the source code,where a migration is
marked as failed via MIGRATION_STATUS_FAILED, but the failure happens
outside of migration.c
In such cases, an error_report() call is made, however the current
MigrationState is never updated with the error description, and hence
clien
Currently, a few code paths exist in the function vmstate_save_state_v,
which ultimately leads to a migration failure. However, an update in the
current MigrationState for the error description is never done.
vmstate.c somehow doesn't seem to allow the use of migrate_set_error due
to some dependen
Hi everyone,
This patchset aims to cover code paths in the source code where a
migration is marked as failed via MIGRATION_STATUS_FAILED, however the
failure exists outside of migration.c, and without a call for
migrate_set_error at this place.
This patchset has been split out from the patchs
These functions will be required by the GDB stub in order to provide
the guest view of /proc to GDB.
Reviewed-by: Alex Bennée
Signed-off-by: Ilya Leoshkevich
---
linux-user/qemu.h| 3 +++
linux-user/syscall.c | 54
2 files changed, 38 insertions
These functions will be needed by user-target.c in order to retrieve
the name of the executable.
Reviewed-by: Alex Bennée
Signed-off-by: Ilya Leoshkevich
---
gdbstub/gdbstub.c | 16
gdbstub/internals.h | 2 ++
2 files changed, 10 insertions(+), 8 deletions(-)
diff --git a/g
v1: https://lists.gnu.org/archive/html/qemu-devel/2023-05/msg02614.html
v1 -> v2: Reword the 5/6 commit message (Dominik).
Add R-bs.
Patches that need review:
4/6 gdbstub: Add support for info proc mappings
6/6 tests/tcg: Add a test for info proc mappings
Hi
Add a small test to prevent regressions.
Since there are issues with how GDB interprets QEMU's target.xml,
enable the test only on aarch64 and s390x for now.
Signed-off-by: Ilya Leoshkevich
---
tests/tcg/aarch64/Makefile.target | 3 +-
tests/tcg/multiarch/Makefile.target |
Now that the GDB stub explicitly implements reading host files (note
that it was already possible by changing the emulated code to open and
read those files), concerns may arise that it undermines security.
Document the status quo, which is that the users are already
responsible for securing the G
Currently qemu-user reports pid 1 to GDB. Resolve the TODO and report
the actual PID. Using getpid() relies on the assumption that there is
only one GDBProcess. Add an assertion to make sure that future changes
don't break it.
Reviewed-by: Alex Bennée
Signed-off-by: Ilya Leoshkevich
---
gdbstub
Currently the GDB's generate-core-file command doesn't work well with
qemu-user: the resulting dumps are huge [1] and at the same time
incomplete (argv and envp are missing). The reason is that GDB has no
access to proc mappings and therefore has to fall back to using
heuristics for discovering the
On Mon, Apr 24, 2023 at 10:53:36AM +0100, Daniel P. Berrangé wrote:
> On Fri, Apr 21, 2023 at 11:59:25PM +0200, Juan Quintela wrote:
> > Daniel P. Berrangé wrote:
> > > When running migration tests we monitor for a STOP event so we can skip
> > > redundant waits. This will be needed for the RESUME
On Tue, 23 May 2023, BALATON Zoltan wrote:
Unrelated to this patch I also started to see random crashes with a DSI on a
dcbz instruction now which did not happen before (or not frequently enough
for me to notice). I did not bisect that as it happens randomly but I wonder
if it could be related
Currently, it is only done when the iteration finishes successfully.
Not cleaning up the userfaultfd write protection can lead to
symptoms/issues such as the process hanging in memmove or GDB not
being able to attach.
Signed-off-by: Fiona Ebner
---
For the success case, the stuff in between the
This series improves the pflash usage in RISC-V virt machine with solutions to
below issues.
1) Currently the first pflash is reserved for ROM/M-mode firmware code. But
S-mode
payload firmware like EDK2 need both pflash devices to have separate code and
variable
store so that OS distros can keep
pflash devices can be used in virt machine for different
purposes like for ROM code or S-mode FW payload. Add a
section in the documentation on how to use pflash devices
for different purposes.
Signed-off-by: Sunil V L
---
docs/system/riscv/virt.rst | 29 +
1 file cha
Currently, virt machine supports two pflash instances each with
32MB size. However, the first pflash is always assumed to
contain M-mode firmware and reset vector is set to this if
enabled. Hence, for S-mode payloads like EDK2, only one pflash
instance is available for use. This means both code and
Ján Tomko writes:
> On a Friday in 2023, Markus Armbruster wrote:
>>> { "sandbox", NULL, QEMU_CAPS_SECCOMP_SANDBOX },
>>
>>Does option -sandbox exist?
>>
>>It does since v1.2. If CONFIG_SECCOMP is off, actually using it is a
>>fatal error. Compiling out the option entirely would be more use
Currently, pflash devices can be configured only via -pflash
or -drive options. This is the legacy way and the
better way is to use -blockdev as in other architectures.
libvirt also has moved to use -blockdev method.
To support -blockdev option, pflash devices need to be
created in instance_init i
On 5/25/23 20:02, Andrey Drobyshev wrote:
In case when we're rebasing within one backing chain, and when target image
is larger than old backing file, bdrv_is_allocated_above() ends up setting
*pnum = 0. As a result, target offset isn't getting incremented, and we
get stuck in an infinite for lo
On 5/25/23 20:02, Andrey Drobyshev wrote:
Before previous commit, rebase was getting infitely stuck in case of
rebasing within the same backing chain and when overlay_size > backing_size.
Let's add this case to the rebasing test 024 to make sure it doesn't
break again.
Signed-off-by: Andrey Drob
On 8/11/22 19:30, Cédric Le Goater wrote:
On 8/11/22 18:40, Nicholas Piggin wrote:
The chiptod is a pervasive facility which can keep a time, synchronise
it across multiple chips, and can move that time to or from the core
timebase units.
This adds a very basic initial emulation of chiptod regi
On 8/11/22 10:04, Cédric Le Goater wrote:
On 8/11/22 09:54, Nicholas Piggin wrote:
The SBE (Self Boot Engine) are on-chip microcontrollers that perform
early boot steps, as well as provide some runtime facilities (e.g.,
timer, secure register access, MPIPL). The latter facilities are
accessed mo
On Wed, May 24, 2023 at 11:37:39AM +0200, Philippe Mathieu-Daudé wrote:
Instead of adding 'vhost-vsock-common.c' twice (for VHOST_VSOCK
and VHOST_USER_VSOCK), have it depend on VHOST_VSOCK_COMMON,
selected by both symbols.
Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by: Richard Henderson
Re
On Wed, May 24, 2023 at 11:37:41AM +0200, Philippe Mathieu-Daudé wrote:
Instead of having "virtio/virtio-bus.h" implicitly included,
explicitly include it, to avoid when rearranging headers:
hw/virtio/vhost-vsock-common.c: In function ‘vhost_vsock_common_start’:
hw/virtio/vhost-vsock-common.c:
On Fri, May 26, 2023 at 05:40:03PM +0530, Sunil V L wrote:
> This series improves the pflash usage in RISC-V virt machine with solutions to
> below issues.
>
> 1) Currently the first pflash is reserved for ROM/M-mode firmware code. But
> S-mode
> payload firmware like EDK2 need both pflash devices
pci-ohci might habe been disabled in the QEMU binary (e.g. when "configure"
has been run with "--without-default-devices"). Thus we should check
for its availability before blindly using it.
Signed-off-by: Thomas Huth
---
hw/ppc/mac_newworld.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion
Jonathan Cameron writes:
> Inject poison using qmp command cxl-inject-poison to add an entry to the
QMP command
> poison list.
>
> For now, the poison is not returned CXL.mem reads, but only via the
> mailbox command Get Poison List. So a normal memory read to an address
> that is on the poison
Daniel P. Berrangé writes:
> On Thu, May 25, 2023 at 06:20:44PM -0300, Fabiano Rosas wrote:
>> We recently moved glib detection code to meson but the static libs
>> were left out. Add a specific dependency for stress.c which is linked
>> statically.
>>
>> $ make V=1 tests/migration/initrd-stress
Jonathan Cameron writes:
> From: Ira Weiny
>
> To facilitate testing provide a QMP command to inject a general media
> event. The event can be added to the log specified.
>
> Signed-off-by: Ira Weiny
> Signed-off-by: Jonathan Cameron
>
> ---
> v7: Various docs updates and field renames includ
Jonathan Cameron writes:
> Defined in CXL r3.0 8.2.9.2.1.2 DRAM Event Record, this event
> provides information related to DRAM devices.
>
> Example injection command in QMP:
>
> { "execute": "cxl-inject-dram-event",
> "arguments": {
> "path": "/machine/peripheral/cxl-mem0",
>
Jonathan Cameron writes:
> These events include a copy of the device health information at the
> time of the event. Actually using the emulated device health would
> require a lot of controls to manipulate that state. Given the aim
> of this injection code is to just test the flows when events o
On Fri, 26 May 2023, Thomas Huth wrote:
pci-ohci might habe been disabled in the QEMU binary (e.g. when "configure"
has been run with "--without-default-devices"). Thus we should check
for its availability before blindly using it.
Signed-off-by: Thomas Huth
---
hw/ppc/mac_newworld.c | 3 ++-
1 f
On 15.05.23 09:36, Jean-Louis Dupond wrote:
When we for example have a sparse qcow2 image and discard: unmap is enabled,
there can be a lot of fragmentation in the image after some time. Surely on VM's
that do a lot of writes/deletes.
This causes the qcow2 image to grow even over 110% of its virt
On Fri, May 26, 2023 at 01:23:07PM +0200, Markus Armbruster wrote:
> Going with
>
> # 2. Dirty bitmap mode captures writes to memory (for example by
> #temporarily revoking write access to all pages) and counting page
> #faults. Information about modified pages is collec
Am 26.05.23 um 12:16 schrieb Juan Quintela:
> Nak
>
> Sometimes it works, and sometimes it hangs.
Sorry, I originally only ran the tests for x86_64 (native for me). I now
ran into the hang too, with qtest-aarch64/migration-test and
qtest-i386/migration-test.
> Can you take a look?
Will do!
Bes
On 26/5/23 14:10, Sunil V L wrote:
Currently, pflash devices can be configured only via -pflash
or -drive options. This is the legacy way and the
better way is to use -blockdev as in other architectures.
libvirt also has moved to use -blockdev method.
To support -blockdev option, pflash devices
On 26/5/23 14:10, Sunil V L wrote:
pflash devices can be used in virt machine for different
purposes like for ROM code or S-mode FW payload. Add a
section in the documentation on how to use pflash devices
for different purposes.
Signed-off-by: Sunil V L
---
docs/system/riscv/virt.rst | 29 +++
[Side topic]
Would folks be interested in a Linux Plumbers Conference MC on this
topic generally, across different hypervisors, VMMs, and architectures?
If so, please let me know who the key folk would be and we can try writing
up an MC proposal.
--
James Morris
Eric Blake writes:
> On Tue, May 23, 2023 at 06:39:00PM -0300, Fabiano Rosas wrote:
>> From: Lin Ma
>>
>> Sometimes the query-block performs time-consuming I/O(say waiting for
>> the fstat of NFS complete), So let's make this QMP handler runs in a
>> coroutine.
>
> Grammar suggestions:
>
> Some
From: Marco Liebel
The order in which instructions are generated by gen_insn() influences
assignment to tmp registers. During generation, tmp instructions (e.g.
generate_V6_vassign_tmp) use vreg_src_off() to determine what kind of
register to use as source. If some instruction (e.g.
generate_V6_v
Eric Blake writes:
> On Tue, May 23, 2023 at 06:39:03PM -0300, Fabiano Rosas wrote:
>> From: João Silva
>>
>> The fstat call can take a long time to finish when running over
>> NFS. Add a version of it that runs in the thread pool.
>>
>> Adapt one of its users, raw_co_get_allocated_file size t
From: Matheus Tavares Bernardino
Some code comments refer to hex_new_value and hex_new_pred_value, which
have been transferred to DisasContext and, in the case of hex_new_value,
should now be accessed through get_result_gpr().
In order to fix this outdated comments and also avoid having to tweak
Change Hexagon maintainer from Taylor Simpson to Brian Cain
Put Taylor's gmail address in .mailmap
Signed-off-by: Taylor Simpson
Reviewed-by: Alex Bennée
---
MAINTAINERS | 2 +-
.mailmap| 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 1c93
From: Matheus Tavares Bernardino
Many Hexagon python scripts call hex_common.get_tagregs(), but only one
call site use the full reg structure given by this function. To make the
code cleaner, let's make get_tagregs() filter out the unused fields
(i.e. 'toss' and 'numregs'), properly removed the u
The following changes since commit a3cb6d5004ff638aefe686ecd540718a793bd1b1:
Merge tag 'pull-tcg-20230525' of https://gitlab.com/rth7680/qemu into staging
(2023-05-25 11:11:52 -0700)
are available in the Git repository at:
https://github.com/quic/qemu tags/pull-hex-20230526
On Thu, May 25, 2023 at 08:30:03PM +0200, Markus Armbruster wrote:
Stefan Hajnoczi writes:
On Wed, May 17, 2023 at 09:19:26AM +0200, Stefano Garzarella wrote:
CCing Markus for some advice.
On Tue, May 16, 2023 at 11:04:21AM -0500, Jonathon Jongsma wrote:
[...]
> I need some way to determ
On 5/25/23 19:56, fa...@mail.ustc.edu.cn wrote:
"The beginning of the structure, with pretaddr, should be just below 16-byte
alignment."
It is incorrect! The beginning of the structure, with pretaddr not aligned as
16-byte!
On x86-64, It aligned as (16n - sizeof(void*)) because of instruction
On Mon, 3 Apr 2023 21:19:53 -0400
Dinah Baum wrote:
> Part 1 is a refactor/code motion patch for
> qapi/machine target required for setup of
>
> Part 2 which enables query-cpu-model-expansion
> on all architectures
>
> Part 3 implements the ',help' feature
>
> Limitations:
> Currently only 'F
On Thu, May 25, 2023 at 02:47:09PM +0200, Kevin Wolf wrote:
> The AioContext lock must not be held for bdrv_open_child(), but it is
> necessary for the followig operations, in particular those using nested
following
> event loops in coroutine wrappers.
>
> Temporarily dropping the main AioContex
On 26/05/2023 15:31, Hanna Czenczek wrote:
On 15.05.23 09:36, Jean-Louis Dupond wrote:
When we for example have a sparse qcow2 image and discard: unmap is
enabled,
there can be a lot of fragmentation in the image after some time.
Surely on VM's
that do a lot of writes/deletes.
This causes the
On Fri, May 26, 2023 at 12:24:07PM +0530, Prasad Pandit wrote:
> Hello Peter, all
>
> On Thu, 25 May 2023 at 18:33, Peter Xu wrote:
>
> > IIRC this bug used to only reproduce on rt kernels, is it still the case?
> >
>
> * Yes, it's a same crash.
>
>
> > Here besides doing correct unregister,
On Fri, May 26, 2023 at 01:10:51PM +0530, P J P wrote:
> From: Prasad Pandit
>
> vhost_dev_start function does not release memory objects in case
> of an error. This may crash the guest with:
>
> stack trace of thread 125653:
> Program terminated with signal SIGSEGV, Segmentation fault
> #
On 5/26/23 02:49, Juan Quintela wrote:
Philippe Mathieu-Daudé wrote:
Hi,
On 26/5/23 01:25, Richard Henderson wrote:
Document the meaning of exclusive_high in a big-endian context,
and why we can't change it now.
Signed-off-by: Richard Henderson
---
target/arm/cpu.h | 7 +++
1 file c
v4:
- added patch 02 to allow libvirt to discover we support fdset [Markus]
- modified the commit description of patch 01
v3:
https://lore.kernel.org/qemu-devel/20230511091527.46620-1-sgarz...@redhat.com/
- use qemu_open() on `path` to simplify libvirt code [Jonathon]
- remove patch 01 since we a
Some virtio-blk drivers (e.g. virtio-blk-vhost-vdpa) supports the fd
passing. Let's expose this to the user, so the management layer
can pass the file descriptor of an already opened path.
If the libblkio virtio-blk driver supports fd passing, let's always
use qemu_open() to open the `path`, so we
The virtio-blk-vhost-vdpa driver in libblkio 1.3.0 supports the fd
passing through the new 'fd' property.
Since now we are using qemu_open() on '@path' if the virtio-blk driver
supports the fd passing, let's announce it.
In this way, the management layer can pass the file descriptor of an
already
On 25/05/2023 15:59, Mickaël Salaün wrote:
On 25/05/2023 00:20, Edgecombe, Rick P wrote:
On Fri, 2023-05-05 at 17:20 +0200, Mickaël Salaün wrote:
# How does it work?
This implementation mainly leverages KVM capabilities to control the
Second
Layer Address Translation (or the Two Dimensional
QEMU v8.0 is able to switch dynamically between vhost-vdpa passthrough
and SVQ mode as long as the net device does not have CVQ. The net device
state followed (and migrated) by CVQ requires special care.
A pre-requisite to add CVQ to that framework is to determine if devices with
CVQ are migratab
We need to tell in the caller, as some errors are expected in a normal
workflow. In particular, parent drivers in recent kernels with
VHOST_BACKEND_F_IOTLB_ASID may not support vring groups. In that case,
-ENOTSUP is returned.
This is the case of vp_vdpa in Linux 6.2.
Next patches in this serie
Evaluating it at start time instead of initialization time may make the
guest capable of dynamically adding or removing migration blockers.
Also, moving to initialization reduces the number of ioctls in the
migration, reducing failure possibilities.
As a drawback we need to check for CVQ isolatio
On Wed, May 24, 2023 at 04:53:49PM +0200, Anthony Harivel wrote:
> set=UTF-8
> Status: RO
> Content-Length: 24102
> Lines: 667
>
> Marcelo Tosatti, May 19, 2023 at 20:28:
>
> Hi Marcelo,
>
> > > > > +/* Assuming those values are the same accross physical
> > > > > system/packages */
> > > >
On 25/05/2023 17:52, Edgecombe, Rick P wrote:
On Thu, 2023-05-25 at 15:59 +0200, Mickaël Salaün wrote:
[ snip ]
The kernel often creates writable aliases in order to write to
protected data (kernel text, etc). Some of this is done right as
text
is being first written out (alternatives for exa
It is always 0 and it is not useful to route call through file
descriptor.
Reviewed-by: Stefano Garzarella
Acked-by: Jason Wang
Signed-off-by: Eugenio Pérez
---
Commit extracted from series [1], Message-Id
<20230509154435.1410162-1-epere...@redhat.com>, as this change is not
needed anymore the
On 5/26/23 01:02, Thomas Huth wrote:
What output do you get when running the tests directly? i.e.:
cd tests/qemu-iotests/
./check -qcow2 150
=== Mapping non-sparse conversion ===
Offset Length File
-0 0x10TEST_DIR/t.IMGFMT
+0 0x1
Am 26.05.23 um 15:47 schrieb Fiona Ebner:
> Am 26.05.23 um 12:16 schrieb Juan Quintela:
>> Nak
>>
>> Sometimes it works, and sometimes it hangs.
>
> Sorry, I originally only ran the tests for x86_64 (native for me). I now
> ran into the hang too, with qtest-aarch64/migration-test and
> qtest-i386/
On 5/26/23 01:18, Paolo Bonzini wrote:
qatomic_mb_read and qatomic_mb_set were the very first atomic primitives
introduced for QEMU; their semantics are unclear and they provide a false
sense of safety.
The last use of qatomic_mb_read() has been removed, so delete it.
qatomic_mb_set() instead ca
On 5/26/23 03:19, Daniel P. Berrangé wrote:
The CI rules have special logic for what happens in upstream. To enable
contributors who modify CI rules to test this logic, however, they need
to be able to override which repo is considered upstream. This
introduces the 'QEMU_CI_UPSTREAM' variable
On 5/26/23 03:19, Daniel P. Berrangé wrote:
If the stable staging branches publish containers under the 'latest' tag
they will clash with containers published on the primary staging branch,
as well as with each other. This introduces logic that overrides the
container tag when jobs run against t
On 5/26/23 03:19, Daniel P. Berrangé wrote:
In upstream context we only run pipelines on staging branches, and
limited publishing jobs on the default branch.
We don't want to run pipelines on stable branches, or tags, because
the content will have already been tested on a staging branch before
g
On 5/26/23 03:19, Daniel P. Berrangé wrote:
+# Upstream pipeline jobs start automatically unless told not to
+# by setting QEMU_CI=1
+- if: '$QEMU_CI == "1" && $CI_PROJECT_NAMESPACE == $QEMU_CI_UPSTREAM &&
$CI_COMMIT_BRANCH =~/staging/'
+ when: manual
+ variables:
+
From: Fabiano Rosas
We recently moved glib detection code to meson but this changes the
linker command line from -lglib-2.0 to using a path to libglib-2.0.so.
This does not work for static linking, which is used by stress.c:
$ make V=1 tests/migration/initrd-stress.img
cc -m64 -mcx16 -o tests/
By using a subproject, our own meson.build can use variables from
the subproject instead of hard-coded paths. This is also the first step
towards managing downloads with .wrap files instead of submodule.
Reviewed-by: Daniel P. Berrangé
Signed-off-by: Paolo Bonzini
---
.gitmodules
ARCH is always empty, so just define HOST_ARCH as the result of uname.
The incorrect definition was not being used because the "ifeq" statement
is wrong; replace it with the same idiom based on $(realpath) that the
main Makefile uses.
With this change, vm-build-netbsd in a configured tree will not
It is now the same as $(PYTHON), since the latter always points at
pyvenv/bin/python3.
Reviewed-by: Alex Bennée
Signed-off-by: Paolo Bonzini
---
tests/Makefile.include| 8 +++-
tests/vm/Makefile.include | 2 +-
2 files changed, 4 insertions(+), 6 deletions(-)
diff --git a/tests/Makefi
ARCH is always empty, so just define HOST_ARCH as the result of uname.
Acked-by: Alex Bennée
Signed-off-by: Paolo Bonzini
---
tests/docker/Makefile.include | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/docker/Makefile.include b/tests/docker/Makefile.include
index 940
fdt_opt == 'disabled' is going to give an error if libfdt is required
by any target, so catch that immediately. For fdt_opt == 'enabled',
instead, do not check immediately whether the internal libfdt is present.
Instead do the check after ascertaining that libfdt is absent or too old.
Reviewed-by
Recent dtc/libfdt can use either Make or meson as the build system.
By using a subproject, our own meson.build can remove the hard
coded list of source files.
This is also the first step towards managing downloads with .wrap
files instead of submodule.
Reviewed-by: Daniel P. Berrangé
Signed-off-
The VirtioInfoList is already allocated by QAPI_LIST_PREPEND and
need not be allocated by the caller.
Fixes Coverity CID 1508724.
Reviewed-by: Daniel P. Berrangé
Signed-off-by: Paolo Bonzini
---
hw/virtio/virtio-qmp.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --gi
The following changes since commit a3cb6d5004ff638aefe686ecd540718a793bd1b1:
Merge tag 'pull-tcg-20230525' of https://gitlab.com/rth7680/qemu into staging
(2023-05-25 11:11:52 -0700)
are available in the Git repository at:
https://gitlab.com/bonzini/qemu.git tags/for-upstream
for you to fe
See James Morris's proposal here:
https://lore.kernel.org/all/17f62cb1-a5de-2020-2041-359b8e96b...@linux.microsoft.com/
On 26/05/2023 04:36, James Morris wrote:
> [Side topic]
>
> Would folks be interested in a Linux Plumbers Conference MC on this
> topic generally, across different hypervisors,
From: Fabiano Rosas
Commit d2e6f9272d ("fuzz: remove fork-fuzzing scaffolding") removed
the linker script and forgot to remove the comment.
Signed-off-by: Fabiano Rosas
Message-Id: <20230525212044.30222-2-faro...@suse.de>
Signed-off-by: Paolo Bonzini
---
meson.build | 2 --
1 file changed, 2
Setting the MAKE variable to a GNU Make executable does not really have
any effect: if a non-GNU Make is used, the QEMU Makefile will fail to
parse. Just remove everything related to --make and $make as dead code.
Signed-off-by: Paolo Bonzini
---
configure | 18 +-
meson.build
Apart from CLICOLOR_FORCE and GREP_OPTIONS, there are other variables
that are listed in the Autoconf manual. While Autoconf neutralizes them
very early, and assumes it does not (yet) run in a shell that has "unset",
QEMU assumes that the user invoked configure under a POSIX shell, and
therefore c
It is recommended to use SSIZE_T for ssize_t on win32, but the commit
that is being used for slirp.wrap uses int. Update to include the fix
as well as the other bugfix commit "ip: Enforce strict aliasing".
Reported-by: Michael Tokarev
Signed-off-by: Paolo Bonzini
---
subprojects/slirp.wrap | 2
On 5/24/23 06:39, Alex Bennée wrote:
We weren't using cs_base in the hash calculations before. Since the
arm front end moved a chunk of flags in a378206a20 (target/arm: Move
mode specific TB flags to tb->cs_base) they comprise of an important
part of the execution state.
Widen the tb_hash_func t
On 5/26/23 02:08, Thomas Huth wrote:
The following changes since commit a3cb6d5004ff638aefe686ecd540718a793bd1b1:
Merge tag 'pull-tcg-20230525' ofhttps://gitlab.com/rth7680/qemu into
staging (2023-05-25 11:11:52 -0700)
are available in the Git repository at:
https://gitlab.com/thuth/qe
om/gaosong/qemu.git tags/pull-loongarch-20230526
for you to fetch changes up to 65bfaaae6ac79ebc623acc0ce28cc3bd4fe8b5e5:
target/loongarch: Fix the vinsgr2vr/vpickve2gr instructions cause system
coredump (2023-05-26 17:21:16 +0800)
---
Signed-off-by: Rajnesh Kanwal
---
target/riscv/csr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/riscv/csr.c b/target/riscv/csr.c
index 4451bd1263..041f0b3e2e 100644
--- a/target/riscv/csr.c
+++ b/target/riscv/csr.c
@@ -1522,7 +1522,7 @@ static RISCVException rmw_mi
101 - 200 of 287 matches
Mail list logo
