On Thu, Nov 24, 2022 at 01:50:19AM -0500, Michael S. Tsirkin wrote:
On Thu, Nov 24, 2022 at 12:19:25AM +, Raphael Norwitz wrote:
> On Nov 23, 2022, at 8:16 AM, Stefano Garzarella wrote:
>
> Commit 02b61f38d3 ("hw/virtio: incorporate backend features in features")
> properly negotiates VHOS
On Thu, Nov 24, 2022 at 03:31:59PM +0800, Jason Wang wrote:
> On Thu, Nov 24, 2022 at 3:06 PM Michael S. Tsirkin wrote:
> >
> > On Thu, Nov 24, 2022 at 12:12:15PM +0800, Jason Wang wrote:
> > > On Wed, Nov 23, 2022 at 3:21 PM Michael S. Tsirkin
> > > wrote:
> > > >
> > > > On Wed, Nov 23, 2022 a
On Thu, Nov 24, 2022 at 3:06 PM Michael S. Tsirkin wrote:
>
> On Thu, Nov 24, 2022 at 12:12:15PM +0800, Jason Wang wrote:
> > On Wed, Nov 23, 2022 at 3:21 PM Michael S. Tsirkin wrote:
> > >
> > > On Wed, Nov 23, 2022 at 03:08:25PM +0800, Jason Wang wrote:
> > > > On Wed, Nov 23, 2022 at 2:15 PM M
From: Dongwon Kim
A warning, "qemu: warning: console: no gl-unblock within" followed by
guest scanout lockup can happen if dpy_gl_update is called in a row
and the second call is made before gd_draw_event scheduled by the first
call is taking place. This is because draw call returns without decre
From: Claudio Fontana
The GTK Clipboard implementation may cause guest hangs.
Therefore implement new configure switch: --enable-gtk-clipboard,
as a meson option disabled by default, which warns in the help
text about the experimental nature of the feature.
Regenerate the meson build options to
From: Michael Tokarev
Fixes: effaf5a240e03020f4ae953e10b764622c3e87cc
Signed-off-by: Michael Tokarev
Reviewed-by: Thomas Huth
Reviewed-by: Stefan Weil
Message-Id: <20221105114851.306206-1-...@msgid.tls.msk.ru>
Signed-off-by: Gerd Hoffmann
---
hw/usb/hcd-xhci.c | 2 +-
1 file changed, 1 inser
The following changes since commit 7c09a7f6ae1770d15535980d15dffdb23f4d9786:
Update VERSION for v7.2.0-rc2 (2022-11-22 18:59:56 -0500)
are available in the Git repository at:
https://gitlab.com/kraxel/qemu.git tags/fixes-20221124-pull-request
for you to fetch changes up to 64f1359bd08060ffe
From: Joelle van Dyne
Run state is also in RUN_STATE_PRELAUNCH while "-S" is used.
This reverts commit 0631d4b448454ae8a1ab091c447e3f71ab6e088a
Signed-off-by: Joelle van Dyne
Reviewed-by: Ján Tomko
The original commit broke the usage of usbredir with libvirt, which
starts every domain with "
Il mer 23 nov 2022, 08:59 Marc-André Lureau ha
scritto:
> config USB_SMARTCARD_PASSTHRU
> bool
> default y
> select USB_SMARTCARD
>
> config USB_SMARTCARD_EMULATED
> bool
> default y
> select USB_SMARTCARD
>
Yes, this is the way. (TM)
Also, you should add a "config LIBCA
On Thu, Nov 24, 2022 at 12:12:15PM +0800, Jason Wang wrote:
> On Wed, Nov 23, 2022 at 3:21 PM Michael S. Tsirkin wrote:
> >
> > On Wed, Nov 23, 2022 at 03:08:25PM +0800, Jason Wang wrote:
> > > On Wed, Nov 23, 2022 at 2:15 PM Michael S. Tsirkin
> > > wrote:
> > > >
> > > > On Wed, Nov 23, 2022 a
Il mer 23 nov 2022, 17:29 Kevin Wolf ha scritto:
> As I said, personally, I don't feel like putting QEMU_IN_COROUTINE()
> assertions into every coroutine_fn is a useful thing to do. Static
> analysis (maybe even with something vrc based in 'make check'? Paolo,
> would this be realistic?)
Yes, u
Il mer 23 nov 2022, 17:49 Kevin Wolf ha scritto:
> I already asked about other opinions on this in patch 1.
>
> These assertions are runtime checks and I don't feel they are the right
> tool to verify coroutine_fn consistency. Asserting in tricky places
> makes sense to me, especially as long as
On Thu, Nov 24, 2022 at 12:19:25AM +, Raphael Norwitz wrote:
>
> > On Nov 23, 2022, at 8:16 AM, Stefano Garzarella wrote:
> >
> > Commit 02b61f38d3 ("hw/virtio: incorporate backend features in features")
> > properly negotiates VHOST_USER_F_PROTOCOL_FEATURES with the vhost-user
> > backend,
Adds checks to the hashst and hashchk instructions to only execute if
enabled by the relevant aspect in the DEXCR and HDEXCR.
This behaviour is guarded behind TARGET_PPC64 since Power10 is
currently the only implementation which has the DEXCR.
Signed-off-by: Nicholas Miehlbradt
---
target/ppc/e
Define the DEXCR and HDEXCR as special purpose registers.
Each register occupies two SPR indicies, one which can be read in an
unprivileged state and one which can be modified in the appropriate
priviliged state, however both indicies refer to the same underlying
value.
Note that the ISA uses the
Implements the Dynamic Execution Control Register (DEXCR) and the
Hypervisor Dynamic Execution Control Register (HDEXCR) in TCG as
defined in Power ISA 3.1B. Only aspects 5 (Non-privileged hash instruction
enable) and 6 (Privileged hash instruction enable) have architectural
effects. Other aspec
On Wed, Nov 23, 2022 at 3:21 PM Michael S. Tsirkin wrote:
>
> On Wed, Nov 23, 2022 at 03:08:25PM +0800, Jason Wang wrote:
> > On Wed, Nov 23, 2022 at 2:15 PM Michael S. Tsirkin wrote:
> > >
> > > On Wed, Nov 23, 2022 at 01:47:04PM +0800, Jason Wang wrote:
> > > > On Wed, Nov 23, 2022 at 1:26 PM J
> On Nov 23, 2022, at 8:16 AM, Stefano Garzarella wrote:
>
> Commit 02b61f38d3 ("hw/virtio: incorporate backend features in features")
> properly negotiates VHOST_USER_F_PROTOCOL_FEATURES with the vhost-user
> backend, but we forgot to enable vrings as specified in
> docs/interop/vhost-user.rst
Hello,
On behalf of the QEMU Team, I'd like to announce the availability of the
third release candidate for the QEMU 7.2 release. This release is meant
for testing purposes and should not be used in a production environment.
http://download.qemu-project.org/qemu-7.2.0-rc2.tar.xz
http://downlo
On 23/11/22 19:49, Cédric Le Goater wrote:
On 11/23/22 19:13, Philippe Mathieu-Daudé wrote:
On 23/11/22 15:12, Alex Bennée wrote:
Thomas Huth writes:
On 23/11/2022 12.15, Philippe Mathieu-Daudé wrote:
On 18/11/22 12:33, Alex Bennée wrote:
The old URL wasn't stable. I suspect the current URL
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/7.2 for any
user-visible changes.
signature.asc
Description: PGP signature
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/7.2 for any
user-visible changes.
signature.asc
Description: PGP signature
Subject: [PATCH] cpu/i386: update xsave components after CPUID filtering
On i386 platform, CPUID data are setup through three consecutive steps: CPU
model definition, expansion and filtering.
XSAVE components are enabled during the expansion stage, by checking if they
are enabled in CPUID. Howev
axel/qemu.git tags/fixes-20221123-pull-request
>
> for you to fetch changes up to 7d3cf19548b7f9afd9d25c30dd1450aad7d1877d:
>
> hw/audio/intel-hda: Drop unnecessary prototype (2022-11-23 12:30:45 +0100)
>
> ---
On Wed, 23 Nov 2022 12:08:05 +
Marc Zyngier wrote:
> On Wed, 23 Nov 2022 01:42:36 +,
> chenxiang wrote:
> >
> > From: Xiang Chen
> >
> > Currently the number of MSI vectors comes from register PCI_MSI_FLAGS
> > which should be power-of-2 in qemu, in some scenaries it is not the same a
* Avihai Horon (avih...@nvidia.com) wrote:
> +ret = qemu_file_get_to_fd(f, migration->data_fd, data_size);
> +if (!ret) {
> +trace_vfio_load_state_device_data(vbasedev->name, data_size);
> +
> +}
I notice you had a few cases like that; I wouldn't bother making that
condition
On 11/23/22 19:13, Philippe Mathieu-Daudé wrote:
On 23/11/22 15:12, Alex Bennée wrote:
Thomas Huth writes:
On 23/11/2022 12.15, Philippe Mathieu-Daudé wrote:
On 18/11/22 12:33, Alex Bennée wrote:
The old URL wasn't stable. I suspect the current URL will only be
stable for a few months so may
* Avihai Horon (avih...@nvidia.com) wrote:
>
> On 08/11/2022 19:52, Vladimir Sementsov-Ogievskiy wrote:
> > External email: Use caution opening links or attachments
> >
> >
> > On 11/3/22 19:16, Avihai Horon wrote:
> > > From: Juan Quintela
> > >
> > > It was only used for RAM, and in that cas
Hi,
On 23/11/22 13:17, Mads Ynddal wrote:
From: Mads Ynddal
Continuing the refactor of a48e7d9e52 (gdbstub: move guest debug support
check to ops) by removing hardcoded kvm_enabled() from generic cpu.c
code, and replace it with a property of AccelOpsClass.
Signed-off-by: Mads Ynddal
---
ac
On 23/11/22 15:12, Alex Bennée wrote:
Thomas Huth writes:
On 23/11/2022 12.15, Philippe Mathieu-Daudé wrote:
On 18/11/22 12:33, Alex Bennée wrote:
The old URL wasn't stable. I suspect the current URL will only be
stable for a few months so maybe we need another strategy for hosting
rootfs sna
Am 23.11.2022 um 18:04 hat Paolo Bonzini geschrieben:
> On 11/23/22 14:45, Kevin Wolf wrote:
> > I think this means that if we clean up everything, in the end we'll have
> > coroutine_wrapper and coroutine_wrapper_bdrv (the fourth version not in
> > the above list, but that Paolo mentioned we may w
On Wed, Nov 23, 2022 at 05:27:34PM +, manish.mishra wrote:
> MSG_PEEK reads from the peek of channel, The data is treated as
> unread and the next read shall still return this data. This
> support is currently added only for socket class. Extra parameter
> 'flags' is added to io_readv calls to
BALATON Zoltan writes:
> On Wed, 23 Nov 2022, Markus Armbruster wrote:
>> Daniel P. Berrangé writes:
>>> On Wed, Nov 23, 2022 at 02:51:49PM +0100, BALATON Zoltan wrote:
On Wed, 23 Nov 2022, Markus Armbruster wrote:
> Signed-off-by: Markus Armbruster
> Reviewed-by: Laurent Vivier
>
On Tue, Nov 22, 2022, Chao Peng wrote:
> On Fri, Nov 18, 2022 at 03:59:12PM +, Sean Christopherson wrote:
> > On Fri, Nov 18, 2022, Alex Benn?e wrote:
> > > > We don't actually need a new bit, the opposite side of private is
> > > > shared, i.e. flags with KVM_MEMORY_EXIT_FLAG_PRIVATE cleared e
> > - -object
> > memory-backend-file,id=cxl-mem1,share=on,mem-path=/tmp/cxltest.raw,size=256M
> > \
> > - -object
> > memory-backend-file,id=cxl-lsa1,share=on,mem-path=/tmp/lsa.raw,size=256M \
> > + -object
> > memory-backend-file,pmem=true,id=pmem0,share=on,mem-path=/tmp/cxltest.raw,size=2
* Juan Quintela (quint...@redhat.com) wrote:
> Signed-off-by: Juan Quintela
Reviewed-by: Dr. David Alan Gilbert
> ---
> migration/migration.c | 24
> 1 file changed, 12 insertions(+), 12 deletions(-)
>
> diff --git a/migration/migration.c b/migration/migration.c
> ind
Current logic assumes that channel connections on the destination side are
always established in the same order as the source and the first one will
always be the main channel followed by the multifid or post-copy
preemption channel. This may not be always true, as even if a channel has a
connectio
MSG_PEEK reads from the peek of channel, The data is treated as
unread and the next read shall still return this data. This
support is currently added only for socket class. Extra parameter
'flags' is added to io_readv calls to pass extra read flags like
MSG_PEEK.
Reviewed-by: Daniel P. Berrangé
Current logic assumes that channel connections on the destination side are
always established in the same order as the source and the first one will
always be the main channel followed by the multifid or post-copy
preemption channel. This may not be always true, as even if a channel has a
connectio
Am 23.11.2022 um 12:42 hat Emanuele Giuseppe Esposito geschrieben:
> Extend the regex to cover also return type, pointers included.
> This implies that the value returned by the function cannot be
> a simple "int" anymore, but the custom return type.
> Therefore remove poll_state->ret and instead u
Am 23.11.2022 um 12:42 hat Emanuele Giuseppe Esposito geschrieben:
> Right now, we take the first parameter of the function to get the
> BlockDriverState to pass to bdrv_poll_co(), that internally calls
> functions that figure in which aiocontext the coroutine should run.
>
> However, it is useles
Am 23.11.2022 um 12:42 hat Emanuele Giuseppe Esposito geschrieben:
> This new annotation creates just a function wrapper that creates
> a new coroutine. It assumes the caller is not a coroutine.
>
> This is much better as g_c_w, because it is clear if the caller
> is a coroutine or not, and provid
On 11/23/22 14:45, Kevin Wolf wrote:
I think this means that if we clean up everything, in the end we'll have
coroutine_wrapper and coroutine_wrapper_bdrv (the fourth version not in
the above list, but that Paolo mentioned we may want to have).
Yes, I agree.
The only thing I'm unsure about is
Am 23.11.2022 um 12:42 hat Emanuele Giuseppe Esposito geschrieben:
> It is always called in coroutine_fn callbacks, therefore
> it can directly call bdrv_co_create().
>
> Rename it to bdrv_co_create_file too.
>
> Signed-off-by: Emanuele Giuseppe Esposito
Reviewed-by: Kevin Wolf
Am 23.11.2022 um 12:42 hat Emanuele Giuseppe Esposito geschrieben:
> Call two different functions depending on whether bdrv_create
> is in coroutine or not, following the same pattern as
> generated_co_wrapper functions.
>
> This allows to also call the coroutine function directly,
> without using
Am 23.11.2022 um 12:42 hat Emanuele Giuseppe Esposito geschrieben:
> This macro will be used to mark all coroutine_fn functions.
> Right now, it will be used for the newly introduced coroutine_fn, since
> we know the callers.
>
> As a TODO, in the future we might want to add this macro to all
> co
Am 23.11.2022 um 12:42 hat Emanuele Giuseppe Esposito geschrieben:
> We know that the string will stay around until the function
> returns, and the parameter of drv->bdrv_co_create_opts is const char*,
> so it must not be modified either.
>
> Suggested-by: Kevin Wolf
> Signed-off-by: Emanuele Giu
Am 23.11.2022 um 12:42 hat Emanuele Giuseppe Esposito geschrieben:
> Avoid mixing bdrv_* functions with blk_*, so create blk_* counterparts
> for bdrv_block_status_above and bdrv_is_allocated_above.
>
> Note that since bdrv_block_status_above only calls the g_c_w function
> bdrv_common_block_statu
* Juan Quintela (quint...@redhat.com) wrote:
> Until previous commit, save_live_pending() was used for ram. Now with
> the split into state_pending_estimate() and state_pending_exact() it
> is not needed anymore, so remove them.
>
> Signed-off-by: Juan Quintela
> ---
> include/migration/registe
Am 23.11.2022 um 12:42 hat Emanuele Giuseppe Esposito geschrieben:
> These functions end up calling bdrv_common_block_status_above(), a
> generated_co_wrapper function.
> In addition, they also happen to be always called in coroutine context,
> meaning all callers are coroutine_fn.
> This means tha
On 23/11/22 9:57 pm, Peter Xu wrote:
On Wed, Nov 23, 2022 at 09:28:14PM +0530, manish.mishra wrote:
On 23/11/22 9:22 pm, Peter Xu wrote:
On Wed, Nov 23, 2022 at 03:05:27PM +, manish.mishra wrote:
+int migration_channel_read_peek(QIOChannel *ioc,
+const cha
On Wed, 23 Nov 2022, Markus Armbruster wrote:
Daniel P. Berrangé writes:
On Wed, Nov 23, 2022 at 02:51:49PM +0100, BALATON Zoltan wrote:
On Wed, 23 Nov 2022, Markus Armbruster wrote:
Signed-off-by: Markus Armbruster
Reviewed-by: Laurent Vivier
---
v2:
* PATCH 1+2 merged as commit 0a553c12c7
Am 23.11.2022 um 12:42 hat Emanuele Giuseppe Esposito geschrieben:
> bdrv_common_block_status_above() is a g_c_w, and it is being called by
> many "wrapper" functions like bdrv_is_allocated(),
> bdrv_is_allocated_above() and bdrv_block_status_above().
>
> Because we want to eventually split the co
On Wed, Nov 23, 2022 at 09:28:14PM +0530, manish.mishra wrote:
>
> On 23/11/22 9:22 pm, Peter Xu wrote:
> > On Wed, Nov 23, 2022 at 03:05:27PM +, manish.mishra wrote:
> > > +int migration_channel_read_peek(QIOChannel *ioc,
> > > +const char *buf,
> > > +
Cool, thanks for posting an update.
An short introduction would be nice before diving into the details of ZBDs:
"This summer I worked on adding Zoned Block Device (ZBD) support to
virtio-blk as part of the https://www.outreachy.org/";>Outreachy internship program.
QEMU hasn't directly supported ZB
On 22/11/22 19:08, Philippe Mathieu-Daudé wrote:
From: Richard Henderson
Instead of requiring a separate hash table lookup,
put a pointer to the CIF into TCGHelperInfo.
Signed-off-by: Richard Henderson
Message-Id: <2022074101.2069454-27-richard.hender...@linaro.org>
[PMD: Split from bigge
On Wed, Nov 23, 2022 at 09:34:35PM +0530, manish.mishra wrote:
>
> On 23/11/22 9:28 pm, Daniel P. Berrangé wrote:
> > On Wed, Nov 23, 2022 at 03:05:27PM +, manish.mishra wrote:
> > > Current logic assumes that channel connections on the destination side are
> > > always established in the same
On Wed, Nov 23, 2022 at 04:03:49PM +, Alex Bennée wrote:
>
> "Michael S. Tsirkin" writes:
>
> > On Wed, Nov 23, 2022 at 03:21:32PM +, Alex Bennée wrote:
> >> Hi,
> >>
> >> This hopefully fixes the problems with VirtIO migration caused by the
> >> previous refactoring of virtio_device_st
On 23/11/22 9:28 pm, Daniel P. Berrangé wrote:
On Wed, Nov 23, 2022 at 03:05:27PM +, manish.mishra wrote:
Current logic assumes that channel connections on the destination side are
always established in the same order as the source and the first one will
always be the main channel followed
"Michael S. Tsirkin" writes:
> On Wed, Nov 23, 2022 at 03:21:32PM +, Alex Bennée wrote:
>> Hi,
>>
>> This hopefully fixes the problems with VirtIO migration caused by the
>> previous refactoring of virtio_device_started(). That introduced a
>> different order of checking which didn't give
On 23/11/22 9:22 pm, Peter Xu wrote:
On Wed, Nov 23, 2022 at 03:05:27PM +, manish.mishra wrote:
+int migration_channel_read_peek(QIOChannel *ioc,
+const char *buf,
+const size_t buflen,
+Error *
On Wed, Nov 23, 2022 at 03:05:27PM +, manish.mishra wrote:
> Current logic assumes that channel connections on the destination side are
> always established in the same order as the source and the first one will
> always be the main channel followed by the multifid or post-copy
> preemption cha
On Wed, Nov 23, 2022 at 03:05:27PM +, manish.mishra wrote:
> +int migration_channel_read_peek(QIOChannel *ioc,
> +const char *buf,
> +const size_t buflen,
> +Error **errp)
> +{
> + ssize_t len = 0;
On Wed, Nov 23, 2022 at 03:05:26PM +, manish.mishra wrote:
> MSG_PEEK reads from the peek of channel, The data is treated as
> unread and the next read shall still return this data. This
> support is currently added only for socket class. Extra parameter
> 'flags' is added to io_readv calls to
> 2022年11月22日 12:37，BALATON Zoltan 写道：
>
> Hello,
>
> On Mon, 21 Nov 2022, Bernhard Beschow wrote:
>> Am 21. November 2022 22:43:50 UTC schrieb "Philippe Mathieu-Daudé"
>> :
>>> On 21/11/22 16:34, Bernhard Beschow wrote:
Am 27. Oktober 2022 20:47:19 UTC schrieb "Philippe Mathieu-Daudé"
On Wed, Nov 23, 2022 at 03:21:32PM +, Alex Bennée wrote:
> Hi,
>
> This hopefully fixes the problems with VirtIO migration caused by the
> previous refactoring of virtio_device_started(). That introduced a
> different order of checking which didn't give the VM state primacy but
> wasn't notice
Thomas Huth 于2022年11月23日周三 20:48写道：
>
> On 17/11/2022 20.12, Stefan Hajnoczi wrote:
> > Hi Sam,
> > Please send a git repo URL so Thomas can fetch the commit without
> > email/file size limitations.
>
> The size obviously comes from the PNG image ... since this seems to be a
> photo, I think JPG w
We have a bunch of variables associated with the device and the vhost
backend which are used inconsistently throughout the code base. Lets
start trying to bring some order by agreeing what each variable is
for.
Signed-off-by: Alex Bennée
Cc: Stefano Garzarella
Cc: "Michael S. Tsirkin"
Cc: Stefa
The VM status should always preempt the device status for these
checks. This ensures the device is in the correct state when we
suspend the VM prior to migrations. This restores the checks to the
order they where in before the refactoring moved things around.
While we are at it lets improve our do
Hi,
This hopefully fixes the problems with VirtIO migration caused by the
previous refactoring of virtio_device_started(). That introduced a
different order of checking which didn't give the VM state primacy but
wasn't noticed as we don't properly exercise VirtIO device migration
and caused issues
> 2022年11月14日 16:25，Jiaxun Yang 写道：
>
> Value of C0_CMGCRBase will be reseted to default when cpu reset
> happens. In some cases software may move GCR base and then initiate
> a CPU reset, this will leave C0_CMGCRBase of reseted core incorrect.
>
> Implement a callback in CMGCR device to allo
Daniel P. Berrangé writes:
> On Wed, Nov 23, 2022 at 02:51:49PM +0100, BALATON Zoltan wrote:
>> On Wed, 23 Nov 2022, Markus Armbruster wrote:
>> > Signed-off-by: Markus Armbruster
>> > Reviewed-by: Laurent Vivier
>> > ---
>> > v2:
>> > * PATCH 1+2 merged as commit 0a553c12c7 and 3f7febc937
>> >
Current logic assumes that channel connections on the destination side are
always established in the same order as the source and the first one will
always be the main channel followed by the multifid or post-copy
preemption channel. This may not be always true, as even if a channel has a
connectio
Current logic assumes that channel connections on the destination side are
always established in the same order as the source and the first one will
always be the main channel followed by the multifid or post-copy
preemption channel. This may not be always true, as even if a channel has a
connectio
MSG_PEEK reads from the peek of channel, The data is treated as
unread and the next read shall still return this data. This
support is currently added only for socket class. Extra parameter
'flags' is added to io_readv calls to pass extra read flags like
MSG_PEEK.
Suggested-by: Daniel P. Berrangé
Hello, Richard,
We just noticed the gdb-stub is broken and probably caused by commit 4a3585568
("target/arm: Plumb debug into S1Translate").
(gdb) target remote :1234
Remote debugging using :1234
0x0e1716d0 in ?? ()
=> 0x0e1716d0: Cannot access memory at address 0xe1716d0
This is
First of all, Thanks for the hard work.
With QMP, I can backup dirty-bitmap - like 'blockdev-backup' incremental
sync mode.
But this command should be executed at the host where the QEMU process is
live.
I want to execute a backup at the other host so it does not affect running
Guest.
- `blockdev
From: Peter Maydell
Currently the intel-hda device has a reset method which manually
resets all the codecs by calling device_legacy_reset() on them. This
means they get reset twice, once because child devices on a qbus get
reset before the parent device's reset method is called, and then
again b
From: Peter Maydell
The only use of intel_hda_reset() is after its definition, so we
don't need to separately declare its prototype at the top of the
file; drop the unnecessary line.
Signed-off-by: Peter Maydell
Reviewed-by: Philippe Mathieu-Daudé
Message-Id: <20221014142632.2092404-3-peter.ma
From: Dongwon Kim
A warning, "qemu: warning: console: no gl-unblock within" followed by
guest scanout lockup can happen if dpy_gl_update is called in a row
and the second call is made before gd_draw_event scheduled by the first
call is taking place. This is because draw call returns without decre
From: Joelle van Dyne
Run state is also in RUN_STATE_PRELAUNCH while "-S" is used.
This reverts commit 0631d4b448454ae8a1ab091c447e3f71ab6e088a
Signed-off-by: Joelle van Dyne
Reviewed-by: Ján Tomko
The original commit broke the usage of usbredir with libvirt, which
starts every domain with "
From: Claudio Fontana
The GTK Clipboard implementation may cause guest hangs.
Therefore implement new configure switch: --enable-gtk-clipboard,
as a meson option disabled by default, which warns in the help
text about the experimental nature of the feature.
Regenerate the meson build options to
The following changes since commit 7c09a7f6ae1770d15535980d15dffdb23f4d9786:
Update VERSION for v7.2.0-rc2 (2022-11-22 18:59:56 -0500)
are available in the Git repository at:
https://gitlab.com/kraxel/qemu.git tags/fixes-20221123-pull-request
for you to fetch changes up to
From: Peter Maydell
Currently the hcd-xhci-pci and hcd-xhci-sysbus devices, which are
mostly wrappers around the TYPE_XHCI device, which is a direct
subclass of TYPE_DEVICE. Since TYPE_DEVICE devices are not on any
qbus and do not get automatically reset, the wrapper devices both
reset the TYPE_
From: Michael Tokarev
Fixes: effaf5a240e03020f4ae953e10b764622c3e87cc
Signed-off-by: Michael Tokarev
Reviewed-by: Thomas Huth
Reviewed-by: Stefan Weil
Message-Id: <20221105114851.306206-1-...@msgid.tls.msk.ru>
Signed-off-by: Gerd Hoffmann
---
hw/usb/hcd-xhci.c | 2 +-
1 file changed, 1 inser
> On 23 Nov 2022, at 15.05, Alex Bennée wrote:
>
> Nice. Looks good to me but I'll have a proper look when I go through my
> gdbstub/next queue. I don't think this is critical for 7.2.
>
Thanks, and I agree. It can easily wait.
Hi Stefan!
The following changes since commit 7c09a7f6ae1770d15535980d15dffdb23f4d9786:
Update VERSION for v7.2.0-rc2 (2022-11-22 18:59:56 -0500)
are available in the Git repository at:
https://gitlab.com/thuth/qemu.git tags/pull-request-2022-11-23
for you to fetch changes up to 4189af72d
The qemu-advent-calendar.org server will be decommissioned soon.
I've mirrored the images that we use for the QEMU CI to gitlab,
so update their URLs to point to the new location.
Message-Id: <20221121102436.78635-1-th...@redhat.com>
Tested-by: Philippe Mathieu-Daudé
Reviewed-by: Philippe Mathieu
The logs in the gitlab-CI have a size constraint, and sometimes
we already hit this limit. The biggest part of the log then seems
to be filled by the qom-test, so we should decrease the size of
the output - which can be done easily by not printing the path
for each property, since the path has alre
From: Alex Bennée
The old URL wasn't stable. I suspect the current URL will only be
stable for a few months so maybe we need another strategy for hosting
rootfs snapshots?
Signed-off-by: Alex Bennée
Message-Id: <20221118113309.1057790-1-alex.ben...@linaro.org>
Signed-off-by: Thomas Huth
---
t
On Tue, Nov 22, 2022 at 07:01:38PM +0100, Eugenio Perez Martin wrote:
On Tue, Nov 22, 2022 at 4:13 AM Jason Wang wrote:
On Mon, Nov 21, 2022 at 6:11 PM Stefano Garzarella wrote:
>
> Commit 69e1c14aa2 ("virtio: core: vq reset feature negotation support")
> enabled VIRTIO_F_RING_RESET by defaul
Thomas Huth writes:
> On 23/11/2022 12.15, Philippe Mathieu-Daudé wrote:
>> On 18/11/22 12:33, Alex Bennée wrote:
>>> The old URL wasn't stable. I suspect the current URL will only be
>>> stable for a few months so maybe we need another strategy for hosting
>>> rootfs snapshots?
>>>
>>> Signed-
On 23/11/2022 15.13, Marc-André Lureau wrote:
Hi Bin
On Fri, Oct 28, 2022 at 9:06 AM Bin Meng wrote:
Now that we have fixed various test case issues as seen when running
on Windows, let's enable the qtest build on Windows.
Signed-off-by: Bin Meng
Reviewed-by: Thomas Huth
We haven't solve
Hi Bin
On Fri, Oct 28, 2022 at 9:06 AM Bin Meng wrote:
>
> Now that we have fixed various test case issues as seen when running
> on Windows, let's enable the qtest build on Windows.
>
> Signed-off-by: Bin Meng
> Reviewed-by: Thomas Huth
We haven't solved the CI timing out or eating all the CP
On Wed, Nov 23, 2022 at 02:51:49PM +0100, BALATON Zoltan wrote:
> On Wed, 23 Nov 2022, Markus Armbruster wrote:
> > Signed-off-by: Markus Armbruster
> > Reviewed-by: Laurent Vivier
> > ---
> > v2:
> > * PATCH 1+2 merged as commit 0a553c12c7 and 3f7febc937
> > * PATCH 3 change to util/coroutine-uc
Mads Ynddal writes:
> From: Mads Ynddal
>
> Continuing the refactor of a48e7d9e52 (gdbstub: move guest debug support
> check to ops) by removing hardcoded kvm_enabled() from generic cpu.c
> code, and replace it with a property of AccelOpsClass.
>
> Signed-off-by: Mads Ynddal
Nice. Looks good
On Wed, 23 Nov 2022, Markus Armbruster wrote:
Signed-off-by: Markus Armbruster
Reviewed-by: Laurent Vivier
---
v2:
* PATCH 1+2 merged as commit 0a553c12c7 and 3f7febc937
* PATCH 3 change to util/coroutine-ucontext.c dropped [Laurent]
bsd-user/elfload.c | 2 +-
contrib/plugi
On Wed, Nov 23, 2022 at 02:01:32PM +0100, Eric Auger wrote:
>
>
> On 11/23/22 12:24, Michael S. Tsirkin wrote:
> > On Wed, Nov 23, 2022 at 12:10:09PM +0100, Eric Auger wrote:
> >>
> >> On 11/23/22 10:30, Michael S. Tsirkin wrote:
> >>> On Wed, Nov 23, 2022 at 09:18:39AM +0100, Eric Auger wrote:
>
Am 23.11.2022 um 12:45 hat Emanuele Giuseppe Esposito geschrieben:
>
>
> Am 18/11/2022 um 11:57 schrieb Paolo Bonzini:
> > On 11/16/22 15:07, Emanuele Giuseppe Esposito wrote:
> >> Here we introduce generated_co_wrapper_simple, a simplification of
> >> g_c_w that
> >> only considers the case wher
Signed-off-by: Markus Armbruster
Reviewed-by: Laurent Vivier
---
v2:
* PATCH 1+2 merged as commit 0a553c12c7 and 3f7febc937
* PATCH 3 change to util/coroutine-ucontext.c dropped [Laurent]
bsd-user/elfload.c | 2 +-
contrib/plugins/cache.c | 8
contr
1 - 100 of 152 matches
Mail list logo
