From: Zong Li
The real physical address should add the 12 bits page offset. It also
causes the PMP wrong checking due to the minimum granularity of PMP is
4 byte, but we always get the physical address which is 4KB alignment,
that means, we always use the start address of the page to check PMP
Once an interrupt has been claimed, but before it has been compelted we
shouldn't receive any more pending interrupts. This patche keeps track
of this to ensure that we don't see any more interrupts until it is
completed.
Signed-off-by: Alistair Francis
Message-Id:
After a claim or a priority change we need to update the pending
interrupts. This is based on the same patch for the SiFive PLIC:
55765822804f5a58594e "riscv: plic: Add a couple of mising
sifive_plic_update calls"
Signed-off-by: Alistair Francis
Cc: Jessica Clarke
Reviewed-by: Philippe
On 2020/8/21 20:39, Dr. David Alan Gilbert wrote:
> * Daniel P. Berrangé (berra...@redhat.com) wrote:
>> On Fri, Aug 21, 2020 at 08:22:06PM +0800, Zheng Chuan wrote:
>>>
>>>
>>> On 2020/8/21 1:55, Dr. David Alan Gilbert wrote:
* Daniel P. Berrangé (berra...@redhat.com) wrote:
> On
Hello,
On 8/19/20 6:43 PM, Thiago Jung Bauermann wrote:
> Instead of setting CPUState::halted to 1 in ppce500_cpu_reset_sec(), use
> the start-powered-off property which makes cpu_common_reset() initialize it
> to 1 in common code.
>
> Also change creation of CPU object from cpu_create() to
This patch follows what commit aa4d30f6618dc "riscv: plic: Honour source
priorities" does and ensures that the highest priority interrupt will be
serviced first.
Signed-off-by: Alistair Francis
Cc: Jessica Clarke
Reviewed-by: Philippe Mathieu-Daudé
Message-Id:
---
hw/intc/ibex_plic.c | 15
On Samstag, 22. August 2020 02:16:23 CEST Geoffrey McRae wrote:
> On 2020-08-22 03:47, Paolo Bonzini wrote:
> > On 21/08/20 19:34, Christian Schoenebeck wrote:
> >>> static void qjack_fini_out(HWVoiceOut *hw)
> >>> {
> >>>
> >>> QJackOut *jo = (QJackOut *)hw;
> >>>
It was missing the instance_size field.
Cc: Eduardo Habkost
Signed-off-by: Cédric Le Goater
---
hw/ppc/pnv_lpc.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/hw/ppc/pnv_lpc.c b/hw/ppc/pnv_lpc.c
index b5ffa48dac71..23f1e09492b1 100644
--- a/hw/ppc/pnv_lpc.c
+++
On 8/21/20 10:50 PM, Max Filippov wrote:
> Hi Peter,
>
> please pull the following batch of updates for target/xtensa.
>
> Changes v1->v2:
> - rebase on top of build system changes, resolve trivial conflicts
> in the last two patches that add new files.
>
> The following changes since commit
On Saturday, August 22, 2020, Laurent Vivier wrote:
> Le 22/08/2020 à 00:28, Carlo Marcelo Arenas Belón a écrit :
> > While technically compatible will (depending on the CPU) hopefully fail
> > later with a cryptic error:
> >
> > qemu: Unexpected FPU mode
> >
> > Provide an earlier hint of
On Wednesday, August 19, 2020, Ahmed Karaman
wrote:
> Host CPU : Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
> Host Memory : 15.49 GB
>
> Start Time (UTC) : 2020-08-19 21:00:01
> End Time (UTC) : 2020-08-19 21:32:15
> Execution Time : 0:32:14.021998
>
> Status : SUCCESS
>
On Saturday, August 22, 2020, Aleksandar Markovic <
aleksandar.qemu.de...@gmail.com> wrote:
>
>
> On Wednesday, August 19, 2020, Ahmed Karaman
> wrote:
>
>> Host CPU : Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
>> Host Memory : 15.49 GB
>>
>> Start Time (UTC) : 2020-08-19 21:00:01
>>
On 4/6/20 10:34 PM, BALATON Zoltan wrote:
> In some corner cases (that never happen during normal operation but a
> malicious guest could program wrong values) pixman functions were
> called with parameters that result in a crash. Fix this and add more
> checks to disallow such cases.
(Fair)
The S24/TCX datasheet is listed as "Unable to locate" on [1].
However the NetBSD revision 1.32 of the driver introduced
64-bit accesses to the stippler and blitter [2]. It is safe
to assume these memory regions are 64-bit accessible.
QEMU implementation is 32-bit, so fill the 'impl' fields.
[1]
Fix SuperI/O QOM issues reported here:
https://www.mail-archive.com/qemu-devel@nongnu.org/msg731954.html
Supersedes: <20200821173831.1262979-1-phi...@redhat.com>
Eduardo Habkost (1):
hw/isa/superio: Do not enforce class_size when inherited from parent
Philippe Mathieu-Daudé (1):
Instead of setting the instance size on each implementations,
set it on the abstract parent, so we are sure no implementation
will forget to set it.
Reported-by: Eduardo Habkost
Signed-off-by: Philippe Mathieu-Daudé
---
hw/isa/isa-superio.c | 2 +-
hw/isa/smc37c669-superio.c | 1 -
This happens because openbios accesses unassigned memory during the SBus
scan:
Probing SBus slot 0 offset 0
invalid accepts: (null) addr 2000 size: 1
Probing SBus slot 1 offset 0
invalid accepts: (null) addr 3000 size: 1
Probing SBus slot 2 offset 0
invalid accepts: (null) addr
The S24/TCX datasheet is listed as "Unable to locate" on [1].
However the NetBSD revision 1.32 of the driver introduced
64-bit accesses to the stippler and blitter [2]. It is safe
to assume these memory regions are 64-bit accessible.
QEMU implementation is 32-bit, so fill the 'impl' fields.
[1]
Hi Alistair,
On 8/22/20 7:33 AM, Alistair Francis wrote:
> Reported-by: Eduardo Habkost
> Signed-off-by: Alistair Francis
> ---
> hw/core/register.c | 14 +-
> 1 file changed, 9 insertions(+), 5 deletions(-)
>
> diff --git a/hw/core/register.c b/hw/core/register.c
> index
** Tags added: sparc testcase
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1892540
Title:
qemu can no longer boot NetBSD/sparc
Status in QEMU:
New
Bug description:
Booting NetBSD/sparc in
Thanks Mr. Aleksandar for your feedback!
On Sat, Aug 22, 2020, 1:09 PM Aleksandar Markovic <
aleksandar.qemu.de...@gmail.com> wrote:
> Hi, Ahmed.
>
> The report, and the topic in general, look quite interesting. However, I
> would suggest two improvements:
>
> - The title should reflect the
Hi, Ahmed.
The report, and the topic in general, look quite interesting. However, I
would suggest two improvements:
- The title should reflect the content in a clearer way. Let's say,
"Compilers and QEMU performance" would be IMHO better. The expression "two
builds" is just missing the central
On Sat, Aug 22, 2020 at 10:39:20AM +0200, Cédric Le Goater wrote:
> It was missing the instance_size field.
>
> Cc: Eduardo Habkost
> Signed-off-by: Cédric Le Goater
Applied to ppc-for-5.2, thanks.
> ---
> hw/ppc/pnv_lpc.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff
On Wed, 19 Aug 2020 at 07:38, Gerd Hoffmann wrote:
>
> The following changes since commit 672b2f2695891b6d818bddc3ce0df964c7627969:
>
> Open 5.2 development tree (2020-08-18 13:44:04 +0100)
>
> are available in the Git repository at:
>
> git://git.kraxel.org/qemu
+Marcel, Laine, Daniel
On 08/21/20 12:30, Igor Mammedov wrote:
> On Tue, 18 Aug 2020 23:52:23 +0200
> Julia Suvorova wrote:
>
>> PCIe native hot-plug has numerous problems with racing events and
>> unpredictable guest behaviour (Windows).
> Documenting these misterious problems I've asked for
On 8/22/20 10:59 AM, Cédric Le Goater wrote:
> Hello,
>
> On 8/19/20 6:43 PM, Thiago Jung Bauermann wrote:
>> Instead of setting CPUState::halted to 1 in ppce500_cpu_reset_sec(), use
>> the start-powered-off property which makes cpu_common_reset() initialize it
>> to 1 in common code.
>>
>> Also
Thanks Mr. Aleksandar,
"Reference" and "latest" already each has its own results directory.
I will try re-running the tests tonight from scratch as you've suggested to
see how things will go.
I will also add the "---" line at the beginning as you've suggested.
Best regards,
Ahmed
On Sat,
Most uses of qemu_hexdump() do not take an array of char
as input, forcing use of cast. Since we can use this
helper to dump any kind of buffer, use a pointer to void
argument instead.
Signed-off-by: Philippe Mathieu-Daudé
---
include/qemu-common.h| 2 +-
hw/dma/xlnx_dpdma.c | 2 +-
On 8/17/20 6:18 PM, Philippe Mathieu-Daudé wrote:
> This is a follow up on last year patch from Stephen Checkoway:
> "block/pflash_cfi02: Implement intereleaved flash devices"
> https://www.mail-archive.com/qemu-devel@nongnu.org/msg613077.html
>
> Instead of making the PFLASH device more complex,
On 8/17/20 6:18 PM, Philippe Mathieu-Daudé wrote:
> This is a follow up on last year patch from Stephen Checkoway:
> "block/pflash_cfi02: Implement intereleaved flash devices"
> https://www.mail-archive.com/qemu-devel@nongnu.org/msg613077.html
>
> Instead of making the PFLASH device more complex,
Le 22/08/2020 à 00:28, Carlo Marcelo Arenas Belón a écrit :
> While technically compatible will (depending on the CPU) hopefully fail
> later with a cryptic error:
>
> qemu: Unexpected FPU mode
>
> Provide an earlier hint of what the problem might be by detecting if the
> binary might not be
On Friday, August 7, 2020, Huacai Chen wrote:
> Add Loongson-3 based machine support, it use liointc as the interrupt
> controler and use GPEX as the pci controller. Currently it can only work
> with KVM, but we will add TCG support in future.
>
>
Huacai,
We changed our build system yesterday,
Public bug reported:
Previously, with QEMU 5.0.0 running a VM with the following command:
$ qemu-system-x86_64 -enable-kvm -hda arch-zoom.qcow2 -m 4G -device usb-
ehci,id=ehci -device usb-
host,bus=ehci.0,vendorid=0x04f2,productid=0xb449 -device intel-hda
-device hda-duplex -vga virtio
Would
** Attachment added: "bisect-log.txt"
https://bugs.launchpad.net/qemu/+bug/1892581/+attachment/5403655/+files/bisect-log.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1892581
Title:
QEMU
My system is Arch Linux.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1892581
Title:
QEMU 5.1 no longer says anything about inaccessible devices
Status in QEMU:
New
Bug description:
The previous commit is fine, it displays the USB errors:
libusb: error [_get_usbfs_fd] libusb couldn't open USB device
/dev/bus/usb/002/004: Permission denied
libusb: error [_get_usbfs_fd] libusb requires write access to USB device nodes.
libusb: error [_get_usbfs_fd] libusb couldn't open USB
From: Eduardo Habkost
When a class inherits from an abstract parent, its class_size
is already initialized to its parent size. If the class is not
extended, it is pointless to set the class_size field again.
Signed-off-by: Eduardo Habkost
Signed-off-by: Philippe Mathieu-Daudé
---
On 8/22/20 6:18 PM, Peter Maydell wrote:
> On Sat, 22 Aug 2020 at 16:05, Philippe Mathieu-Daudé wrote:
>> Most uses of qemu_hexdump() do not take an array of char
>> as input, forcing use of cast. Since we can use this
>> helper to dump any kind of buffer, use a pointer to void
>> argument
Most uses of qemu_hexdump() do not take an array of char
as input, forcing use of cast. Since we can use this
helper to dump any kind of buffer, use a pointer to void
argument instead.
Signed-off-by: Philippe Mathieu-Daudé
---
Since v1:
- renamed argument 'bufptr' (Peter Maydell)
---
On Sat, Aug 22, 2020 at 3:20 AM Philippe Mathieu-Daudé wrote:
> On 8/21/20 10:50 PM, Max Filippov wrote:
> > please pull the following batch of updates for target/xtensa.
>
> 3.12MiB of generated data...
>
> Where does that come from?
Generated by xtensa processor generator, as one of many
On 8/12/20 9:02 PM, Philippe Mathieu-Daudé wrote:
> This series aims to ease looking at the '-d unimp' output reported
> by the UnimplementedDevice.
>
> - read/write accesses are now aligned
> - the value format width uses the access size
> - the offset (address) uses the size of the memory
On 8/6/20 3:09 PM, Philippe Mathieu-Daudé wrote:
> Fix a typo and assert sysbus_mmio_get_region() is called
> with correct index.
>
> Philippe Mathieu-Daudé (2):
> hw/core/sysbus: Fix a typo
> hw/core/sysbus: Assert memory region index is in range
>
> hw/core/sysbus.c | 3 ++-
> 1 file
On 8/6/20 3:03 PM, Philippe Mathieu-Daudé wrote:
> This series improve tracing of multiple UART device in the same
> chipset, and allow to use the Clock API to feed each device with
> an (updatable) input clock.
>
> Based-on: <20200730165900.7030-1-phi...@redhat.com>
> "hw/char: Remove
Not sure this is a bug.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1892581
Title:
QEMU 5.1 no longer says anything about inaccessible devices
Status in QEMU:
New
Bug description:
Hi Anthony,
On 8/11/20 12:55 PM, Anthony PERARD wrote:
> On Wed, Jul 22, 2020 at 10:25:17AM +0200, Philippe Mathieu-Daudé wrote:
>> Xen accelerator requires specific changes to a machine to be able
>> to use it. See for example the 'Xen PC' machine configure its PCI
>> bus calling
+Robert
On 8/7/20 12:16 PM, Paolo Bonzini wrote:
> On 07/08/20 12:02, Stefan Hajnoczi wrote:
>> On Thu, Aug 06, 2020 at 05:07:26PM +0200, Philippe Mathieu-Daudé wrote:
>>> Last uses of memory_region_clear_global_locking() have been
>>> removed in commit 7070e085d4 ("acpi: mark PMTIMER as
ping now that 5.2 is opened :)
On 8/3/20 12:56 PM, Philippe Mathieu-Daudé wrote:
> This is not a critical issue, but still annoying if you use tracing.
>
> Maybe it is worth fixing for forks that are based on release tags,
> else consider it 5.2 material.
>
> Anyway we can still discuss if
On Sat, 22 Aug 2020 at 16:05, Philippe Mathieu-Daudé wrote:
> Most uses of qemu_hexdump() do not take an array of char
> as input, forcing use of cast. Since we can use this
> helper to dump any kind of buffer, use a pointer to void
> argument instead.
>
> Signed-off-by: Philippe Mathieu-Daudé
I was changing the /dev file permissions based on the output from above,
that's why I decided to submit this bug report.
Either way, the output from lsusb works too.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
qemu_hexdump()'s pointer to the buffer and length of the
buffer are closely related arguments but are widely separated
in the argument list order (also, the format of
function prototypes is usually to have the FILE* argument
coming first).
Reorder the arguments as "fp, prefix, buf, size" which
- Pass const void* buffer
- Reorder arguments
Supersedes: <20200822150457.1322519-1-f4...@amsat.org>
Philippe Mathieu-Daudé (2):
util/hexdump: Convert to take a void pointer argument
util/hexdump: Reorder qemu_hexdump() arguments
include/qemu-common.h| 3 ++-
hw/dma/xlnx_dpdma.c
As far as I know, the Debian CD ISO images are not bootable on s390x
(they do not contain boot information according to the El-Torrito
standard). Please open a bug against Debian instead if you want to have
that changed. So far, you have to boot here manually instead (see
On Wed, 19 Aug 2020 at 16:23, Eduardo Habkost wrote:
>
> The following changes since commit 672b2f2695891b6d818bddc3ce0df964c7627969:
>
> Open 5.2 development tree (2020-08-18 13:44:04 +0100)
>
> are available in the Git repository at:
>
> git://github.com/ehabkost/qemu.git
There is an issue when accessing an alias memory region via the
memory_region_dispatch_read() / memory_region_dispatch_write()
calls.
Since commit 2cdfcf272d ("memory: assign MemoryRegionOps to all
regions") we assign _mem_ops to all MemoryRegions.
The memory_region_init_alias() flow is:
22.08.2020 20:03, Vladimir Sementsov-Ogievskiy wrote:
01.11.2019 18:25, Max Reitz wrote:
The XFS kernel driver has a bug that may cause data corruption for qcow2
images as of qemu commit c8bb23cbdbe32f. We can work around it by
treating post-EOF fallocates as serializing up until infinity
01.11.2019 18:25, Max Reitz wrote:
The XFS kernel driver has a bug that may cause data corruption for qcow2
images as of qemu commit c8bb23cbdbe32f. We can work around it by
treating post-EOF fallocates as serializing up until infinity (INT64_MAX
in practice).
Hi! I'm doing some
On Saturday, August 22, 2020, Ahmed Karaman
wrote:
> Thanks Mr. Aleksandar,
>
> "Reference" and "latest" already each has its own results directory.
>
>
I meant also source directories of these two should be separate. Name
reference source directory qemu-ref or qemu-5.1, let's say.
I will try
On 7/30/20 6:58 PM, Philippe Mathieu-Daudé wrote:
> Remove the TYPE_SERIAL_IO which is simply a superset of
> TYPE_SERIAL_MM, as suggested by Paolo and Peter here:
> https://www.mail-archive.com/qemu-devel@nongnu.org/msg721806.html
>
> Philippe Mathieu-Daudé (2):
> hw/mips/mipssim: Use MMIO
ping?
On 7/24/20 10:43 AM, Philippe Mathieu-Daudé wrote:
> cmos_get_fd_drive_type() is declared in "hw/block/fdc.h".
> This currently works because "hw/i386/pc.h" happens to
> include it. Simplify including the correct header.
>
> Fixes: 2055dbc1c9 ("acpi: move aml builder code for floppy
ping?
On 8/14/20 3:23 PM, Philippe Mathieu-Daudé wrote:
> I forgot to Cc qemu-arm@, doing it now since most of the users
> of this are ARM machines.
>
> On 8/14/20 3:21 PM, Philippe Mathieu-Daudé wrote:
>> This is the QEMU equivalent of this Linux commit (but 7 years later):
>>
On Fri, 21 Aug 2020 at 15:12, Eric Blake wrote:
>
> bitmaps patches for 2020-08-21
>
> - Andrey Shinkevich: Enhance qcow2.py for iotest inspection of qcow2 images
> - Max Reitz: Add block-bitmap-mapping migration parameter
iotest
The set of changes addresses "Diagnose "make is too old" in configure
(or in the makefile?)" from https://wiki.qemu.org/Features/Meson#Easy.
It also provides cleaner backwards compatible build invocation on macOS.
Roman Bolshakov (4):
configure: Use discovered make for in-source build
configure doesn't detect if $make is installed on the build host.
This is also helpful for hosts where an alias for make is used, i.e.
configure would fail if gmake is not present on macOS.
Signed-off-by: Roman Bolshakov
---
configure | 4
1 file changed, 4 insertions(+)
diff --git
New meson/make build requires GNU make 3.82+ but macOS ships 3.81 even
on Big Sur while homebrew provides GNU make 4.3 as 'gmake' in $PATH.
With the change, 'make' switches over to gmake implicitly.
Signed-off-by: Roman Bolshakov
---
configure | 22 ++
1 file changed, 22
On 8/17/20 12:05 PM, Bin Meng wrote:
> Cadence SD/SDIO/eMMC Host Controller (SD4HC) is an SDHCI compatible
> controller. The SDHCI compatible registers start from offset 0x200,
> which are called Slot Register Set (SRS) in its datasheet.
>
> This creates a Cadence SDHCI model built on top of the
Hi Havard,
On 8/20/20 10:30 PM, Havard Skinnemoen wrote:
> On Thu, Aug 20, 2020 at 10:46 AM Philippe Mathieu-Daudé
> wrote:
>>
>> On 8/20/20 6:24 PM, Havard Skinnemoen wrote:
>>> On Wed, Aug 19, 2020 at 10:29 PM Philippe Mathieu-Daudé
>>> wrote:
+Eric / Richard for compiler
Host CPU : Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
Host Memory : 15.49 GB
Start Time (UTC) : 2020-08-22 21:30:02
End Time (UTC) : 2020-08-22 22:35:14
Execution Time : 1:05:12.080181
Status : SUCCESS
Note:
Changes denoted by '-' are less than 0.01%.
Hi Rafael,
On 8/14/20 9:46 AM, Philippe Mathieu-Daudé wrote:
> On 8/3/20 8:09 AM, Thomas Huth wrote:
>> On 02/08/2020 00.44, Rafael Kitover wrote:
>>> Use the test from Makefile to check if vhost-user-gpu is being built,
>>> and if so require pixman.
>>
>> Fixes: 9b52b17ba5 ("configure: Allow to
On Sat, 22 Aug 2020, Philippe Mathieu-Daudé wrote:
On 4/6/20 10:34 PM, BALATON Zoltan wrote:
In some corner cases (that never happen during normal operation but a
malicious guest could program wrong values) pixman functions were
called with parameters that result in a crash. Fix this and add
QEMU build fails with cryptic messages if make is too old:
Makefile.ninja:2655: *** multiple target patterns. Stop.
To avoid the confusion it's worth to fail the build right away and print
a friendly error message.
Signed-off-by: Roman Bolshakov
---
Makefile | 5 +
1 file changed, 5
A recursive make is inovked if in-source build is used but $(MAKE) is
the same as the one used in the original make invocaton.
Some platforms have preference to use gmake, or a make passed as an
option to "configure". Honor the choice.
Signed-off-by: Roman Bolshakov
---
configure | 2 ++
1
Your pipeline has failed.
Project: QEMU ( https://gitlab.com/qemu-project/qemu )
Branch: master ( https://gitlab.com/qemu-project/qemu/-/commits/master )
Commit: 66e01f1c (
https://gitlab.com/qemu-project/qemu/-/commit/66e01f1cdc9663660201cced4df8ec0a28937919
)
Commit Message: Merge
On Fri, 21 Aug 2020 at 22:18, Paolo Bonzini wrote:
>
> The following changes since commit d6f83a72a7db94a3ede9f5cc4fb39f9c8e89f954:
>
> Merge remote-tracking branch
> 'remotes/philmd-gitlab/tags/acceptance-testing-20200812' into staging
> (2020-08-21 14:51:43 +0100)
>
> are available in the
Note for bisection: it looks like it works fine as of tag stable-4.2 .
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1892604
Title:
qemu-system-arm: ../hw/usb/hcd-dwc2.c:666: dwc2_glbreg_read:
On Tue, Aug 18, 2020 at 11:32 AM Stefan Hajnoczi wrote:
>
> Automatically size the number of virtio-scsi-pci, vhost-scsi-pci, and
> vhost-user-scsi-pci request virtqueues to match the number of vCPUs.
> Other transports continue to default to 1 request virtqueue.
>
> A 1:1 virtqueue:vCPU mapping
Public bug reported:
When trying to run the 2016-05-27 Raspbian image on the emulated raspi2
platform, the system boots but shortly after the login prompt QEMU
(master; commit ID ca489cd037e4d50dc6c40570a167504ad7e5a521) dies with:
qemu-system-arm: ../hw/usb/hcd-dwc2.c:666: dwc2_glbreg_read:
76 matches
Mail list logo
