Hi Volker,
> Did you see my patches at
> https://lists.nongnu.org/archive/html/qemu-devel/2022-12/msg02895.html ?
> Patches 01/11 and 02/11 prevent the disturbing error message from
> audio_calloc and later patches remove the audio_calloc function.
>
Oh, I missed these. Thank you for pointing it
Does it make sense to just allocate 4k of memory or so?
Paolo
Il mer 28 dic 2022, 03:55 Wang, Wenchao ha scritto:
> Hi, Paolo,
>
>
>
> Thanks for your reply.
>
>
>
> The reason why the variable xcr0 must be added to the header file of QEMU
> is because HAXM needs QEMU to allocate memory from us
Il ven 23 dic 2022, 16:54 Peter Xu ha scritto:
> > This is not valid because the transaction could happen in *another*
> thread.
> > In that case memory_region_transaction_depth() will be > 0, but RCU is
> > needed.
>
> Do you mean the code is wrong, or the comment? Note that the code has
> chec
On 12/2/2022 2:13 PM, Chao Peng wrote:
> In confidential computing usages, whether a page is private or shared is
> necessary information for KVM to perform operations like page fault
> handling, page zapping etc. There are other potential use cases for
> per-page memory attributes, e.g. to make
Hi, Paolo,
Thanks for your question.
This buffer is only used by the interfaces of ioctl(HAX_VCPU_SET_REGS) or
ioctl(HAX_VCPU_GET_REGS). It is currently sizeof(struct vcpu_state_t), which is
changed by the patch. Currently, the parameters passed by different ioctl() are
not same, so it may not
It should be the variable rdl2 to revert the already-notified listeners.
Fixes: 2044969f0b ("virtio-mem: Implement RamDiscardManager interface")
Signed-off-by: Chenyi Qiang
---
hw/virtio/virtio-mem.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/virtio/virtio-mem.c b/hw/
On Tue, 2022-12-20 at 17:29 +, David Woodhouse wrote:
> On 20 December 2022 17:25:31 GMT, Paul Durrant wrote:
> > On 20/12/2022 16:27, David Woodhouse wrote:
> > >
> > >
> > > On 20 December 2022 13:56:39 GMT, Paul Durrant
> > > wrote:
> > > > The callback via is essentially just another li
On 23/12/22 15:23, Chuang Xu wrote:
Before using any flatview, sanity check we're not during a memory
region transaction or the map can be invalid.
Signed-off-by: Chuang Xu
---
include/exec/memory.h | 9 +
softmmu/memory.c | 5 +
2 files changed, 14 insertions(+)
diff --gi
On Tue, 27 Dec 2022 17:49:04 -0300
Matheus Tavares Bernardino wrote:
> Signed-off-by: Matheus Tavares Bernardino
> ---
> target/hexagon/idef-parser/README.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Reviewed-by: Alessandro Di Federico
Thanks for the fixes!
--
Alessandro
On Wednesday, December 21, 2022 7:02:43 PM CET Shi, Guohuai wrote:
>
> > -Original Message-
> > From: Christian Schoenebeck
> > Sent: Wednesday, December 21, 2022 22:48
> > To: Greg Kurz ; qemu-devel@nongnu.org
> > Cc: Shi, Guohuai ; Meng, Bin
> >
> > Subject: Re: [PATCH v3 07/17] hw/9pf
On 28/12/22 10:03, Chenyi Qiang wrote:
It should be the variable rdl2 to revert the already-notified listeners.
Fixes: 2044969f0b ("virtio-mem: Implement RamDiscardManager interface")
Signed-off-by: Chenyi Qiang
---
hw/virtio/virtio-mem.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On 27/12/22 21:49, Matheus Tavares Bernardino wrote:
Signed-off-by: Matheus Tavares Bernardino
---
target/hexagon/idef-parser/README.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Reviewed-by: Philippe Mathieu-Daudé
Hi,
In this new version I rebased the patches on top of
"[PATCH 00/12] hw/riscv: Improve Spike HTIF emulation fidelity"
from Bin Meng. Patches 4 and 5 from v1 got removed since Bin picked
them in the HTIF changes.
I also removed patches 13, 14 and 15 because I have another cleanup
already plann
The sifive_u, spike and virt machines are writing the 'bootargs' FDT
node during their respective create_fdt().
Given that bootargs is written only when '-append' is used, and this
option is only allowed with the '-kernel' option, which in turn is
already being check before executing riscv_load_ke
The microchip_icicle_kit, sifive_u, spike and virt boards are now doing
the same steps when '-kernel' is used:
- execute load_kernel()
- load init_rd()
- write kernel_cmdline
Let's fold everything inside riscv_load_kernel() to avoid code
repetition. Every other board that uses riscv_load_kernel()
The only remaining caller is riscv_load_kernel() which belongs to the
same file.
Signed-off-by: Daniel Henrique Barboza
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Bin Meng
---
hw/riscv/boot.c | 76 -
include/hw/riscv/boot.h | 1 -
2 files
The MachineState object provides a 'fdt' pointer that is already being
used by other RISC-V machines, and it's also used by the 'dumpdtb' QMP
command.
Remove the 'fdt' pointer from SpikeState and use MachineState::fdt
instead.
Signed-off-by: Daniel Henrique Barboza
Reviewed-by: Philippe Mathieu-
riscv_load_initrd() returns the initrd end addr while also writing a
'start' var to mark the addr start. These informations are being used
just to write the initrd FDT node. Every existing caller of
riscv_load_initrd() is writing the FDT in the same manner.
We can simplify things by writing the FD
This will make the code more in line with what the other boards are
doing. We'll also avoid an extra check to machine->kernel_filename since
we already checked that before executing riscv_load_kernel().
Signed-off-by: Daniel Henrique Barboza
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Alist
'filename', 'mem_size' and 'fdt' from riscv_load_initrd() can all be
retrieved by the MachineState object for all callers.
Cc: Palmer Dabbelt
Signed-off-by: Daniel Henrique Barboza
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Bin Meng
---
hw/riscv/boot.c| 6 --
hw/riscv/mi
All callers are using kernel_filename as machine->kernel_filename.
This will also simplify the changes in riscv_load_kernel() that we're
going to do next.
Cc: Palmer Dabbelt
Signed-off-by: Daniel Henrique Barboza
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Bin Meng
---
hw/riscv/boot.c
The MachineState object provides a 'fdt' pointer that is already being
used by other RISC-V machines, and it's also used by the 'dumpdtb' QMP
command.
Remove the 'fdt' pointer from SiFiveUState and use MachineState::fdt
instead.
Cc: Palmer Dabbelt
Signed-off-by: Daniel Henrique Barboza
Reviewed
When called from syscall(), we are not within a TB and pc == 0.
We can skip the check for invalidating the current TB.
Signed-off-by: Richard Henderson
[PMD: Split patch in 2]
Signed-off-by: Philippe Mathieu-Daudé
---
accel/tcg/tb-maint.c | 17 -
1 file changed, 12 insertions(+)
On 28/12/22 13:49, Philippe Mathieu-Daudé wrote:
Signed-off-by: Richard Henderson
[PMD: Split patch in 2]
Signed-off-by: Philippe Mathieu-Daudé
---
accel/tcg/tb-maint.c | 53 ++--
1 file changed, 27 insertions(+), 26 deletions(-)
Reviewed-by: Philipp
This test is used to do a quick sanity check to ensure that we're able
to run the existing QEMU FW image.
'sifive_u', 'spike' and 'virt' riscv64 machines, and 'sifive_u' and
'virt' 32 bit machines are able to run the default RISCV64_BIOS_BIN |
RISCV32_BIOS_BIN firmware with minimal options.
The r
Signed-off-by: Richard Henderson
[PMD: Split patch in 2]
Signed-off-by: Philippe Mathieu-Daudé
---
accel/tcg/tb-maint.c | 53 ++--
1 file changed, 27 insertions(+), 26 deletions(-)
diff --git a/accel/tcg/tb-maint.c b/accel/tcg/tb-maint.c
index c9b8d3c6c3.
On 28/12/22 08:24, Philippe Mathieu-Daudé wrote:
On 24/12/22 16:18, Richard Henderson wrote:
As in page_get_flags, we need to try again with the mmap
lock held if we fail a page lookup.
Signed-off-by: Richard Henderson
---
accel/tcg/user-exec.c | 39 ---
On 28/12/22 13:42, Daniel Henrique Barboza wrote:
The microchip_icicle_kit, sifive_u, spike and virt boards are now doing
the same steps when '-kernel' is used:
- execute load_kernel()
- load init_rd()
- write kernel_cmdline
Let's fold everything inside riscv_load_kernel() to avoid code
repetit
On 28/12/22 13:49, Philippe Mathieu-Daudé wrote:
When called from syscall(), we are not within a TB and pc == 0.
We can skip the check for invalidating the current TB.
Signed-off-by: Richard Henderson
[PMD: Split patch in 2]
Signed-off-by: Philippe Mathieu-Daudé
---
accel/tcg/tb-maint.c | 17
On 28/12/22 13:42, Daniel Henrique Barboza wrote:
This test is used to do a quick sanity check to ensure that we're able
to run the existing QEMU FW image.
'sifive_u', 'spike' and 'virt' riscv64 machines, and 'sifive_u' and
'virt' 32 bit machines are able to run the default RISCV64_BIOS_BIN |
RI
On 12/28/22 09:56, Philippe Mathieu-Daudé wrote:
On 28/12/22 13:42, Daniel Henrique Barboza wrote:
The microchip_icicle_kit, sifive_u, spike and virt boards are now doing
the same steps when '-kernel' is used:
- execute load_kernel()
- load init_rd()
- write kernel_cmdline
Let's fold everyt
On 12/28/22 09:59, Philippe Mathieu-Daudé wrote:
On 28/12/22 13:42, Daniel Henrique Barboza wrote:
This test is used to do a quick sanity check to ensure that we're able
to run the existing QEMU FW image.
'sifive_u', 'spike' and 'virt' riscv64 machines, and 'sifive_u' and
'virt' 32 bit machi
When requesting the flatview output with 'info mtree -f',
the MemoryRegion priority is irrelevant and noise. Remove it.
Signed-off-by: Philippe Mathieu-Daudé
---
softmmu/memory.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/softmmu/memory.c b/softmmu/memory.c
index e
Signed-off-by: Philippe Mathieu-Daudé
---
hw/virtio/virtio-mem.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/hw/virtio/virtio-mem.c b/hw/virtio/virtio-mem.c
index d96bde1fab..c252027391 100644
--- a/hw/virtio/virtio-mem.c
+++ b/hw/virtio/virtio-mem.c
@@ -207,7
On 27/12/22 18:54, Michael S. Tsirkin wrote:
On Tue, Dec 27, 2022 at 05:43:57PM +0100, Philippe Mathieu-Daudé wrote:
On 27/12/22 08:20, Longpeng(Mike) wrote:
From: Longpeng
This allows the vhost device to batch the setup of all its host notifiers.
This significantly reduces the device startin
On 27/12/22 18:56, Michael S. Tsirkin wrote:
On Tue, Dec 27, 2022 at 05:51:47PM +0100, Philippe Mathieu-Daudé wrote:
On 27/12/22 08:20, Longpeng(Mike) wrote:
From: Longpeng
This allows the vhost-vdpa device to batch the setup of all its MRs of
host notifiers.
This significantly reduces the d
The MachineState object provides a 'fdt' pointer that is already being
used by other RISC-V machines, and it's also used by the 'dumpdtb' QMP
command.
Remove the 'fdt' pointer from SpikeState and use MachineState::fdt
instead.
Signed-off-by: Daniel Henrique Barboza
Reviewed-by: Philippe Mathieu-
riscv_load_initrd() returns the initrd end addr while also writing a
'start' var to mark the addr start. These informations are being used
just to write the initrd FDT node. Every existing caller of
riscv_load_initrd() is writing the FDT in the same manner.
We can simplify things by writing the FD
The microchip_icicle_kit, sifive_u, spike and virt boards are now doing
the same steps when '-kernel' is used:
- execute load_kernel()
- load init_rd()
- write kernel_cmdline in the fdt
Let's fold everything inside riscv_load_kernel() to avoid code
repetition. Every other board that uses riscv_lo
The sifive_u, spike and virt machines are writing the 'bootargs' FDT
node during their respective create_fdt().
Given that bootargs is written only when '-append' is used, and this
option is only allowed with the '-kernel' option, which in turn is
already being check before executing riscv_load_ke
All callers are using kernel_filename as machine->kernel_filename.
This will also simplify the changes in riscv_load_kernel() that we're
going to do next.
Cc: Palmer Dabbelt
Signed-off-by: Daniel Henrique Barboza
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Bin Meng
---
hw/riscv/boot.c
'filename', 'mem_size' and 'fdt' from riscv_load_initrd() can all be
retrieved by the MachineState object for all callers.
Cc: Palmer Dabbelt
Signed-off-by: Daniel Henrique Barboza
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Bin Meng
---
hw/riscv/boot.c| 6 --
hw/riscv/mi
This will make the code more in line with what the other boards are
doing. We'll also avoid an extra check to machine->kernel_filename since
we already checked that before executing riscv_load_kernel().
Signed-off-by: Daniel Henrique Barboza
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Alist
The only remaining caller is riscv_load_kernel_and_initrd() which
belongs to the same file.
Signed-off-by: Daniel Henrique Barboza
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Bin Meng
---
hw/riscv/boot.c | 76 -
include/hw/riscv/boot.h | 1
Hi,
This new version is still rebased on top of [1]:
"[PATCH 00/12] hw/riscv: Improve Spike HTIF emulation fidelity"
from Bin Meng. All the changes made were proposed by Phil in
the v2 review.
* Patches without reviews: 1, 9
Changes from v2:
- patch 1:
- reduced code repetition with a boot_
The MachineState object provides a 'fdt' pointer that is already being
used by other RISC-V machines, and it's also used by the 'dumpdtb' QMP
command.
Remove the 'fdt' pointer from SiFiveUState and use MachineState::fdt
instead.
Cc: Palmer Dabbelt
Signed-off-by: Daniel Henrique Barboza
Reviewed
This test is used to do a quick sanity check to ensure that we're able
to run the existing QEMU FW image.
'sifive_u', 'spike' and 'virt' riscv64 machines, and 'sifive_u' and
'virt' 32 bit machines are able to run the default RISCV64_BIOS_BIN |
RISCV32_BIOS_BIN firmware with minimal options.
The r
On Monday, December 26, 2022 4:08:37 PM CET Volker Rümelin wrote:
> Am 21.12.22 um 12:03 schrieb Christian Schoenebeck:
> > On Sunday, December 18, 2022 6:15:38 PM CET Volker Rümelin wrote:
> >> The currently used default playback settings in the ALSA audio
> >> backend are a bit unfortunate. With
On 28.12.22 14:09, Philippe Mathieu-Daudé wrote:
Signed-off-by: Philippe Mathieu-Daudé
---
hw/virtio/virtio-mem.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/hw/virtio/virtio-mem.c b/hw/virtio/virtio-mem.c
index d96bde1fab..c252027391 100644
--- a/hw/virti
On 28.12.22 10:03, Chenyi Qiang wrote:
It should be the variable rdl2 to revert the already-notified listeners.
Fixes: 2044969f0b ("virtio-mem: Implement RamDiscardManager interface")
Signed-off-by: Chenyi Qiang
---
hw/virtio/virtio-mem.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On 28.12.22 15:05, Philippe Mathieu-Daudé wrote:
On 27/10/21 14:45, David Hildenbrand wrote:
It's "virtio", not "virito".
Signed-off-by: David Hildenbrand
---
hw/virtio/virtio-mem.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
Reviewed-by: Philippe Mathieu-Daudé
On 27/10/21 14:45, David Hildenbrand wrote:
It's "virtio", not "virito".
Signed-off-by: David Hildenbrand
---
hw/virtio/virtio-mem.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
Reviewed-by: Philippe Mathieu-Daudé
diff --git a/hw/virtio/virtio-mem.c b/hw/virtio/vir
On Wed, 28 Dec 2022 at 15:06, David Hildenbrand wrote:
> On 28.12.22 15:05, Philippe Mathieu-Daudé wrote:
> > On 27/10/21 14:45, David Hildenbrand wrote:
> >> It's "virtio", not "virito".
> >>
> >> Signed-off-by: David Hildenbrand
> >> ---
> >>hw/virtio/virtio-mem.c | 12 ++--
> >>
From: Dongxue Zhang
Should be cpu->cfg.elen in range [8, 64].
Signed-off-by: Dongxue Zhang
---
target/riscv/cpu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/riscv/cpu.c b/target/riscv/cpu.c
index 6fe176e483..5dc51f7912 100644
--- a/target/riscv/cpu.c
+++ b/targe
From: Dongxue Zhang
Should be cpu->cfg.elen in range [8, 64].
Signed-off-by: Dongxue Zhang
---
target/riscv/cpu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/riscv/cpu.c b/target/riscv/cpu.c
index 6fe176e483..5dc51f7912 100644
--- a/target/riscv/cpu.c
+++ b/targe
The setup_data links are appended to the compressed kernel image. Since
the kernel image is typically loaded at 0x10, setup_data lives at
`0x10 + compressed_size`, which does not get relocated during the
kernel's boot process.
The kernel typically decompresses the image starting at address
On Wed, Dec 28, 2022 at 04:07:13AM +0100, Jason A. Donenfeld wrote:
> On Tue, Dec 27, 2022 at 02:36:54PM +0100, Jason A. Donenfeld wrote:
> > On Mon, Dec 26, 2022 at 05:57:30PM +0100, Jason A. Donenfeld wrote:
> > > On Mon, Dec 26, 2022 at 03:43:04PM +0100, Jason A. Donenfeld wrote:
> > > > On Mon,
On Wed, Dec 28, 2022 at 9:38 PM Daniel Henrique Barboza
wrote:
>
> This test is used to do a quick sanity check to ensure that we're able
> to run the existing QEMU FW image.
>
> 'sifive_u', 'spike' and 'virt' riscv64 machines, and 'sifive_u' and
> 'virt' 32 bit machines are able to run the defaul
Various syscalls miss swapping the endiannes of the [res]uid/gid
values. Use the tswapid() helper meant to do exactly that.
Fixes: b03c60f351 ("more syscalls")
Resolves: https://gitlab.com/qemu-project/qemu/-/issues/1394
Signed-off-by: Philippe Mathieu-Daudé
---
linux-user/syscall.c | 55 +++
There are two test cases where the inline asm doesn't
have the correct constraints causing them to fail when
using certain clang versions/optimization levels.
In mem_noshuf.c, the register r7 is written to but
not specified in the clobber list.
In misc.c, the 'result' output needs the early clobb
On 28/12/22 14:33, Daniel Henrique Barboza wrote:
'filename', 'mem_size' and 'fdt' from riscv_load_initrd() can all be
retrieved by the MachineState object for all callers.
Cc: Palmer Dabbelt
Signed-off-by: Daniel Henrique Barboza
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Bin Meng
---
On 28/12/22 14:33, Daniel Henrique Barboza wrote:
The microchip_icicle_kit, sifive_u, spike and virt boards are now doing
the same steps when '-kernel' is used:
- execute load_kernel()
- load init_rd()
- write kernel_cmdline in the fdt
Let's fold everything inside riscv_load_kernel() to avoid c
Hi Jason,
On 28/12/22 15:38, Jason A. Donenfeld wrote:
The setup_data links are appended to the compressed kernel image. Since
the kernel image is typically loaded at 0x10, setup_data lives at
`0x10 + compressed_size`, which does not get relocated during the
kernel's boot process.
The k
Hello everyone, this is a proposal in the libtcg direction, i.e.,
enabling building a single QEMU executable featuring multiple *targets*
(i.e., TCG frontends).
This follows what we discussed in recent KVM calls and originally at
the KVM Forum Emulation BoF.
Note that our commitment to this projec
Is there any chance between 7.1 and 7.2 ‘something’ happened to make it so that
Qemu ‘cares more’ about e.g. when memory regions are added/removed?
I seem to get an abort because a memory region has not been completely setup in
7.2 (while it is being flattened actually) - In 7.1 that never seeme
On Wed, Dec 28, 2022 at 05:02:22PM +0100, Philippe Mathieu-Daudé wrote:
> Hi Jason,
>
> On 28/12/22 15:38, Jason A. Donenfeld wrote:
> > The setup_data links are appended to the compressed kernel image. Since
> > the kernel image is typically loaded at 0x10, setup_data lives at
> > `0x10 +
Hi, it's a good idea to update the skeleton generation. Technically
skeleton generation is not a part of Qemu building. The skeleton is
already presented in the Qemu tree, so we skip dependencies from
clang/bpftool.
It's a good idea to have an updated bpf program and simplified
Makefile with Qemu s
HELLO H. PETER ANVIN,
E
L
L
O
On Wed, Dec 28, 2022 at 05:30:30PM +0100, Jason A. Donenfeld wrote:
> > Fix looks good, glad you figured out the problem.
>
> I mean, kind of. The solution here sucks, especially given that in the
> worst case, setup_data just gets dropped. I'm half inclined to consi
On 12/27/22 18:34, gaosong wrote:
The manual says "The lower 64 bits of each vector register overlap with the floating point
register of the same number. In other words
When the basic floating-point instruction is executed to update the floating-point
register, the low 64 bits of the correspond
On 12/27/22 23:24, Philippe Mathieu-Daudé wrote:
On 24/12/22 16:18, Richard Henderson wrote:
As in page_get_flags, we need to try again with the mmap
lock held if we fail a page lookup.
Signed-off-by: Richard Henderson
---
accel/tcg/user-exec.c | 39 ---
> -Original Message-
> From: Mukilan Thiyagarajan (QUIC)
> Sent: Wednesday, December 28, 2022 9:37 AM
> To: qemu-devel@nongnu.org; Taylor Simpson
> Cc: Brian Cain ; Matheus Bernardino (QUIC)
> ; Mukilan Thiyagarajan (QUIC)
>
> Subject: [PATCH] tests/tcg/hexagon: fix underspecifed asm
> -Original Message-
> From: Mukilan Thiyagarajan (QUIC)
> Sent: Tuesday, December 27, 2022 9:35 AM
> To: qemu-devel@nongnu.org; Taylor Simpson ;
> laur...@vivier.eu
> Cc: Brian Cain ; richard.hender...@linaro.org;
> alex.ben...@linaro.org; Mukilan Thiyagarajan (QUIC)
>
> Subject: [PAT
> -Original Message-
> From: Mukilan Thiyagarajan (QUIC)
> Sent: Tuesday, December 27, 2022 9:35 AM
> To: qemu-devel@nongnu.org; Taylor Simpson ;
> laur...@vivier.eu
> Cc: Brian Cain ; richard.hender...@linaro.org;
> alex.ben...@linaro.org; Mukilan Thiyagarajan (QUIC)
>
> Subject: [PAT
On 28/12/22 18:36, Richard Henderson wrote:
On 12/27/22 23:24, Philippe Mathieu-Daudé wrote:
On 24/12/22 16:18, Richard Henderson wrote:
As in page_get_flags, we need to try again with the mmap
lock held if we fail a page lookup.
Signed-off-by: Richard Henderson
---
accel/tcg/user-exec.c |
On 12/28/22 10:27, Philippe Mathieu-Daudé wrote:
Oh, so you are using this variable as tri-state?
Yes. Perhaps a comment on the -1?
r~
On 28/12/22 17:26, Mark Burton wrote:
Is there any chance between 7.1 and 7.2 ‘something’ happened to make it
so that Qemu ‘cares more’ about e.g. when memory regions are added/removed?
I seem to get an abort because a memory region has not been completely
setup in 7.2 (while it is being flatt
On 28/12/22 19:30, Richard Henderson wrote:
On 12/28/22 10:27, Philippe Mathieu-Daudé wrote:
Oh, so you are using this variable as tri-state?
Yes. Perhaps a comment on the -1?
Or name the variable tristate_lock? And a comment :)
(No need to respin, you can keep my R-b).
On 12/28/22 12:51, Philippe Mathieu-Daudé wrote:
On 28/12/22 14:33, Daniel Henrique Barboza wrote:
'filename', 'mem_size' and 'fdt' from riscv_load_initrd() can all be
retrieved by the MachineState object for all callers.
Cc: Palmer Dabbelt
Signed-off-by: Daniel Henrique Barboza
Reviewed-b
On 19/12/2022 12.21, Marcel Apfelbaum wrote:
On Mon, Dec 19, 2022 at 10:57 AM Yuval Shaia wrote:
Can anyone else pick this one?
Adding Thomas,
I dropped the ball with this one, I am sorry about that, maybe it
doesn't worth a Pull Request only for it.
Why not? Pull request for single patch
From: Michael Kropaczek
Description:
Currently namespaces could be configured as follows:
1. Legacy Namespace - just one namespace within Nvme controller's
where the back-end was specified for nvme device by -drive parameter
pointing directly to the image file.
2. Additional Namespaces - s
From: Michael Kropaczek
Added support for NVMEe NameSpaces Mangement allowing the guest OS to
delete namespaces by issuing nvme delete-ns command.
It is an extension to currently implemented Qemu nvme virtual device.
Virtual devices representing namespaces will be created and/or deleted
during Qe
From: Michael Kropaczek
Added support for NVMEe NameSpaces Mangement allowing the guest OS to
create namespaces by issuing nvme create-ns command.
It is an extension to currently implemented Qemu nvme virtual device.
Virtual devices representing namespaces will be created and/or deleted
during Qe
On Wed, Dec 28, 2022 at 01:41:40PM -0600, Jonathan Derrick wrote:
> +static uint16_t nvme_ns_mgmt(NvmeCtrl *n, NvmeRequest *req)
> +{
> +NvmeCtrl *n_p = NULL; /* primary controller */
> +NvmeIdCtrl *id = &n->id_ctrl;
> +NvmeNamespace *ns;
> +NvmeIdNsMgmt id_ns = {};
> +uint8
On 12/28/22 12:18, Bin Meng wrote:
On Wed, Dec 28, 2022 at 9:38 PM Daniel Henrique Barboza
wrote:
This test is used to do a quick sanity check to ensure that we're able
to run the existing QEMU FW image.
'sifive_u', 'spike' and 'virt' riscv64 machines, and 'sifive_u' and
'virt' 32 bit machi
On 28/12/22 16:35, Philippe Mathieu-Daudé wrote:
Various syscalls miss swapping the endiannes of the [res]uid/gid
values. Use the tswapid() helper meant to do exactly that.
Fixes: b03c60f351 ("more syscalls")
Resolves: https://gitlab.com/qemu-project/qemu/-/issues/1394
This is not the correct
On Mon, Dec 26, 2022 at 11:03 PM Strahinja Jankovic <
strahinjapjanko...@gmail.com> wrote:
> This patch implements Allwinner TWI/I2C controller emulation. Only
> master-mode functionality is implemented.
>
> The SPL boot for Cubieboard expects AXP209 PMIC on TWI0/I2C0 bus, so this
> is
> first par
On Mon, Dec 26, 2022 at 11:03 PM Strahinja Jankovic <
strahinjapjanko...@gmail.com> wrote:
> Cubieboard now can boot directly from SD card, without the need to pass
> `-kernel` parameter. Update Avocado tests to cover this functionality.
>
> Signed-off-by: Strahinja Jankovic
>
Test looks fine to
On 12/13/22 22:26, Helge Deller wrote:
The sparc and hppa architectures provide an own output for the emulated
/proc/cpuinfo file.
Some userspace applications count (even if that's not the recommended
way) the number of lines which start with "processor:" and assume that
this number then reflect
The sparc and hppa architectures provide an own output for the emulated
/proc/cpuinfo file.
Some userspace applications count (even if that's not the recommended
way) the number of lines which start with "processor:" and assume that
this number then reflects the number of online CPUs. Since those
Add overrides for
J2_callr
J2_callrt
J2_callrf
Signed-off-by: Taylor Simpson
---
target/hexagon/gen_tcg.h | 6 ++
target/hexagon/macros.h | 10 --
target/hexagon/genptr.c | 20
3 files changed, 26 insertions(+), 10 deletions(-)
diff --git a/target
These instructions perform a deallocframe+return (jumpr r31)
Add overrides for
L4_return
SL2_return
L4_return_t
L4_return_f
L4_return_tnew_pt
L4_return_fnew_pt
L4_return_tnew_pnt
L4_return_fnew_pnt
SL2_return_t
SL2_return_f
SL2_return_tnew
SL2_return
The idef-parser skips the change-of-flow (COF) instructions, so add
overrides
Changes in v2
Add a new generator for analyze_ instructions. Pouplate the
DisasContext ahead of generating code.
Taylor Simpson (6):
Hexagon (target/hexagon) Add overrides for jumpr31 instructions
Hexagon
Analyze HVX vector and predicate registers
Signed-off-by: Taylor Simpson
---
target/hexagon/translate.h | 14 --
target/hexagon/translate.c | 28
target/hexagon/gen_analyze_funcs.py | 17 ++---
target/hexagon/gen_tcg_funcs.py
Signed-off-by: Taylor Simpson
---
target/hexagon/gen_tcg.h | 4 ++
target/hexagon/genptr.c | 79
2 files changed, 83 insertions(+)
diff --git a/target/hexagon/gen_tcg.h b/target/hexagon/gen_tcg.h
index 231654e6c1..1ac23b75a0 100644
--- a/target/hexagon/
We create a new generator that creates an analyze_ function for
each instruction. Currently, these functions record the writes to
R, P, and C registers by calling ctx_log_reg_write[_pair] or
ctx_log_pred_write.
During gen_start_packet, we invoke the analyze_ function for
each instruction in the p
Add overrides for
SL2_jumpr31Unconditional
SL2_jumpr31_t Predicated true (old value)
SL2_jumpr31_f Predicated false (old value)
SL2_jumpr31_tnew Predicated true (new value)
SL2_jumpr31_fnew Predicated false (new value)
Signed-off-by: Ta
Hi Keith,
Thank you for the review and I agree with you, the issues will be addressed.
Regards,
Michael
-Original Message-
From: Keith Busch
Sent: Wednesday, December 28, 2022 12:10 PM
To: Jonathan Derrick
Cc: qemu-devel@nongnu.org; Michael Kropaczek (CW)
; qemu-bl...@nongnu.org; K
On December 28, 2022 8:57:54 AM PST, "Jason A. Donenfeld"
wrote:
>HELLO H. PETER ANVIN,
>E
>L
>L
>O
>
>On Wed, Dec 28, 2022 at 05:30:30PM +0100, Jason A. Donenfeld wrote:
>> > Fix looks good, glad you figured out the problem.
>>
>> I mean, kind of. The solution here sucks, especially given that
在 2022/12/29 上午1:30, Richard Henderson 写道:
On 12/27/22 18:34, gaosong wrote:
The manual says "The lower 64 bits of each vector register overlap
with the floating point register of the same number. In other words
When the basic floating-point instruction is executed to update the
floating-poi
On 12/28/22 15:58, H. Peter Anvin wrote:
On December 28, 2022 8:57:54 AM PST, "Jason A. Donenfeld"
wrote:
HELLO H. PETER ANVIN,
E
L
L
O
On Wed, Dec 28, 2022 at 05:30:30PM +0100, Jason A. Donenfeld wrote:
Fix looks good, glad you figured out the problem.
I mean, kind of. The solution here s
1 - 100 of 119 matches
Mail list logo
