** Changed in: qemu
Assignee: (unassigned) => Laurent Vivier (laurent-vivier)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1881450
Title:
Emulation of a math function fails for m68k Linux
On 5/14/20 7:53 AM, John Snow wrote:
> In truth, if you don't do this, you'll just get a TypeError
> exception. Now, you'll get an AssertionError.
>
> Is this tangibly better? No.
> Does mypy complain less? Yes.
>
> Signed-off-by: John Snow
> ---
> python/qemu/lib/qmp.py | 1 +
> 1 file
On 5/14/20 7:53 AM, John Snow wrote:
> The type system doesn't want integers.
>
> Signed-off-by: John Snow
> ---
> python/qemu/lib/qmp.py | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/python/qemu/lib/qmp.py b/python/qemu/lib/qmp.py
> index b91c9d5c1c..a634c4e26c
On 5/14/20 7:53 AM, John Snow wrote:
> Python 3.5 and above do not print a warning when logging is not
> configured. As a library, it's best practice to leave logging
> configuration to the client executable.
>
> Signed-off-by: John Snow
> ---
> python/qemu/lib/machine.py | 3 ---
> 1 file
On 5/29/20 10:34 PM, Robert Foley wrote:
> 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:
The immediate value mode was ignored and instruction execution
ends to an invalid access mode.
This was found running 'R' that set FPSR to 0 at startup with
a 'fmove.l #0,FPSR' in qemu-system-m68k emulation and triggers a
kernel crash:
[ 56.64] *** ADDRESS ERROR *** FORMAT=2
[
On 5/29/20 10:34 PM, Robert Foley wrote:
> 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(-)
>
>
Hi Laurent!
On 5/31/20 1:02 PM, Laurent Vivier wrote:
> The immediate value mode was ignored and instruction execution
> ends to an invalid access mode.
>
> This was found running 'R' that set FPSR to 0 at startup with
> a 'fmove.l #0,FPSR' in qemu-system-m68k emulation and triggers a
> kernel
On 5/28/20 1:24 PM, Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert"
>
> When the source finishes migration the destination will still be
> receiving the data sent by the source, so it might not have quite
> finished yet, so won't quite have reached 'completed'.
> This lead
Le 31/05/2020 à 13:23, John Paul Adrian Glaubitz a écrit :
> Hi Laurent!
>
> On 5/31/20 1:02 PM, Laurent Vivier wrote:
>> The immediate value mode was ignored and instruction execution
>> ends to an invalid access mode.
>>
>> This was found running 'R' that set FPSR to 0 at startup with
>> a
Tracing gives me:
IN: expm1f
0x85cc: fetoxm1x %fp2,%fp0
Disassembler disagrees with translator over instruction decoding
Please report this to qemu-devel@nongnu.org
(gdb) x/2hx 0x85cc
0x85cc: 0xf200 0x0808
The instruction is not implemented in qemu. I fix that.
--
You
Fix available.
Execution doesn't fail anymore:
Profiling function expm1f():
Elapsed time: 41 ms
Control result: 71805.108342
Control result matches real hardware one:
Profiling function expm1f():
Elapsed time: 2152 ms
Control result: 71805.108342
** Changed in: qemu
On 5/14/20 7:53 AM, John Snow wrote:
> mypy considers it incorrect to use `bool` to statically return false,
> because it will assume that it could conceivably return True, and gives
> different analysis in that case. Use a None return to achieve the same
> effect, but make mypy happy.
>
> Note:
On 5/14/20 7:54 AM, John Snow wrote:
> It can be None; so add assertions or exceptions where appropriate to
> guard the access accordingly.
>
> Signed-off-by: John Snow
> ---
> python/qemu/lib/qtest.py | 14 +++---
> 1 file changed, 11 insertions(+), 3 deletions(-)
>
> diff --git
Philippe Mathieu-Daudé writes:
> From: Thomas Huth
>
> Now that we can select the second serial console in the acceptance tests
> (see commit 746f244d9720 "Allow to use other serial consoles than default"),
> we can also test the sh4 image from the QEMU advent calendar 2018.
>
>
Hi Robert,
On 5/29/20 10:34 PM, Robert Foley wrote:
> 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
Philippe Mathieu-Daudé writes:
> Hi Robert,
>
> On 5/29/20 10:34 PM, Robert Foley wrote:
>> diff --git a/configure b/configure
>> index d82de47fdd..8a286e75a5 100755
>> --- a/configure
>> +++ b/configure
>> @@ -411,6 +411,7 @@ prefix="/usr/local"
>> mandir="\${prefix}/share/man"
>>
On 5/29/20 10:34 PM, Robert Foley wrote:
> 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:
>
** Patch added: "0001-target-m68k-implement-opcode-fetoxm1x.patch"
https://bugs.launchpad.net/qemu/+bug/1881450/+attachment/5379012/+files/0001-target-m68k-implement-opcode-fetoxm1x.patch
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to
Example provided in the launchpad bug fails with:
qemu: uncaught target signal 4 (Illegal instruction) - core dumped
Illegal instruction (core dumped)
It appears fetoxm1 is not implemented:
IN: expm1f
0x85cc: fetoxm1x %fp2,%fp0
Disassembler disagrees with translator over
Hi,
After discussion on v1 of this series, the conclusion was that page
crossings must be done for all targets and for both user and system
mode. This series deals with rx target, that is the only target that
does not perform this check in system mode.
In version two of this series, the original
Add the page crossings check in use_goto_tb(). If this check is not
applied, a number of bugs may occasionally occur during target rx
system mode emulation.
Also, this check is needed in user mode related to emulation of system
call mmap(). rx target does not currently support user mode, but it is
On 5/14/20 7:53 AM, John Snow wrote:
> Use the Python3 style instead.
>
> Signed-off-by: John Snow
> ---
> python/qemu/lib/machine.py | 2 +-
> python/qemu/lib/qtest.py | 15 +++
> 2 files changed, 8 insertions(+), 9 deletions(-)
Thanks, applied to my python-next tree:
On 5/14/20 7:53 AM, John Snow wrote:
> Mostly, ignore the "no bare except" rule, because flake8 is not
> contextual and cannot determine if we re-raise. Pylint can, though, so
> always prefer pylint for that.
>
> Signed-off-by: John Snow
> ---
> python/qemu/lib/.flake8| 2 ++
>
On 5/29/20 10:34 PM, Robert Foley wrote:
> 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.
>
Hi Laurent!
On 5/31/20 2:09 PM, Laurent Vivier wrote:
> I guess you are using my q800-dev branch?
That's what I initially did, then I pulled from upstream.
> In this branch, there is an attempt to manage unnormalized numbers that
> seems to trigger this lock up.
>
> You can either use master +
On 5/14/20 7:53 AM, John Snow wrote:
> Note:
>
> A bug in typeshed (https://github.com/python/typeshed/issues/3977)
> misinterprets the type of makefile(). Work around this by explicitly
> stating that we are opening a text-mode file.
>
> Signed-off-by: John Snow
> ---
> python/qemu/lib/qmp.py
Philippe Mathieu-Daudé writes:
> Hi,
>
> As there is no SH4 active maintainer, I gathered various
> patches in a single series, in case someone is willing to
> apply them.
I'm sure you you could put yourself down as an "Odd Fixes" maintainer
and put together a PR if you want?
>
> CI report:
On 5/29/20 10:34 PM, Robert Foley wrote:
> 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
>
On 5/29/20 10:34 PM, Robert Foley wrote:
> 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
> ---
>
On 5/29/20 10:34 PM, Robert Foley wrote:
> 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
On 5/29/20 9:05 AM, Pavel Dovgalyuk wrote:
> This patch moves image downloading functions to the separate class to allow
> reusing them from record/replay tests.
>
> Signed-off-by: Pavel Dovgalyuk
> ---
> 0 files changed
>
> diff --git a/tests/acceptance/boot_linux.py
memory_region_set_size() handle the 16 Exabytes limit by
special-casing the UINT64_MAX value. This is not a problem
for the 32-bit maximum, 4 GiB.
By using the UINT32_MAX value, the bm-raven MemoryRegion
ends up missing 1 byte:
$ qemu-system-ppc -M prep -S -monitor stdio -usb
memory-region:
IEC binary prefixes ease code review: the unit is explicit.
Signed-off-by: Philippe Mathieu-Daudé
---
hw/pci/pci_bridge.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/hw/pci/pci_bridge.c b/hw/pci/pci_bridge.c
index 3ba3203f72..3789c17edc 100644
---
memory_region_set_size() handle the 16 Exabytes limit by
special-casing the UINT64_MAX value. This is not a problem
for the 32-bit maximum, 4 GiB.
By using the UINT32_MAX value, the aspeed-ram-container
MemoryRegion ends up missing 1 byte:
$ qemu-system-arm -M ast2600-evb -S -monitor stdio
In an effort to remove the cpu_physical_memory_rw() API,
update s390_cpu_virt_mem_rw() to use a more recent
address_space_rw() API.
Signed-off-by: Philippe Mathieu-Daudé
---
target/s390x/mmu_helper.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git
Do not restrict 64-bit CPU to 32-bit max access by default.
Signed-off-by: Philippe Mathieu-Daudé
---
RFC because this probably require an audit of all devices
used on 64-bit targets.
But if we find such problematic devices, they should instead
enforce their access_size_max = 4 rather than
The DMA device should not use the CPU address space
to do its operation, but its own address space.
Replace cpu_physical_memory_write() by dma_memory_read()
since we already have the DMA address space available.
Signed-off-by: Philippe Mathieu-Daudé
---
hw/dma/rc4030.c | 3 ++-
1 file changed,
These patches are extracted from a bigger series which
- remove generic ISA space, restricting it to the hw
that really has it (mostly PCI-ISA bridges)
- allow QTest/GDB to use any address space
- make I/O address space target-specific (only X86 and
AVR have a CPU connected to it)
- better
The DMA operations should not use the CPU address space, but
the DMA address space. Add support for a DMA address space,
and replace the cpu_physical_memory API calls by equivalent
dma_memory_read/write calls.
Signed-off-by: Philippe Mathieu-Daudé
---
include/hw/sd/allwinner-sdhost.h | 4
It is pointless to have 32-bit CPUs see a 64-bit address
space, when they can only address the 32 lower bits.
Only create CPU address space with a size it can address.
This makes HMP 'info mtree' command easier to understand
(on 32-bit CPUs).
Signed-off-by: Philippe Mathieu-Daudé
---
This is
Most CPUs can do 64-bit operations. Update the CPUReadMemoryFunc
and CPUWriteMemoryFunc prototypes.
Signed-off-by: Philippe Mathieu-Daudé
---
include/exec/cpu-common.h | 4 ++--
hw/usb/hcd-musb.c | 12 ++--
2 files changed, 8 insertions(+), 8 deletions(-)
diff --git
Patchew URL: https://patchew.org/QEMU/20200531175425.10329-1-f4...@amsat.org/
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 ===
Thanks Thomas for Your suggestion. Unfortunately I cannot achieve the
reconnection:
KVM runs with following parameters:
-usb -device usb-host,vendorid=0x04e8,productid=0x3242,id=drucker
-monitor unix:qemu-monitor-socket,server,nowait
With the Unix socket, I can now pipe commands to the qemu
Public bug reported:
This is quite odd, and I'm not sure about how to get around it. I'm writing an
OS in Rust and require APIC support. When I boot my kernel with
qemu-system-x86_64, however, it dumps out a [lot] of warnings; it claims that
TCG doesn't support FMA, X2APIC, AVX, F16C, AVX2,
On Sun, 31 May 2020 at 18:54, Philippe Mathieu-Daudé wrote:
>
> Do not restrict 64-bit CPU to 32-bit max access by default.
>
> Signed-off-by: Philippe Mathieu-Daudé
> ---
> RFC because this probably require an audit of all devices
> used on 64-bit targets.
> But if we find such problematic
On 5/31/20 7:54 PM, Philippe Mathieu-Daudé wrote:
> The DMA operations should not use the CPU address space, but
> the DMA address space. Add support for a DMA address space,
> and replace the cpu_physical_memory API calls by equivalent
> dma_memory_read/write calls.
>
> Signed-off-by: Philippe
On Sun, 31 May 2020 at 18:54, Philippe Mathieu-Daudé wrote:
>
> Most CPUs can do 64-bit operations. Update the CPUReadMemoryFunc
> and CPUWriteMemoryFunc prototypes.
>
> Signed-off-by: Philippe Mathieu-Daudé
> ---
> include/exec/cpu-common.h | 4 ++--
> hw/usb/hcd-musb.c | 12
On Thu, 28 May 2020 at 19:19, Eric Blake wrote:
>
> The following changes since commit a20ab81d22300cca80325c284f21eefee99aa740:
>
> Merge remote-tracking branch
> 'remotes/huth-gitlab/tags/pull-request-2020-05-28' into staging (2020-05-28
> 16:18:06 +0100)
>
> are available in the Git
On Sun, 31 May 2020 at 18:38, Philippe Mathieu-Daudé wrote:
>
> memory_region_set_size() handle the 16 Exabytes limit by
> special-casing the UINT64_MAX value.
> This is not a problem for the 32-bit maximum, 4 GiB, but
> in some places we incorrectly use UINT32_MAX instead of
> 4 GiB, and end up
Hi,
I'm Yash. I'm a 3rd year college undergraduate student, currently interning
in IIT Madras in Project Shakti. We have built RISC-V boards and I have
been assigned the task to add these boards as machines to QEMU.
I am absolutely new to this and have no idea how to go about this. Please
help me
memory_region_set_size() handle the 16 Exabytes limit by
special-casing the UINT64_MAX value. This is not a problem
for the 32-bit maximum, 4 GiB.
By using the UINT32_MAX value, the pci_bridge_io MemoryRegion
ends up missing 1 byte:
(qemu) info mtree
memory-region: pci_bridge_io
IEC binary prefixes ease code review: the unit is explicit.
Signed-off-by: Philippe Mathieu-Daudé
---
hw/hppa/dino.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/hw/hppa/dino.c b/hw/hppa/dino.c
index 2b1b38c58a..7290f23962 100644
--- a/hw/hppa/dino.c
+++
IEC binary prefixes ease code review: the unit is explicit.
Signed-off-by: Philippe Mathieu-Daudé
---
hw/pci-host/i440fx.c| 3 ++-
hw/pci-host/q35.c | 2 +-
hw/pci-host/versatile.c | 5 +++--
3 files changed, 6 insertions(+), 4 deletions(-)
diff --git a/hw/pci-host/i440fx.c
memory_region_set_size() handle the 16 Exabytes limit by
special-casing the UINT64_MAX value.
This is not a problem for the 32-bit maximum, 4 GiB, but
in some places we incorrectly use UINT32_MAX instead of
4 GiB, and end up missing 1 byte in the memory region.
This series fixes the cases I
IEC binary prefixes ease code review: the unit is explicit.
Signed-off-by: Philippe Mathieu-Daudé
---
hw/i386/xen/xen-hvm.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/hw/i386/xen/xen-hvm.c b/hw/i386/xen/xen-hvm.c
index 82ece6b9e7..679d74e6a3 100644
---
IEC binary prefixes ease code review: the unit is explicit.
Signed-off-by: Philippe Mathieu-Daudé
---
target/i386/cpu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/i386/cpu.c b/target/i386/cpu.c
index 3733d9a279..33ce4861fb 100644
--- a/target/i386/cpu.c
+++
On Sun, 31 May 2020 at 18:54, Philippe Mathieu-Daudé wrote:
>
> It is pointless to have 32-bit CPUs see a 64-bit address
> space, when they can only address the 32 lower bits.
>
> Only create CPU address space with a size it can address.
> This makes HMP 'info mtree' command easier to understand
On Sat, 30 May 2020 at 08:53, Thomas Huth wrote:
>
> Hi Peter,
>
> the following changes since commit c86274bc2e34295764fb44c2aef3cf29623f9b4b:
>
> Merge remote-tracking branch
> 'remotes/stsquad/tags/pull-testing-tcg-plugins-270520-1' into staging
> (2020-05-29 17:41:45 +0100)
>
> are
This module supported SCI / SCIa / SCIF.
Hardware manual.
SCI / SCIF
https://www.renesas.com/us/en/doc/products/mpumcu/001/r01uh0457ej0401_sh7751.pdf
SCIa
https://www.renesas.com/us/en/doc/products/mpumcu/doc/rx_family/r01uh0033ej0140_rx62n.pdf
Signed-off-by: Yoshinori Sato
---
SH4 SCI module convert to renesas_sci.c.
This file is obsolute.
Signed-off-by: Yoshinori Sato
---
hw/char/sh_serial.c | 431
1 file changed, 431 deletions(-)
delete mode 100644 hw/char/sh_serial.c
diff --git a/hw/char/sh_serial.c
Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by: John Snow
Reviewed-by: Kevin Wolf
Message-Id: <20200512103238.7078-6-phi...@redhat.com>
---
scripts/modules/module_block.py | 29 +++--
1 file changed, 15 insertions(+), 14 deletions(-)
diff --git
From: John Snow
Use the Python3 style instead.
Signed-off-by: John Snow
Reviewed-by: Philippe Mathieu-Daudé
Message-Id: <20200514055403.18902-12-js...@redhat.com>
Signed-off-by: Philippe Mathieu-Daudé
---
python/qemu/machine.py | 2 +-
python/qemu/qtest.py | 15 +++
2 files
From: John Snow
Bring our these files up to speed with pylint 2.5.0.
Add a pylintrc file to formalize which pylint subset
we are targeting.
The similarity ignore is there to suppress similarity
reports across imports, which for typing constants,
are going to trigger this report erroneously.
From: Philippe Mathieu-Daudé
Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by: John Snow
Reviewed-by: Kevin Wolf
Message-Id: <20200512103238.7078-3-phi...@redhat.com>
Signed-off-by: Philippe Mathieu-Daudé
---
scripts/qemu-gdb.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Signed-off-by: Philippe Mathieu-Daudé
Acked-by: Paolo Bonzini
Reviewed-by: John Snow
Reviewed-by: Kevin Wolf
Message-Id: <20200512103238.7078-5-phi...@redhat.com>
---
scripts/kvm/vmxcap | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/scripts/kvm/vmxcap
From: John Snow
mypy considers it incorrect to use `bool` to statically return false,
because it will assume that it could conceivably return True, and gives
different analysis in that case. Use a None return to achieve the same
effect, but make mypy happy.
Note: Pylint considers function
From: John Snow
Note:
A bug in typeshed (https://github.com/python/typeshed/issues/3977)
misinterprets the type of makefile(). Work around this by explicitly
stating that we are opening a text-mode file.
Signed-off-by: John Snow
Reviewed-by: Philippe Mathieu-Daudé
Message-Id:
From: John Snow
In truth, if you don't do this, you'll just get a TypeError
exception. Now, you'll get an AssertionError.
Is this tangibly better? No.
Does mypy complain less? Yes.
Signed-off-by: John Snow
Reviewed-by: Philippe Mathieu-Daudé
Message-Id:
From: John Snow
There's more wrong with these scripts; They are in various stages of
disrepair. That's beyond the scope of this current patchset.
This just mechanically corrects the imports and the shebangs, as part of
ensuring that the python/qemu/lib refactoring didn't break anything
From: John Snow
It can be None; so add assertions or exceptions where appropriate to
guard the access accordingly.
Signed-off-by: John Snow
Reviewed-by: Philippe Mathieu-Daudé
Message-Id: <20200514055403.18902-30-js...@redhat.com>
Signed-off-by: Philippe Mathieu-Daudé
---
From: "Dr. David Alan Gilbert"
When the source finishes migration the destination will still be
receiving the data sent by the source, so it might not have quite
finished yet, so won't quite have reached 'completed'.
This lead to occasional asserts in the next few checks.
After the source has
On 31/05/2020, Philippe Mathieu-Daudé wrote:
On 3/30/20 6:41 PM, Peter Maydell wrote:
On Mon, 30 Mar 2020 at 17:21, Philippe Mathieu-Daudé wrote:
On 3/30/20 6:08 PM, Peter Maydell wrote:
On Mon, 30 Mar 2020 at 16:30, Philippe Mathieu-Daudé wrote:
Since commit 3f940dc98, we added support
From: Pavel Dovgalyuk
This patch moves image downloading functions to the separate class to allow
reusing them from record/replay tests.
Signed-off-by: Pavel Dovgalyuk
Tested-by: Philippe Mathieu-Daudé
Message-Id: <159073593167.20809.17582679291556188984.stgit@pasha-ThinkPad-X280>
On Sun, 31 May 2020 at 17:42, Jon Doron wrote:
>
> On 31/05/2020, Philippe Mathieu-Daudé wrote:
> >On 3/30/20 6:41 PM, Peter Maydell wrote:
> >> PS: do we have any documentation of this new command ?
> >> ab4752ec8d9 has the implementation but no documentation...
> >
> >Jon, do you have
On 5/29/20 9:04 AM, Pavel Dovgalyuk wrote:
> The following series adds record/replay tests to the acceptance group.
> Test pass successfully with the latest submitted record/replay fixes:
> - replay: notify the main loop when there are no instructions
> - replay: synchronize on every virtual
8bit or 16bit timer.
This implementation support only internal clock mode.
Hardware manual.
https://www.renesas.com/us/en/doc/products/mpumcu/doc/rx_family/r01uh0033ej0140_rx62n.pdf
Signed-off-by: Yoshinori Sato
---
include/hw/timer/renesas_8timer.h | 61
hw/timer/renesas_8timer.c
TMU - SH4 Timer module.
CMT - Compare and match timer used by some Renesas MCUs.
The two modules have similar interfaces and have been merged.
Signed-off-by: Yoshinori Sato
---
include/hw/timer/renesas_timer.h | 59 +
hw/timer/renesas_timer.c | 421 +++
rx62n - RX62N MCU.
rx-virt - RX QEMU virtual target.
This has the same specifications as the gdb simulator.
Signed-off-by: Yoshinori Sato
---
include/hw/rx/rx.h| 7 ++
include/hw/rx/rx62n.h | 91
hw/rx/rx-virt.c | 143 +
hw/rx/rx62n.c
From: John Snow
The type system doesn't want integers.
Signed-off-by: John Snow
Reviewed-by: Philippe Mathieu-Daudé
Message-Id: <20200514055403.18902-15-js...@redhat.com>
Signed-off-by: Philippe Mathieu-Daudé
---
python/qemu/qmp.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
From: Robert Foley
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
Reviewed-by: Philippe Mathieu-Daudé
Tested-by: Philippe Mathieu-Daudé
Message-Id:
From: Pavel Dovgalyuk
This patch splits code in BootLinuxConsole class into two different
classes to allow reusing it by record/replay tests.
Signed-off-by: Pavel Dovgalyuk
Reviewed-by: Alex Bennée
Tested-by: Philippe Mathieu-Daudé
Message-Id:
Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by: John Snow
Reviewed-by: Kevin Wolf
Message-Id: <20200512103238.7078-7-phi...@redhat.com>
---
tests/migration/guestperf-batch.py | 2 +-
tests/migration/guestperf-plot.py | 2 +-
tests/migration/guestperf.py | 2 +-
3 files changed, 3
From: John Snow
Mostly, ignore the "no bare except" rule, because flake8 is not
contextual and cannot determine if we re-raise. Pylint can, though, so
always prefer pylint for that.
Signed-off-by: John Snow
Reviewed-by: Philippe Mathieu-Daudé
Message-Id:
On 3/30/20 6:41 PM, Peter Maydell wrote:
> On Mon, 30 Mar 2020 at 17:21, Philippe Mathieu-Daudé
> wrote:
>> On 3/30/20 6:08 PM, Peter Maydell wrote:
>>> On Mon, 30 Mar 2020 at 16:30, Philippe Mathieu-Daudé
>>> wrote:
Since commit 3f940dc98, we added support for vAttach packet
to
This implementation supported only ICUa.
Hardware manual.
https://www.renesas.com/us/en/doc/products/mpumcu/doc/rx_family/r01uh0033ej0140_rx62n.pdf
Signed-off-by: Yoshinori Sato
---
include/hw/intc/rx_icu.h | 56 ++
hw/intc/rx_icu.c | 379 +++
Hello.
This series add to hardware emulation module for RX target.
Details below.
Interrupt controller, 8bit timer, 16bit comapare match timer and
SCI is RX62N integrated peripheral.
rx-virt - RX62N MCU and external RAM. It like gdb simulator.
The compare match timer has a CPU interface similar
Using unified TMU/CMT module.
Signed-off-by: Yoshinori Sato
---
include/hw/sh4/sh.h| 10 -
hw/sh4/sh7750.c| 47 +-
hw/sh4/Kconfig | 2 +-
hw/timer/Makefile.objs | 1 -
4 files changed, 38 insertions(+), 22 deletions(-)
diff
SH4 TMU using new module. This file is obsolute.
Signed-off-by: Yoshinori Sato
---
hw/timer/sh_timer.c | 341
1 file changed, 341 deletions(-)
delete mode 100644 hw/timer/sh_timer.c
diff --git a/hw/timer/sh_timer.c b/hw/timer/sh_timer.c
deleted
Using new implementation SCI module.
Signed-off-by: Yoshinori Sato
---
include/hw/sh4/sh.h | 11 ---
hw/sh4/sh7750.c | 45 +
hw/sh4/Kconfig | 1 +
3 files changed, 42 insertions(+), 15 deletions(-)
diff --git a/include/hw/sh4/sh.h
Tested-by: Philippe Mathieu-Daudé
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: Yoshinori Sato
Message-Id: <20190607091116.49044-17-ys...@users.sourceforge.jp>
Signed-off-by: Richard Henderson
pick ed65c02993 target/rx: Add RX to SysEmuTarget
pick 01372568ae tests: Add rx to
From: John Snow
We guarantee 3.5+ everywhere; remove more dead checks. In general, try
to avoid using version checks and instead prefer to attempt behavior
when possible.
Signed-off-by: John Snow
Reviewed-by: Philippe Mathieu-Daudé
Message-Id: <20200514035230.25756-1-js...@redhat.com>
From: Philippe Mathieu-Daudé
Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by: John Snow
Reviewed-by: Kevin Wolf
Message-Id: <20200512103238.7078-4-phi...@redhat.com>
Signed-off-by: Philippe Mathieu-Daudé
---
scripts/qmp/qom-get | 2 +-
scripts/qmp/qom-list | 2 +-
scripts/qmp/qom-set |
From: John Snow
Python 3.5 and above do not print a warning when logging is not
configured. As a library, it's best practice to leave logging
configuration to the client executable.
Signed-off-by: John Snow
Reviewed-by: Philippe Mathieu-Daudé
Message-Id:
From: Philippe Mathieu-Daudé
These scripts are loaded as plugin by GDB (and they don't
have any __main__ entry point). Remove the shebang header.
Signed-off-by: Philippe Mathieu-Daudé
Acked-by: Alex Bennée
Reviewed-by: John Snow
Reviewed-by: Kevin Wolf
Message-Id:
/python-next-20200531
for you to fetch changes up to 1c80c87c8c2489e4318c93c844aa29bc1d014146:
tests/acceptance: refactor boot_linux to allow code reuse (2020-05-31 18:25=
:31 +0200)
Python queue:
* migration acceptance test fix
From: Robert Foley
This helps debug issues that occur during the boot sequence.
Signed-off-by: Robert Foley
Reviewed-by: Peter Puhov
Reviewed-by: Alex Bennée
Reviewed-by: Philippe Mathieu-Daudé
Tested-by: Philippe Mathieu-Daudé
Message-Id: <20200529203458.1038-5-robert.fo...@linaro.org>
From: Vladimir Sementsov-Ogievskiy
Add method to hard-kill vm, without any quit commands.
Signed-off-by: Vladimir Sementsov-Ogievskiy
Reviewed-by: Andrey Shinkevich
Message-Id: <20200217150246.29180-19-vsement...@virtuozzo.com>
Signed-off-by: Philippe Mathieu-Daudé
---
From: Robert Foley
This allows for waiting for completion of arbitrary commands.
Signed-off-by: Robert Foley
Reviewed-by: Peter Puhov
Reviewed-by: Alex Bennée
Reviewed-by: Philippe Mathieu-Daudé
Tested-by: Philippe Mathieu-Daudé
Message-Id: <20200529203458.1038-7-robert.fo...@linaro.org>
On 5/31/20 6:24 PM, Yoshinori Sato wrote:
> Hello.
>
> This series add to hardware emulation module for RX target.
>
> Details below.
> Interrupt controller, 8bit timer, 16bit comapare match timer and
> SCI is RX62N integrated peripheral.
> rx-virt - RX62N MCU and external RAM. It like gdb
1 - 100 of 114 matches
Mail list logo
