RISC-V specifies multiple sizes for addressable memory and Linux probes for
the machine's support at startup via the satp CSR register (done in
csr.c:validate_vm).
As per the specification, sv64 must support sv57, which in turn must
support sv48...etc. So we can restrict machine support by simply
On 2/2/2023 6:40 PM, Igor Mammedov wrote:
> On Fri, 6 Jan 2023 00:38:26 -0800
> Lei Wang wrote:
>
>> The new CPU model mostly inherits features from Icelake-Server, while
>> adding new features:
>> - AMX (Advance Matrix eXtensions)
>> - Bus Lock Debug Exception
>> and new instructions:
>> - A
Currently, the max satp mode is set with the only constraint that it must be
implemented in QEMU, i.e. set in valid_vm_1_10_[32|64].
But we actually need to add another level of constraint: what the hw is
actually capable of, because currently, a linux booting on a sifive-u54
boots in sv57 mode wh
The 'mmu-type' should reflect what the hardware is capable of so use the
new satp_mode field in RISCVCPUConfig to do that.
Signed-off-by: Alexandre Ghiti
Reviewed-by: Andrew Jones
Reviewed-by: Alistair Francis
Reviewed-by: Bin Meng
Reviewed-by: Frank Chang
---
hw/riscv/virt.c | 19 ++
Alexander Graf writes:
> Add an option for hostmem-file to start the memory object at an offset
> into the target file. This is useful if multiple memory objects reside
> inside the same target file, such as a device node.
>
> In particular, it's useful to map guest memory directly into /dev/mem
On 2/2/23 23:31, John Snow wrote:
Signed-off-by: John Snow
---
qemu-options.hx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/qemu-options.hx b/qemu-options.hx
index d59d19704bc..52d477547f5 100644
--- a/qemu-options.hx
+++ b/qemu-options.hx
@@ -1606,7 +1606,7 @@ SRST
Hi Peter,
On 2/2/23 18:57, Peter Maydell wrote:
On Fri, 23 Dec 2022 at 09:01, Alexander Graf wrote:
The finalize_gic_version() function tries to determine which GIC version
the current accelerator / host combination supports. During the initial
HVF porting efforts, I didn't realize that I als
在 2023/2/2 下午1:51, Richard Henderson 写道:
On 2/1/23 17:16, Song Gao wrote:
The Manual 2.2.7.2:
'The LL.{W/D} instruction retrieves a word/double-word data from
the specified address of the memory and writes it to the general
register rd after sign extension.'
Signed-off-by: Song
We need get more migration thread information to support
migration pin, especially thread name and its pid. Add an
qmp interface to query migration threads information.
v2 of:
https://lists.nongnu.org/archive/html/qemu-devel/2023-01/msg04618.html
diff to v2:
* remove the event that report thread
Introduce interface query-migrationthreads. The interface is used
to query information about migration threads and returns with
migration thread's name and its id.
Introduce threadinfo.c to manage threads with migration.
Signed-off-by: Jiang Jiacheng
---
migration/meson.build | 1 +
migration/
To support query migration thread infomation, save and delete
thread(live_migration and multifdsend) information at thread
creation and finish.
Signed-off-by: Jiang Jiacheng
---
migration/migration.c | 5 +
migration/multifd.c | 5 +
2 files changed, 10 insertions(+)
diff --git a/migr
On 02/02/2023 19.59, Alex Bennée wrote:
Alex Bennée writes:
A significant portion of our CI logs are just enumerating each
successfully built object file. The current widespread versions of
ninja don't have a quiet option so we use NINJA_STATUS to add a fixed
string to the ninja output which
301 - 312 of 312 matches
Mail list logo
