From: Francisco Iglesias
Signed-off-by: Francisco Iglesias
Message-id: 20240906181645.40359-4-francisco.igles...@amd.com
Reviewed-by: Peter Maydell
Signed-off-by: Peter Maydell
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index b9812d46525
: Philippe Mathieu-Daudé
Message-id: 20240903144550.280-1-alireza.san...@huawei.com
Signed-off-by: Peter Maydell
---
target/arm/cpu-features.h | 50 ++
target/arm/cpu64.c| 19 ---
target/arm/tcg/cpu64.c| 108 +++---
3 files changed, 117
arhwal as maintainer
MAINTAINERS: Update Xilinx Versal OSPI maintainer's email address
MAINTAINERS: Add my-self as CAN maintainer
Jan Klötzke (1):
hw/intc/arm_gic: fix spurious level triggered interrupts
Johannes Stoelp (1):
kvm: Use 'unsigned long' for request argument in
DeviceClass::legacy_reset method.
This will allow us to remove all the get_transitional_function
handling from resettable.c.
Signed-off-by: Peter Maydell
Reviewed-by: Philippe Mathieu-Daudé
Message-id: 20240830145812.1967042-11-peter.mayd...@linaro.org
---
hw/core/qdev.c | 55
o admittedly it is much less
generic than kvm_type today, but it seemed a somewhat sane way to get
the information we need from the memmap at VM creation time.
Signed-off-by: Danny Canter
Message-id: 20240828111552.93482-2-danny_can...@apple.com
Reviewed-by: Peter Maydell
[PMM: removed explicit s
!= NULL.
Signed-off-by: Peter Maydell
Reviewed-by: Richard Henderson
Message-id: 20240830145812.1967042-10-peter.mayd...@linaro.org
---
hw/core/qdev.c | 51 --
1 file changed, 12 insertions(+), 39 deletions(-)
diff --git a/hw/core/qdev.c b/hw/core
There are no callers of device_class_set_parent_reset() left in the tree,
as they've all been converted to use three-phase reset and the
corresponding resettable_class_set_parent_phases() function.
Remove device_class_set_parent_reset().
Signed-off-by: Peter Maydell
Reviewed-by: Philippe Ma
Rename the DeviceClass::reset field to legacy_reset; this is helpful
both in flagging up that it's best not used in new code and in
making it easy to search for where it's being used still.
Signed-off-by: Peter Maydell
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Richard Henderso
On Thu, 12 Sept 2024 at 07:53, Philippe Mathieu-Daudé wrote:
>
> v2:
> - Fill Pierrick's commit description suggested by Eric Blake
> - Include TMP105 fixes from Guenter
>
> The following changes since commit a4eb31c678400472de0b4915b9154a7c20d8332f:
>
> Merge tag 'pull-testing-gdbstub-oct-10092
On Fri, 13 Sept 2024 at 15:05, Daniel P. Berrangé wrote:
>
> On Fri, Sep 13, 2024 at 02:31:34PM +0100, Peter Maydell wrote:
> > On Fri, 13 Sept 2024 at 13:24, Peter Maydell
> > wrote:
> > >
> > > On Thu, 12 Sept 2024 at 16:10, Peter Maydell
> > >
On Thu, 12 Sept 2024 at 14:09, Song Gao wrote:
>
> The following changes since commit 4b7ea33074450bc6148c8e1545d78f179e64adb4:
>
> Merge tag 'pull-request-2024-09-11' of https://gitlab.com/thuth/qemu into
> staging (2024-09-11 19:28:23 +0100)
>
> are available in the Git repository at:
>
> h
On Thu, 12 Sept 2024 at 06:30, Richard Henderson
wrote:
>
> The following changes since commit a4eb31c678400472de0b4915b9154a7c20d8332f:
>
> Merge tag 'pull-testing-gdbstub-oct-100924-1' of
> https://gitlab.com/stsquad/qemu into staging (2024-09-11 13:17:29 +0100)
>
> are available in the Git r
On Fri, 13 Sept 2024 at 13:24, Peter Maydell wrote:
>
> On Thu, 12 Sept 2024 at 16:10, Peter Maydell wrote:
> >
> > The cross-i686-tci CI job is persistently flaky with various tests
> > hitting timeouts. One theory for why this is happening is that we're
> >
On Thu, 12 Sept 2024 at 16:10, Peter Maydell wrote:
>
> The cross-i686-tci CI job is persistently flaky with various tests
> hitting timeouts. One theory for why this is happening is that we're
> running too many tests in parallel and so sometimes a test gets
> starved of C
On Fri, 13 Sept 2024 at 12:29, Markus Armbruster wrote:
>
> Peter Maydell writes:
> > Specifically, if you don't disable the error-exit when qtest
> > is in use, then the generic qom-test tests which say "can we
> > at least instantiate every machine?"
On Thu, 12 Sept 2024 at 06:30, Alistair Francis wrote:
>
> The following changes since commit a4eb31c678400472de0b4915b9154a7c20d8332f:
>
> Merge tag 'pull-testing-gdbstub-oct-100924-1' of
> https://gitlab.com/stsquad/qemu into staging (2024-09-11 13:17:29 +0100)
>
> are available in the Git re
On Fri, 13 Sept 2024 at 11:02, Markus Armbruster wrote:
>
> Fabiano Rosas writes:
> > I could add error/warn variants that are noop in case qtest is
> > enabled. It would, however, lead to this pattern which is discouraged by
> > the error.h documentation (+Cc Markus for advice):
> >
> > before:
On Fri, 13 Sept 2024 at 09:28, Markus Armbruster wrote:
>
> Peter Maydell writes:
>
> > On Tue, 3 Sept 2024 at 21:04, Philippe Mathieu-Daudé
> > wrote:
> >>
> >> sd_set_cb() was only used by omap2_mmc_init() which
> >> got recently removed. Time
On Wed, 11 Sept 2024 at 14:51, Michael S. Tsirkin wrote:
>
> The following changes since commit a66f28df650166ae8b50c992eea45e7b247f4143:
>
> Merge tag 'migration-20240909-pull-request' of
> https://gitlab.com/peterx/qemu into staging (2024-09-10 11:19:22 +0100)
>
> are available in the Git rep
On Wed, 11 Sept 2024 at 13:34, Paolo Bonzini wrote:
>
> The following changes since commit 7b87a25f49a301d3377f3e71e0b4a62540c6f6e4:
>
> Merge tag 'edgar/xen-queue-2024-09-04.for-upstream' of
> https://gitlab.com/edgar.iglesias/qemu into staging (2024-09-05 13:02:26
> +0100)
>
> are available
On Thu, 12 Sept 2024 at 16:09, Peter Xu wrote:
>
> On Thu, Sep 12, 2024 at 09:13:16AM +0100, Peter Maydell wrote:
> > On Wed, 11 Sept 2024 at 22:26, Fabiano Rosas wrote:
> > > I don't think we're discussing total CI time at this point, so the math
> > >
I job runs in seems to cause us to default
to a parallelism of 9 in the main CI.)
Signed-off-by: Peter Maydell
---
If this works we might be able to wind this up to -j2 or -j3,
and/or consider whether other CI jobs need something similar.
---
.gitlab-ci.d/crossbuilds.yml | 6 +-
1 file
On Mon, 19 Aug 2024 at 14:56, Mattias Nissler wrote:
>
> When DMA memory can't be directly accessed, as is the case when
> running the device model in a separate process without shareable DMA
> file descriptors, bounce buffering is used.
>
> It is not uncommon for device models to request mapping
On Thu, 12 Sept 2024 at 14:48, Fabiano Rosas wrote:
> Peter Maydell writes:
> > For some examples from this week:
> >
> > https://gitlab.com/qemu-project/qemu/-/jobs/7802183144
> > https://gitlab.com/qemu-project/qemu/-/jobs/7799842373
> > https://gitlab.com/qe
; Signed-off-by: Richard Henderson
Reviewed-by: Peter Maydell
thanks
-- PMM
On Wed, 11 Sept 2024 at 12:49, Jan Klötzke wrote:
>
> On GICv2 and later, level triggered interrupts are pending when either
> the interrupt line is asserted or the interrupt was made pending by a
> GICD_ISPENDRn write. Making a level triggered interrupt pending by
> software persists until either
On Fri, 6 Sept 2024 at 19:16, Francisco Iglesias
wrote:
>
> Hi all,
>
> I'm not in possesion of Vikram's new email address at his new job, because of
> this the first patch in the series suggest's to remove Vikram as maintainer
> for
> the Xilinx CAN models and also the CAN bus subsystem. The sec
On Thu, 12 Sept 2024 at 12:59, Philippe Mathieu-Daudé wrote:
>
> On 12/9/24 09:38, Pierrick Bouvier wrote:
> > This patch is part of a series that moves towards a consistent use of
> > g_assert_not_reached() rather than an ad hoc mix of different
> > assertion mechanisms.
> >
> > Reviewed-by: Rich
On Wed, 11 Sept 2024 at 10:34, Thomas Huth wrote:
>
> Hi Peter!
>
> The following changes since commit a66f28df650166ae8b50c992eea45e7b247f4143:
>
> Merge tag 'migration-20240909-pull-request' of
> https://gitlab.com/peterx/qemu into staging (2024-09-10 11:19:22 +0100)
>
> are available in the
On Wed, 11 Sept 2024 at 23:30, Sergey Makarov wrote:
>
> *** Patchset goal ***
>
> This patchset aims to improve standard conformance for SiFive PLIC
> implementation.
>
> *** Testing cases ***
>
> Currently there are no automated tests for these changes, but there
> are several test cases, with w
On Wed, 11 Sept 2024 at 22:26, Fabiano Rosas wrote:
> I don't think we're discussing total CI time at this point, so the math
> doesn't really add up. We're not looking into making the CI finish
> faster. We're looking into making migration-test finish faster. That
> would reduce timeouts in CI, s
On Wed, 11 Sept 2024 at 07:47, Alex Bennée wrote:
>
> The following changes since commit a66f28df650166ae8b50c992eea45e7b247f4143:
>
> Merge tag 'migration-20240909-pull-request' of
> https://gitlab.com/peterx/qemu into staging (2024-09-10 11:19:22 +0100)
>
> are available in the Git repository
On Tue, 10 Sept 2024 at 17:47, Markus Armbruster wrote:
>
> The following changes since commit 7bbadc60b58b742494555f06cd342311ddab9351:
>
> Merge tag 'crypto-fixes-pull-request' of https://gitlab.com/berrange/qemu
> into staging (2024-09-09 15:19:32 +0100)
>
> are available in the Git reposito
On Wed, 11 Sept 2024 at 11:54, Jan Klötzke wrote:
>
> On Fri, 2024-09-06 at 13:50 +0100, Peter Maydell wrote:
> > On Mon, 2 Sept 2024 at 13:32, Jan Klötzke
> > wrote:
> > >
> > > Level triggered interrupts are pending when either the interrupt line
> &g
On Wed, 11 Sept 2024 at 07:50, Ganapatrao Kulkarni
wrote:
>
>
>
> On 10-09-2024 05:53 pm, Peter Maydell wrote:
> > On Tue, 10 Sept 2024 at 12:57, Ganapatrao Kulkarni
> > wrote:
> >> On 16-07-2024 09:15 pm, Peter Maydell wrote:
> >>> Since Cornelia
On Wed, 11 Sept 2024 at 07:27, Jacob Abrams wrote:
> On 9/10/24 02:34, Peter Maydell wrote:
> > If we make the .impl and .valid changes, then the result is
> > that we permit 16 bit writes to come through to the read
> > and write functions. Since we don't make any chan
On Tue, 10 Sept 2024 at 18:27, Michael S. Tsirkin wrote:
>
> On Thu, Aug 29, 2024 at 02:46:48PM +0900, Akihiko Odaki wrote:
> > Previously it was allowed to call object_unparent() for a memory region
> > in instance_finalize() of its parent. However, such a call typically
> > has no effect because
On Tue, 10 Sept 2024 at 15:53, Michael S. Tsirkin wrote:
>
> On Mon, Aug 19, 2024 at 06:54:54AM -0700, Mattias Nissler wrote:
> > When DMA memory can't be directly accessed, as is the case when
> > running the device model in a separate process without shareable DMA
> > file descriptors, bounce bu
On Tue, 10 Sept 2024 at 13:37, Thomas Huth wrote:
>
> The following changes since commit 7bbadc60b58b742494555f06cd342311ddab9351:
>
> Merge tag 'crypto-fixes-pull-request' of https://gitlab.com/berrange/qemu
> into staging (2024-09-09 15:19:32 +0100)
>
> are available in the Git repository at:
On Tue, 10 Sept 2024 at 16:31, Michael S. Tsirkin wrote:
>
> On Thu, Sep 05, 2024 at 08:05:14PM +0100, Peter Maydell wrote:
> > On Thu, 5 Sept 2024 at 19:22, Daniel P. Berrangé
> > wrote:
> > >
> > > On Fri, Aug 16, 2024 at 11:47:16AM +0100, Daniel P. Be
onvert vector [US]QSHRN, [US]QRSHRN, SQSHRUN to
> decodetree
> target/arm: Convert scalar [US]QSHRN, [US]QRSHRN, SQSHRUN to
> decodetree
Other than my comments on the NeonGenNarrowEnvFn patch,
series
Reviewed-by: Peter Maydell
thanks
-- PMM
On Mon, 9 Sept 2024 at 21:11, Peter Xu wrote:
>
> The following changes since commit f2aee60305a1e40374b2fc1093e4d04404e780ee:
>
> Merge tag 'pull-request-2024-09-08' of https://gitlab.com/huth/qemu into
> staging (2024-09-09 10:47:24 +0100)
>
> are available in the Git repository at:
>
> htt
On Mon, 9 Sept 2024 at 17:25, Richard Henderson
wrote:
>
> While these functions really do return a 32-bit value,
> widening the return type means that we need do less
> marshalling between TCG types.
>
> Remove NeonGenNarrowEnvFn typedef; add NeonGenOne64OpEnvFn.
>
> Signed-off-by: Richard Hender
On Mon, 9 Sept 2024 at 23:24, Philippe Mathieu-Daudé wrote:
>
> On 9/9/24 18:22, Richard Henderson wrote:
> > Reviewed-by: Peter Maydell
>
> I wonder, maybe you mispasted my previous R-b tags
> with Peter's?
> https://lore.kernel.org/qemu-devel/37096dc8-7827-4a4c-a27
On Tue, 10 Sept 2024 at 12:57, Ganapatrao Kulkarni
wrote:
> On 16-07-2024 09:15 pm, Peter Maydell wrote:
> > Since Cornelia first wrote the patch this is based on, we've
> > landed gdbstub support for MTE (so gdb can find out which
> > addresses in the memory map ha
On Tue, 10 Sept 2024 at 13:13, Thomas Huth wrote:
>
> On 06/09/2024 20.07, Peter Maydell wrote:
> > The cross-i686-tci CI job is persistently flaky with various tests
> > hitting timeouts. One theory for why this is happening is that we're
> > running too many tests
On Tue, 10 Sept 2024 at 08:37, Thomas Huth wrote:
>
> On 10/09/2024 08.41, Philippe Mathieu-Daudé wrote:
> > While looking at this, I'm surprised to notice has_cmd() actually
> > *runs* the command by calling run_cmd(). I'd have expected it solely
> > checks for binary presence and RX perms, avoid
On Mon, 9 Sept 2024 at 16:02, Peter Maydell wrote:
>
> On Mon, 9 Sept 2024 at 15:55, Guenter Roeck wrote:
> >
> > On 9/9/24 06:40, Philippe Mathieu-Daudé wrote:
> > > Hi,
> > >
> > > On 3/9/24 18:06, Peter Maydell wrote:
> > >> This patc
On Tue, 10 Sept 2024 at 10:03, Igor Mammedov wrote:
>
> On Mon, 19 Aug 2024 15:43:03 +0100
> Peter Maydell wrote:
>
> > At some point the way we allocate socket-id and core-id to CPUs
> > by default changed; update the example of how to do CPU hotplug
> > and unplu
On Mon, 9 Sept 2024 at 18:40, Philippe Mathieu-Daudé wrote:
>
> Hi,
>
> (Cc'ing Arnaud & Inès who are listed as maintainers)
>
> On 6/9/24 18:12, Peter Maydell wrote:
> > On Mon, 2 Sept 2024 at 14:38, Jacob Abrams wrote:
> >>
> >> These chan
On Mon, 9 Sept 2024 at 18:25, Philippe Mathieu-Daudé wrote:
>
> Hi Peter,
>
> On 9/9/24 15:44, Peter Maydell wrote:
> > On Mon, 9 Sept 2024 at 14:41, Philippe Mathieu-Daudé
> > wrote:
> >>
> >> Hi,
> >>
> >> On 3/9/24 18:06, Pete
On Mon, 9 Sept 2024 at 17:19, Richard Henderson
wrote:
>
> On 9/8/24 22:26, Michael Tokarev wrote:
> >> Why do you think this is an improvement?
> >
> > It just feels more natural, so to say.
> >
> >> What was wrong with the function pointers?
> >
> > Not exactly wrong. It just hurts my eyes when
On Mon, 9 Sept 2024 at 15:17, Daniel P. Berrangé wrote:
>
> The following changes since commit f2aee60305a1e40374b2fc1093e4d04404e780ee:
>
> Merge tag 'pull-request-2024-09-08' of https://gitlab.com/huth/qemu into
> staging (2024-09-09 10:47:24 +0100)
>
> are available in the Git repository at:
On Mon, 9 Sept 2024 at 16:23, Alex Bennée wrote:
> I guess one question is are we getting value from all the extra
> migration tests? There certainly seem to be some sub-tests that are
> slower than the others and I assume testing a small delta on the tests
> before it.
>
> On s390x it seems the n
On Tue, 3 Sept 2024 at 21:04, Philippe Mathieu-Daudé wrote:
>
> sd_set_cb() was only used by omap2_mmc_init() which
> got recently removed. Time to remove it. For historical
> background on the me_no_qdev_me_kill_mammoth_with_rocks
> kludge, see commit 007d1dbf72 ("sd: Hide the qdev-but-not-quite
gt; return dummy_byte;
>
> if (sd->state != sd_sendingdata_state) {
Maybe add the { } that coding style wants to these if()s
since we're editing them anyway?
Either way,
Reviewed-by: Peter Maydell
thanks
-- PMM
On Mon, 9 Sept 2024 at 15:55, Guenter Roeck wrote:
>
> On 9/9/24 06:40, Philippe Mathieu-Daudé wrote:
> > Hi,
> >
> > On 3/9/24 18:06, Peter Maydell wrote:
> >> This patchset removes the various Arm machines which we deprecated
> >> for the 9.0 release a
On Mon, 9 Sept 2024 at 15:22, Zhou Wang via wrote:
>
> Hi All,
>
> When I tested mainline qemu(commit 7b87a25f49), it reports smmuv3 event 0x10
> during kernel booting up.
Does it still do this if you either:
(1) use the v9.1.0 release (commit fd1952d814da)
(2) use "-machine virt-9.1" instead o
On Mon, 9 Sept 2024 at 14:51, Hyman Huang wrote:
>
> Despite the fact that the responsive CPU throttle is enabled,
> the dirty sync count may not always increase because this is
> an optimization that might not happen in any situation.
>
> This test case just making sure it doesn't interfere with
On Tue, 27 Aug 2024 at 04:51, Doug Brown wrote:
>
> This series fixes several problems I ran into while trying to simulate
> the AMD/Xilinx Versal CANFD controller in the xlnx-versal-virt machine
> using Xilinx's v6.6_LTS_2024.1 kernel. With all of these patches
> applied, everything works correct
On Mon, 9 Sept 2024 at 14:41, Philippe Mathieu-Daudé wrote:
>
> Hi,
>
> On 3/9/24 18:06, Peter Maydell wrote:
> > This patchset removes the various Arm machines which we deprecated
> > for the 9.0 release and are therefore allowed to remove for the 9.2
> > release
nificantly increases the runtime. For an all-architectures build
on my local machine 'make check -j8' goes from
real8m19.127s
user31m47.534s
sys 19m42.650s
to
real20m31.218s
user32m48.712s
sys 19m52.133s
more than doubling the wallclock runtime.
Signed-o
nge check 'slot' property (2024-09-08 11:49:49
> +0200)
>
>
> * Fix Coverity issues in mcf5208evb and nubus machines
> * Add URLs for mcf5208evb datasheets
>
>
>
> Peter Maydell (3):
> hw/m68k
On Mon, 9 Sept 2024 at 11:28, Peter Maydell wrote:
>
> On Wed, 4 Sept 2024 at 13:48, Fabiano Rosas wrote:
> >
> > In preparation for adding new payload types to multifd, move most of
> > the no-compression code into multifd-nocomp.c. Let's try to keep a
> >
On Wed, 4 Sept 2024 at 13:48, Fabiano Rosas wrote:
>
> In preparation for adding new payload types to multifd, move most of
> the no-compression code into multifd-nocomp.c. Let's try to keep a
> semblance of layering by not mixing general multifd control flow with
> the details of transmitting pag
On Sat, 7 Sept 2024 at 08:00, Michael Tokarev wrote:
>
> There's a slight difference in fcntl locking handling on arm and others:
> arm has 2 variants of struct flock argument handling, with and without eabi.
> For this reason, we currently take address of the conversion function into
> a variable
On Fri, 6 Sept 2024 at 11:58, Jeuk Kim wrote:
>
> From: Jeuk Kim
>
> The following changes since commit 7b87a25f49a301d3377f3e71e0b4a62540c6f6e4:
>
> Merge tag 'edgar/xen-queue-2024-09-04.for-upstream' of
> https://gitlab.com/edgar.iglesias/qemu into staging (2024-09-05 13:02:26
> +0100)
>
>
On Sat, 7 Sept 2024 at 07:39, Michael Tokarev wrote:
>
> 07.09.2024 02:59, Kenneth Adam Miller wrote:
> > Hello,
> >
> > I'm on commit bd80b59 and my host is:
>
> $ git desc bd80b59
> v2.4.0-rc3-9-gbd80b5963f
>
> Date: Mon Aug 3 11:44:07 2015 +0100
Wow, that is very old. So the answer, in order
On Sat, 7 Sept 2024 at 06:42, Philippe Mathieu-Daudé wrote:
>
> Hi Peter,
>
> On 19/7/24 20:10, Philippe Mathieu-Daudé wrote:
>
> > Philippe Mathieu-Daudé (16):
>
> >hw/char/pl011: Remove unused 'readbuff' field
> >hw/char/pl011: Move pl011_put_fifo() earlier
> >hw/char/pl011: Move pl0
meson test' passing it a --num-processes
argument based on whatever the '-j' option to make was. Adjust the
logic in mtest2make so that if MESON_TESTTHREADS is set then we
honour that, and don't override it.
Signed-off-by: Peter Maydell
---
scripts/mtest2make.py | 4
1 f
ESTTHREADS environment variable to 1 for this job;
this will cause 'meson test' to run only one test at a time.
(Note that this relies on the change to meson2make that makes it
honour MESON_TESTTHREADS; otherwise it will have no effect.)
Signed-off-by: Peter Maydell
---
Seems worth a try -- if
ider whether we should
do something similar across the board -- at the moment we
always use a parallelism of num-cpus + 1, because we use the
same amount of parallelism that we do for the compile step.
thanks
-- PMM
Peter Maydell (2):
scripts/mtest2make: Honour MESON_TESTTHREADS if it is set
.gitlab-ci
On Mon, 2 Sept 2024 at 14:38, Jacob Abrams wrote:
>
> These changes allow the official STM32L4xx HAL UART driver to function
> properly with the b-l475e-iot01a machine.
>
> Modifying USART_CR1 TE bit should alter USART_ISR TEACK bit, and
> likewise for RE and REACK bit.
>
> USART registers may be
On Tue, 3 Sept 2024 at 15:45, Alireza Sanaee wrote:
>
> This patch allows for easier manipulation of the cache description
> register, CCSIDR. Which is helpful for testing as well. Currently,
> numbers get hard-coded and might be prone to errors.
>
> Therefore, this patch adds a wrapper for differ
Is that modify this config that will be
> coming in future patches). This should have no
> behavioral difference at all as hv_vm_config_create()
> just assigns the same default values as if you just
> passed NULL to the function.
>
> Signed-off-by: Danny Canter
Reviewed-by: Peter Maydell
thanks
-- PMM
On Wed, 28 Aug 2024 at 12:16, Danny Canter wrote:
>
> This patchsets focus is on lighting up the ability to create VMs with 64+GB
> of RAM through using some new APIs introduced in macOS 13. Due to the IPA
> sizes
> supported in macOS, the first version we can properly support this requirement
>
ows VMs with 64+ GB of RAM and should fix the
> oddness of the PARange situation as well.
>
> Signed-off-by: Danny Canter
Reviewed-by: Peter Maydell
thanks
-- PMM
d = true;
> nc->nmi_monitor_handler = x86_nmi;
We guarantee that object and class structs are zero-initialized,
so we don't need to explicitly set this field to NULL.
Otherwise
Reviewed-by: Peter Maydell
thanks
-- PMM
On Mon, 19 Aug 2024 at 15:43, Peter Maydell wrote:
>
> At some point the way we allocate socket-id and core-id to CPUs
> by default changed; update the example of how to do CPU hotplug
> and unplug so the example commands work again. The differences
> in the sample input and outpu
Ping for review on these docs conversions, please?
thanks
-- PMM
On Fri, 16 Aug 2024 at 14:22, Peter Maydell wrote:
>
> This patchset converts a collection of the remaining txt files in
> docs/devel to rST format. At this point in the release cycle
> I'm targeting 9.2 for these
On Thu, 15 Aug 2024 at 14:12, Peter Maydell wrote:
>
> This patchset fixes a couple of minor Coverity nits:
> * a can't-happen integer overflow when assigning from a long to
>an int in kvm_init_vcpu()
> * some unreachable code in kvm_dirty_ring_reaper_thread()
>
&g
On Fri, 30 Aug 2024 at 15:58, Peter Maydell wrote:
>
> The main aim of this patchseries is to remove the two remaining uses
> of device_class_set_parent_reset() in the tree, which are virtio-ccw
> and the s390 CPU class. Doing that lets us do some followup cleanup.
> (The diffstat
On Tue, 27 Aug 2024 at 04:51, Doug Brown wrote:
>
> This series fixes several problems I ran into while trying to simulate
> the AMD/Xilinx Versal CANFD controller in the xlnx-versal-virt machine
> using Xilinx's v6.6_LTS_2024.1 kernel. With all of these patches
> applied, everything works correct
On Thu, 5 Sept 2024 at 17:55, Peter Maydell wrote:
>
> I noticed that 'make vm-build-openbsd' had bitrotted a bit:
> * two tests for the stm32l4x5 forgot a qtest_quit(), which meant
>they would pass all their subtests but then timeout because the
>underlying
On Thu, 5 Sept 2024 at 14:01, Peter Maydell wrote:
>
> First target-arm queue for 9.2. I know I have more stuff in
> my to-review queue after this...
>
> -- PMM
>
> The following changes since commit cab1afb393ea0943b3086188e91d71d594ede6bf:
>
> Merge tag '
On Wed, 4 Sept 2024 at 13:49, Fabiano Rosas wrote:
>
> The following changes since commit e638d685ec2a0700fb9529cbd1b2823ac4120c53:
>
> Open 9.2 development tree (2024-09-03 09:18:43 -0700)
>
> are available in the Git repository at:
>
> https://gitlab.com/farosas/qemu.git tags/migration-20240
On Mon, 2 Sept 2024 at 13:32, Jan Klötzke wrote:
>
> Level triggered interrupts are pending when either the interrupt line
> is asserted or the interrupt was made pending by a GICD_ISPENDRn write.
> Making a level triggered interrupt pending by software persists until
> either the interrupt is ack
On Wed, 4 Sept 2024 at 11:40, Thomas Huth wrote:
>
> Hi!
>
> The following changes since commit e638d685ec2a0700fb9529cbd1b2823ac4120c53:
>
> Open 9.2 development tree (2024-09-03 09:18:43 -0700)
>
> are available in the Git repository at:
>
> https://gitlab.com/thuth/qemu.git tags/pull-reque
On Fri, 6 Sept 2024 at 09:14, Daniel P. Berrangé wrote:
>
> On Fri, Sep 06, 2024 at 08:16:31AM +0200, Thomas Huth wrote:
> > On 05/09/2024 23.03, Fabiano Rosas wrote:
> > > Hi,
> > >
> > > This series silences QEMU stderr unless the QTEST_LOG variable is set
> > > and silences -qtest-log unless bo
On Fri, 6 Sept 2024 at 10:30, Thomas Huth wrote:
>
> On 06/09/2024 10.58, Peter Maydell wrote:
> > On Fri, 6 Sept 2024 at 09:09, Thomas Huth wrote:
> >>
> >> When QEMU has been configured with "--without-default-devices", the build
> >> is current
On Fri, 6 Sept 2024 at 09:09, Thomas Huth wrote:
>
> When QEMU has been configured with "--without-default-devices", the build
> is currently failing with:
>
> /usr/bin/ld: libqemu-riscv32-softmmu.a.p/target_riscv_cpu_helper.c.o:
> in function `riscv_cpu_do_interrupt':
> .../qemu/target/riscv/
On Thu, 5 Sept 2024 at 20:44, Richard Henderson
wrote:
>
> On 9/5/24 08:06, Milan P. Stanić wrote:
> > build fails on musl libc (alpine linux) with this error:
> >
> > ../util/cpuinfo-riscv.c: In function 'cpuinfo_init':
> > ../util/cpuinfo-riscv.c:63:21: error: '__NR_riscv_hwprobe' undeclared
>
On Thu, 5 Sept 2024 at 20:34, Fabiano Rosas wrote:
>
> Peter Xu writes:
>
> > On Thu, Sep 05, 2024 at 03:54:45PM -0300, Fabiano Rosas wrote:
> >> The vmstate-checker-script test has a bug that makes it flaky. It was
> >> also committed by mistake and will be removed.
> >>
> >> Since the migration
On Thu, 5 Sept 2024 at 20:16, Thomas Huth wrote:
>
> This reverts commit 10425887ba54241be1ce97f8935fc320332b531c.
>
> Using "imply" instead of "select" is causing a build failure:
>
> /usr/bin/ld: libqemu-riscv32-softmmu.a.p/target_riscv_cpu_helper.c.o: in
> function `riscv_cpu_do_interrupt':
>
On Thu, 5 Sept 2024 at 19:22, Daniel P. Berrangé wrote:
>
> On Fri, Aug 16, 2024 at 11:47:16AM +0100, Daniel P. Berrangé wrote:
> > On Fri, Aug 16, 2024 at 12:37:23PM +0200, Cornelia Huck wrote:
> > > Add 9.2 machine types for arm/i440fx/m68k/q35/s390x/spapr.
> > >
> > > Signed-off-by: Cornelia Hu
to a SIGTERM or polite request
to quit, but it also sidestepped the problem in this case.
However, OpenBSD doesn't have a PDEATHSIG equivalent, so we
see the timeouts when running a 'make vm-build-openbsd' run.
Add the missing qtest_quit() calls.
Signed-off-by: Peter Maydell
---
Many th
On my OpenBSD VM test system, the ahci-test sometimes hits its 60 second
timeout. It has 75 subtests and allowing at least two seconds per
subtest seems reasonable. Bump it to 150s.
Signed-off-by: Peter Maydell
---
tests/qtest/meson.build | 1 +
1 file changed, 1 insertion(+)
diff --git a
s patchset fixes these.
thanks
-- PMM
Peter Maydell (2):
tests/qtest: Add missing qtest_quit() to stm32 tests
tests/qtest: Bump timeout on ahci-test
tests/qtest/dm163-test.c | 2 ++
tests/qtest/stm32l4x5_usart-test.c | 2 ++
tests/qtest/meson.build| 1 +
3 files changed, 5
On Wed, 4 Sept 2024 at 17:15, Edgar E. Iglesias
wrote:
>
> From: "Edgar E. Iglesias"
>
> The following changes since commit e638d685ec2a0700fb9529cbd1b2823ac4120c53:
>
> Open 9.2 development tree (2024-09-03 09:18:43 -0700)
>
> are available in the Git repository at:
>
> https://gitlab.com/ed
On Thu, 5 Sept 2024 at 14:19, Milan P. Stanić wrote:
>
> build fails on musl libc (alpine linux) with this error:
>
> ../util/cpuinfo-riscv.c: In function 'cpuinfo_init':
> ../util/cpuinfo-riscv.c:63:21: error: '__NR_riscv_hwprobe' undeclared (first
> use in this function); did you mean 'riscv_hw
101 - 200 of 21226 matches
Mail list logo
