Command to enable shadow virtqueue looks like:
{ "execute": "x-vhost-enable-shadow-vq", "arguments": { "name": "dev0",
"enable": true } }
Signed-off-by: Eugenio Pérez
---
qapi/net.json | 22 ++
hw/virtio/vhost.c | 6 ++
2 files changed, 28 insertions(+)
diff
Since all the shadow virtqueue device is done in software, we can avoid
the write syscall.
Signed-off-by: Eugenio Pérez
---
hw/virtio/vhost-shadow-virtqueue.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/hw/virtio/vhost-shadow-virtqueue.c
Vhost shadow virtqueue (SVQ)is an intermediate jump for virtqueue
notifications and buffers, allowing qemu to track them. While qemu is
forwarding the buffers and virtqueue changes, is able to commit the
memory it's being dirtied, the same way regular qemu's VirtIO devices
do.
This commit only
It will be used to configure shadow virtqueue. Shadow virtqueue will
relay the device->guest notifications, so vhost need to be able to tell
the masking status.
Signed-off-by: Eugenio Pérez
---
include/hw/virtio/vhost.h | 1 +
hw/virtio/vhost.c | 2 ++
2 files changed, 3 insertions(+)
This method is already present in vhost-user. This commit adapts it to
vhost-net, so SVQ can use.
vhost_kernel_set_enable stops the device, so qemu can ask for its status
(next available idx the device was going to consume). When SVQ starts it
can resume consuming the guest's driver ring, without
Shadow virtqueue notifications forwarding is disabled when vhost_dev
stops, so code flow follows usual cleanup.
Signed-off-by: Eugenio Pérez
---
hw/virtio/vhost-shadow-virtqueue.h | 7 ++
include/hw/virtio/vhost.h | 4 +
hw/virtio/vhost-shadow-virtqueue.c | 113
This allows shadow virtqueue code to assert the queue status before
making changes.
Signed-off-by: Eugenio Pérez
---
include/hw/virtio/virtio.h | 1 +
hw/virtio/virtio.c | 5 +
2 files changed, 6 insertions(+)
diff --git a/include/hw/virtio/virtio.h b/include/hw/virtio/virtio.h
This series enable shadow virtqueue for vhost-net devices. This is a
new method of vhost devices migration: Instead of relay on vhost
device's dirty logging capability, SW assisted LM intercepts dataplane,
forwarding the descriptors between VM and device. Is intended for vDPA
devices with no
On 3/14/21 10:55 PM, Taylor Simpson wrote:
Signed-of-by: Taylor Simpson
---
target/hexagon/op_helper.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Queued.
r~
15.03.2021 09:06, Roman Kagan wrote:
The reconnection logic doesn't need to stop while in a drained section.
Moreover it has to be active during the drained section, as the requests
that were caught in-flight with the connection to the server broken can
only usefully get drained if the
On 3/14/21 10:54 PM, Taylor Simpson wrote:
Address feedback from Richard Henderson <
Signed-off-by: Taylor Simpson
---
target/hexagon/decode.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Queued.
r~
On 3/14/21 10:53 PM, Taylor Simpson wrote:
Address feedback from Richard Henderson <
Signed-off-by: Taylor Simpson
---
target/hexagon/iclass.c | 4
1 file changed, 4 deletions(-)
Queued.
r~
On 3/14/21 10:53 PM, Taylor Simpson wrote:
Change cpu_ldl_code to translator_ldl
Don't end the TB after every packet when HEX_DEBUG is on
Make gen_check_store_width a simple call
Address feedback from Richard Henderson <
Signed-off-by: Taylor Simpson
---
target/hexagon/translate.c | 26
The CONFIG_VFIO switch only works in target specific code. Since
migration/migration.c is common code, the #ifdef does not have
the intended behavior here. Move the related code to a separate
file now which gets compiled via specific_ss instead.
Fixes: 3710586caa ("qapi: Add VFIO devices
>
> are available in the Git repository at:
>
> https://github.com/philmd/qemu.git tags/avr-20210315
>
> for you to fetch changes up to 56b90e60c4019b08012bd8bd1459efc00b055577:
>
> target/avr: Fix inte
On 3/15/21 6:39 PM, Paolo Bonzini wrote:
> The main advantage of 0.57 is that it fixes
> https://github.com/mesonbuild/meson/pull/7900, thus avoiding unnecessary
> rebuilds after running meson.
>
> Signed-off-by: Paolo Bonzini
> ---
> meson | 2 +-
> 1 file changed, 1 insertion(+), 1
at:
https://gitlab.com/rth7680/qemu.git tags/pull-misc-20210315
for you to fetch changes up to 7625a1ed013a042748753750c9d9b1a33c9cd8e0:
utils: Use fixed-point arithmetic in qemu_strtosz (2021-03-15 12:47:08 -0600)
Fix qemu_strtosz
Hi
On Mon, Mar 15, 2021 at 9:22 PM Li Zhang wrote:
> From: Li Zhang
>
> When executing the QMP commands "chardev-change" to change the
> backend device to socket, it will cause a segment fault because
> it assumes chr->label as non-NULL in function yank_register_instance.
> The function
On Mar 14 19:31, Dmitry Fomichev wrote:
> LGTM,
> Reviewed-by: Dmitry Fomichev
>
Thanks Dmitry!
If you could give [10/13], [11/13] and [12/13] a look-see as well that
would be awesome :)
-
k
signature.asc
Description: PGP signature
-20210315
for you to fetch changes up to 7625a1ed013a042748753750c9d9b1a33c9cd8e0:
utils: Use fixed-point arithmetic in qemu_strtosz (2021-03-15 12:47:08 -0600)
Fix qemu_strtosz testsuite failures for i686
Because this bit was not in hflags, the privilege check
for tlb instructions was essentially random.
Recompute hflags when storing to LPCR.
Signed-off-by: Richard Henderson
---
target/ppc/cpu.h | 1 +
target/ppc/helper_regs.c | 3 +++
target/ppc/mmu-hash64.c | 3 +++
Signed-off-by: Richard Henderson
---
hw/ppc/spapr_rtas.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/hw/ppc/spapr_rtas.c b/hw/ppc/spapr_rtas.c
index 8a79f9c628..6ec3e71757 100644
--- a/hw/ppc/spapr_rtas.c
+++ b/hw/ppc/spapr_rtas.c
@@ -51,6 +51,7 @@
#include "target/ppc/mmu-hash64.h"
On 3/15/21 1:51 PM, Richard Henderson wrote:
> Once we've parsed the fractional value, extract it into an integral
> 64-bit fraction. Perform the scaling with integer arithmetic, and
> simplify the overflow detection.
>
> Reviewed-by: Eric Blake
> Message-Id:
Perform the test against FSCR_SCV at runtime, in the helper.
This means we can remove the incorrect set against SCV in
ppc_tr_init_disas_context and do not need to add an HFLAGS bit.
Signed-off-by: Richard Henderson
---
target/ppc/helper.h | 1 +
target/ppc/excp_helper.c | 9 +
We weren't recording MSR_GS in hflags, which means that BookE
memory accesses were essentially random vs Guest State.
Instead of adding this bit directly, record the completed mmu
indexes instead. This makes it obvious that we are recording
exactly the information that we need.
This also means
Copying flags directly from msr has drawbacks: (1) msr bits
mean different things per cpu, (2) msr has 64 bits on 64 cpus
while tb->flags has only 32 bits.
Create a enum to define these bits. Document the origin of each bit.
This fixes the truncation of env->hflags to tb->flags, because we no
Once we've parsed the fractional value, extract it into an integral
64-bit fraction. Perform the scaling with integer arithmetic, and
simplify the overflow detection.
Reviewed-by: Eric Blake
Message-Id: <20210315155835.1970210-2-richard.hender...@linaro.org>
Signed-off-by: Richard Henderson
Because these bits were not in hflags, the code generated
for single-stepping on BookE was essentially random.
Recompute hflags when storing to dbcr0.
Signed-off-by: Richard Henderson
---
target/ppc/helper_regs.c | 20 +++-
target/ppc/misc_helper.c | 3 +++
As per hreg_compute_hflags:
We 'forget' FE0 & FE1: we'll never generate imprecise exceptions
remove the hflags marker from the respective comments.
Signed-off-by: Richard Henderson
---
target/ppc/cpu.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/target/ppc/cpu.h
-20210315
for you to fetch changes up to 7625a1ed013a042748753750c9d9b1a33c9cd8e0:
utils: Use fixed-point arithmetic in qemu_strtosz (2021-03-15 12:47:08 -0600)
Fix qemu_strtosz testsuite failures for i686
It will be stored in tb->flags, which is also uint32_t,
so let's use the correct size.
Signed-off-by: Richard Henderson
---
target/ppc/cpu.h | 4 ++--
target/ppc/misc_helper.c | 2 +-
target/ppc/translate.c | 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git
We have eliminated all normal uses of hflags_nmsr. We need
not even compute it except when we want to migrate. Rename
the field to emphasize this.
Remove the fixme comment for migrating access_type. This value
is only ever used with the current executing instruction, and
is never live when the
In save_user_regs, there are two bugs where we OR in a bit number
instead of the bit, clobbering the low bits of MSR. However:
The MSR_VR and MSR_SPE bits control the availability of the insns.
If the bits were not already set in MSR, then any attempt to access
those registers would result in
In ppc_store_msr we call hreg_compute_hflags, which itself
calls hreg_compute_mem_idx. Rely on ppc_store_msr to update
everything required by the msr update.
Signed-off-by: Richard Henderson
---
target/ppc/machine.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git
Signed-off-by: Richard Henderson
---
hw/ppc/pnv_core.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/hw/ppc/pnv_core.c b/hw/ppc/pnv_core.c
index bd2bf2e044..8c2a15a0fb 100644
--- a/hw/ppc/pnv_core.c
+++ b/hw/ppc/pnv_core.c
@@ -29,6 +29,7 @@
#include "hw/ppc/pnv_xscom.h"
Verify that hflags was updated correctly whenever we change
cpu state that is used by hflags.
Signed-off-by: Richard Henderson
---
target/ppc/cpu.h | 5 +
target/ppc/helper_regs.c | 29 +++--
2 files changed, 32 insertions(+), 2 deletions(-)
diff --git
Move the functions to a new file, helper_regs.c.
Note int_helper.c was relying on helper_regs.h to
indirectly include qemu/log.h.
Signed-off-by: Richard Henderson
---
target/ppc/helper_regs.h | 184 ++--
target/ppc/helper_regs.c | 197
Nothing within the translator -- or anywhere else for that
matter -- checks MSR_SA or MSR_AP on the 602. This may be
a mistake. However, for the moment, we need not record these
bits in hflags.
This allows us to simplify HFLAGS_VSX computation by moving
it to overlap with MSR_VSX.
On 3/15/21 12:34 PM, Rebecca Cran wrote:
On 3/10/21 12:24 PM, Richard Henderson wrote:
On 3/9/21 6:29 PM, Rebecca Cran wrote:
+void tlb_flush_page_range_by_mmuidx(CPUState *cpu, target_ulong addr,
+ unsigned int num_pages, uint16_t idxmap)
I am not keen on
Changes for v4:
* Use hregs_recompute_hflags for hw/ppc/ reset.
-- Incorporate Cedric's feedback.
Changes for v3:
* Fixes for linux-user, signal handling and startup.
-- Oops, the directory in which I did testing for v2
had a reduced set of targets.
Changes for v2:
* Do not put
Match cpu_post_load in using ppc_store_msr to set all of
the cpu state implied by the value of msr. Do not restore
hflags or hflags_nmsr, as we recompute them in ppc_store_msr.
Signed-off-by: Richard Henderson
---
target/ppc/machine.c | 13 +++--
1 file changed, 11 insertions(+), 2
Keep all hflags computation in one place, as this will be
especially important later.
Introduce a new POWERPC_FLAG_HID0_LE bit to indicate when
LE should be taken from HID0. This appears to be set if
and only if POWERPC_FLAG_RTC_CLK is set, but we're not
short of bits and having both names will
From: Philippe Mathieu-Daudé
This test fails when QEMU is built without the megasas device,
restrict it to its availability.
Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by: Thomas Huth
---
MAINTAINERS | 1 +
tests/qtest/fuzz-megasas-test.c | 49
The generic-fuzzer often provides randomized DMA addresses to
virtual-devices. For a 64-bit address-space, the chance of these
randomized addresses coinciding with RAM regions, is fairly small. Even
though the fuzzer's instrumentation eventually finds valid addresses,
this can take some-time, and
For testing, it can be useful to simulate an enormous amount of memory
(e.g. 2^64 RAM). This adds an MMIO device that acts as sparse memory.
When something writes a nonzero value to a sparse-mem address, we
allocate a block of memory. For now, since the only user of this device
is the fuzzer, we
/20210315-pull-request
for you to fetch changes up to fc7c6fae7e36d2aa19b66dea5f9663cebeefb504:
fuzz: move some DMA hooks (2021-03-15 12:49:28 -0400)
Pull request
* Add new and fix existing generic-fuzz configs
* Add
From: Philippe Mathieu-Daudé
When we started to commit the fuzzer QTest reproducers to
fuzz-test.c in commit d8dd1095019 ("qtest: add fuzz test case"),
we forgot to add the corresponding MAINTAINERS entry. Do it now.
Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by: Thomas Huth
---
For the sparse-mem device, we want the fuzzer to populate entire DMA
reads from sparse-mem, rather than hooking into the individual MMIO
memory_region_dispatch_read operations. Otherwise, the fuzzer will treat
each sequential read separately (and populate it with a separate
pattern). Work around
Signed-off-by: Alexander Bulekov
Reviewed-by: Darren Kenny
---
tests/qtest/fuzz/generic_fuzz_configs.h | 6 ++
1 file changed, 6 insertions(+)
diff --git a/tests/qtest/fuzz/generic_fuzz_configs.h
b/tests/qtest/fuzz/generic_fuzz_configs.h
index 2454c627ff..8b8c7ac553 100644
---
From: Philippe Mathieu-Daudé
This test fails when QEMU is built without the virtio-scsi device,
restrict it to its availability.
Reviewed-by: Michael S. Tsirkin
Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by: Thomas Huth
---
MAINTAINERS | 1 +
I noticed that with a sufficiently small timeout, the fuzzer fork-server
sometimes locks up. On closer inspection, the issue appeared to be
caused by entering our SIGALRM handler, while libfuzzer is in it's crash
handlers. Because libfuzzer relies on pipe communication with an
external child
Currently, bash and C crash reproducers are be built manually. This is a
problem, as we want to integrate reproducers into the tree, for
regression testing. This patch adds a script that converts a sequence of
QTest commands into a pasteable Bash reproducer, or a libqtest-based C
program. This
Patchew URL:
https://patchew.org/QEMU/20210315180102.3008391-1-imamm...@redhat.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20210315180102.3008391-1-imamm...@redhat.com
Subject: [PATCH 0/6] pc: support user
We have several scripts that help build reproducers, but no
documentation for how they should be used. Add some documentation
Signed-off-by: Alexander Bulekov
Reviewed-by: Darren Kenny
---
docs/devel/fuzzing.rst | 45 ++
1 file changed, 45 insertions(+)
On 3/15/21 12:45 PM, Daniel P. Berrangé wrote:
> This has been hardcoded to "false" since 2.10.0, since secrets required
> to unlock block devices are now always provided upfront instead of using
up front
> interactive prompts.
>
> Reviewed-by: Thomas Huth
> Signed-off-by: Daniel P. Berrangé
Aaron Lindsay writes:
> On Mar 12 17:28, Alex Bennée wrote:
>> Signed-off-by: Alex Bennée
>
> One nit below, but otherwise:
>
> Reviewed-by: Aaron Lindsay
>
>> ---
>> include/qemu/qemu-plugin.h | 25 ++---
>> 1 file changed, 22 insertions(+), 3 deletions(-)
>>
>> diff
On 3/15/21 12:45 PM, Daniel P. Berrangé wrote:
> The code comment suggests removing QAPIEvent_(str|lookup) symbols too,
> however, these are both auto-generated as standard for any enum in
> QAPI. As such it they'll exist whether we use them or not.
>
> Reviewed-by: Thomas Huth
> Signed-off-by:
On Mon, Mar 15, 2021 at 05:54:17PM +, Alex Bennée wrote:
>
> Daniel P. Berrangé writes:
>
> > On Mon, Mar 15, 2021 at 06:04:10PM +0100, Thomas Huth wrote:
> >> On 15/03/2021 17.57, Peter Maydell wrote:
> >> > On Mon, 15 Mar 2021 at 16:53, Alex Bennée wrote:
> >> > > -Prefer g_new(T, n)
The device-type names for the pro100 network cards, are i8255.. We were
matching "eepro", which catches the PCI PIO/MMIO regions for those
devices, however misses the actual PCI device, which we use to map the
BARs, before fuzzing. Fix that
Signed-off-by: Alexander Bulekov
Reviewed-by: Philippe
On 3/10/21 12:24 PM, Richard Henderson wrote:
On 3/9/21 6:29 PM, Rebecca Cran wrote:
+void tlb_flush_page_range_by_mmuidx(CPUState *cpu, target_ulong addr,
+ unsigned int num_pages, uint16_t
idxmap)
I am not keen on this interface. I think you should take
Some BSD platforms do not have this header.
Reviewed-by: Peter Maydell
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: Joelle van Dyne
---
meson.build | 1 +
block.c | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/meson.build b/meson.build
index
On 3/15/21 12:58 PM, Claudio Fontana wrote:
> Hello Eric,
>
> I am seeing some test failures after todays' rebase on latest master for the
> "cross-i386-user", while on Friday it was ok:
>
> https://gitlab.com/hw-claudio/qemu/-/jobs/1098390932
>
> Running test test-cutils
> **
>
On 3/15/21 8:54 AM, Thomas Huth wrote:
> We are generating a lot of target-specific defines in the *-config-devices.h
> and *-config-target.h files. Using them in common code is wrong and leads
> to very subtle bugs since a "#ifdef CONFIG_SOMETHING" is not working there
> as expected. To avoid
Pure code motion, no functional change.
Signed-off-by: Gerd Hoffmann
Message-Id: <20210312090425.772900-4-kra...@redhat.com>
---
hw/usb/dev-storage-classic.c | 156 +++
hw/usb/dev-storage.c | 135 --
hw/usb/meson.build
On 3/15/21 8:18 AM, Richard Henderson wrote:
> On 3/15/21 5:33 AM, Eric Blake wrote:
>> On 3/13/21 3:48 PM, Richard Henderson wrote:
>>> On 3/11/21 2:07 PM, Eric Blake wrote:
+ /*
+ * Add in a fudge-factor (2^53 when double is IEEE format) for
+ * all scales
From: Thomas Huth
There are some more -usbdevice options that have never been mentioned
in the documentation. Now that we removed -usbdevice from the list
of deprecated features again, we should document them properly.
While we're at it, also sort them alphabetically.
Signed-off-by: Thomas
On Mon, Mar 15, 2021 at 09:16:06PM +0800, Zihao Chang wrote:
> This series supports reload x509 certificates for vnc
> 1. Support reload x509 certificates.
> 2. Support reload vnc certificates.
> 3. Add new qmp display-reload and implement reload x509 certificates
> for vnc.
>
> Example:
>
These patches disables code that cannot be compiled or run on iOS by adding
feature/header detection at configure time.
Only the first patch still needs to be reviewed, thanks!
v3:
* Add braces in if statement in third patch
v2:
* Broken merge where config_host['CONFIG_SMBD_COMMAND'] was
From: Thomas Huth
This property was only required for the pc-1.0 and earlier machine
types. Since these have been removed now, we can delete the property
as well.
Signed-off-by: Thomas Huth
Message-Id: <20210302120152.118042-1-th...@redhat.com>
Signed-off-by: Gerd Hoffmann
---
Replace Windows specific macro with a more generic feature detection
macro. Allows slirp smb feature to be disabled manually as well.
Acked-by: Samuel Thibault
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: Joelle van Dyne
---
configure | 26 +++---
meson.build | 2
From: Paolo Bonzini
No device needs them anymore and in fact they're undocumented.
Remove the code. The only change in behavior is that "-usbdevice
braille:hello" now reports an error, which is a bugfix.
Signed-off-by: Paolo Bonzini
Cc: Gerd Hoffmann
Signed-off-by: Thomas Huth
Message-Id:
Pure code motion, no functional change.
Signed-off-by: Gerd Hoffmann
Message-Id: <20210312090425.772900-3-kra...@redhat.com>
---
hw/usb/dev-storage-bot.c | 63
hw/usb/dev-storage.c | 42 ---
hw/usb/meson.build | 1 +
3
iOS hosts do not have these defined so we fallback to the
default behaviour.
Co-authored-by: Warner Losh
Reviewed-by: Peter Maydell
Signed-off-by: Joelle van Dyne
---
block/file-posix.c | 21 +
1 file changed, 9 insertions(+), 12 deletions(-)
diff --git
it will be used by follow up patches
Signed-off-by: Igor Mammedov
---
include/hw/acpi/aml-build.h | 3 +++
hw/acpi/aml-build.c | 28
2 files changed, 31 insertions(+)
diff --git a/include/hw/acpi/aml-build.h b/include/hw/acpi/aml-build.h
index
In preparation for splitting the usb-storage.c file move
declarations to the new usb/msd.h header file.
Signed-off-by: Gerd Hoffmann
Message-Id: <20210312090425.772900-2-kra...@redhat.com>
---
include/hw/usb/msd.h | 54
hw/usb/dev-storage.c | 48
Stale data in csw (specifically residue) can confuse the state machine
and allows the guest trigger an assert(). So clear csw on reset to
avoid this happening in case the guest resets the device in the middle
of a request.
Buglink: https://bugs.launchpad.net/qemu/+bug/1523811
Signed-off-by: Gerd
On Darwin (iOS), there are no system level APIs for directly accessing
host block devices. We detect this at configure time.
Signed-off-by: Joelle van Dyne
---
meson.build | 6 +-
qapi/block-core.json | 10 +++---
block/file-posix.c | 33 ++---
3
Signed-off-by: Igor Mammedov
---
tests/qtest/bios-tables-test-allowed-diff.h | 11 +++
1 file changed, 11 insertions(+)
diff --git a/tests/qtest/bios-tables-test-allowed-diff.h
b/tests/qtest/bios-tables-test-allowed-diff.h
index dfb8523c8b..fddcfc061f 100644
---
From: Philippe Mathieu-Daudé
The VT82C686 south bridge provides a USB UHCI bus via a PCI function.
Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by: BALATON Zoltan
Message-Id: <20210309190802.830969-2-f4...@amsat.org>
Signed-off-by: Gerd Hoffmann
---
hw/isa/Kconfig | 1 +
1 file changed, 1
From: Paolo Bonzini
It never worked.
Signed-off-by: Paolo Bonzini
Cc: Gerd Hoffmann
Signed-off-by: Thomas Huth
Message-Id: <20210310173323.1422754-3-th...@redhat.com>
Signed-off-by: Gerd Hoffmann
---
hw/usb/u2f.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/hw/usb/u2f.c
Add new kconfig symbols so usb-storage and usb-bot can
be enabled or disabled individually at build time.
Signed-off-by: Gerd Hoffmann
Message-Id: <20210312090425.772900-5-kra...@redhat.com>
---
hw/usb/Kconfig | 13 -
hw/usb/meson.build | 4 ++--
2 files changed, 14
In x86/ACPI world, linux distros are using predictable
network interface naming since systemd v197. Which on
QEMU based VMs results into path based naming scheme,
that names network interfaces based on PCI topology.
With itm on has to plug NIC in exactly the same bus/slot,
which was used when
From: Thomas Huth
When trying to remove the -usbdevice option, there were complaints that
"-usbdevice braille" is still a very useful shortcut for some people.
Thus we never remove this option. Since it's not such a big burden to
keep it around, and it's also convenient in the sense that you
The following changes since commit 6157b0e19721aadb4c7fdcfe57b2924af6144b14:
Merge remote-tracking branch 'remotes/vivier2/tags/linux-user-for-6.0-pull-=
request' into staging (2021-03-14 17:47:49 +)
are available in the Git repository at:
git://git.kraxel.org/qemu tags/usb-20210315
From: Philippe Mathieu-Daudé
Extract the VT82C686 PCI UHCI function into a new unit so
it is only build when the VT82C686 south bridge is selected.
Signed-off-by: Philippe Mathieu-Daudé
Message-Id: <20210309190802.830969-4-f4...@amsat.org>
Signed-off-by: Gerd Hoffmann
---
hw/usb/hcd-uhci.c
On Mon, Mar 15, 2021 at 11:06:30AM +0100, Greg Kurz wrote:
> On Sun, 14 Mar 2021 19:36:04 -0400
> Vivek Goyal wrote:
>
> > On Fri, Mar 12, 2021 at 03:10:03PM +0100, Greg Kurz wrote:
> > > POSIX.1-2017 clearly stipulates that empty filenames aren't
> > > allowed ([1] and [2]). Since virtiofsd is
* Dr. David Alan Gilbert (dgilb...@redhat.com) wrote:
> * Mahmoud Mandour (ma.mando...@gmail.com) wrote:
> > Replaced various qemu_mutex_lock calls and their respective
> > qemu_mutex_unlock calls with QEMU_LOCK_GUARD macro. This simplifies
> > the code by eliminating the respective
Philippe Mathieu-Daudé writes:
> On 3/15/21 5:59 PM, Christian Borntraeger wrote:
>> On 15.03.21 17:51, Philippe Mathieu-Daudé wrote:
>>
>>> diff --git a/hw/core/Kconfig b/hw/core/Kconfig
>>> index fdf03514d7d..9397503656d 100644
>>> --- a/hw/core/Kconfig
>>> +++ b/hw/core/Kconfig
>>> @@
From: Philippe Mathieu-Daudé
Extract generic UHCI prototypes into a new "hcd-uhci.h" local
header so we can reuse them in other units.
Signed-off-by: Philippe Mathieu-Daudé
Message-Id: <20210309190802.830969-3-f4...@amsat.org>
Signed-off-by: Gerd Hoffmann
---
hw/usb/hcd-uhci.h | 93
The 'host_device' and 'host_cdrom' drivers must be used instead.
Reviewed-by: Eric Blake
Signed-off-by: Daniel P. Berrangé
---
block/file-posix.c | 17 ++---
docs/system/deprecated.rst | 7 ---
docs/system/removed-features.rst | 7 +++
it helps to avoid device naming conflicts when guest OS is
configured to use acpi-index for naming.
Spec ialso says so:
PCI Firmware Specification Revision 3.2
4.6.7. _DSM for Naming a PCI or PCI Express Device Under Operating Systems
"
Instance number must be unique under \_SB scope. This
expected changes are:
* larger BNMR operation region
* new PIDX field and method to fetch acpi-index
* PDSM method that implements PCI device _DSM +
per device _DSM that calls PDSM
@@ -221,10 +221,11 @@ DefinitionBlock ("", "DSDT", 1, "BOCHS ", "BXPC",
0x0001)
B0EJ,
Implement _DSM according to:
PCI Firmware Specification 3.1
4.6.7. DSM for Naming a PCI or PCI Express Device Under
Operating Systems
and wire it up to cold and hot-plugged PCI devices.
Feature depends on ACPI hotplug being enabled (as that provides
PCI devices descriptions in
The same data is available in the 'BlockDeviceInfo' struct.
Reviewed-by: Vladimir Sementsov-Ogievskiy
Signed-off-by: Daniel P. Berrangé
---
block/qapi.c| 5 -
docs/system/deprecated.rst | 13 -
Changes since rfc:
* make sure that acpi-index unique
* use dedicated MMIO register for it
* drop syntetic acpi-label field in _DSM
* add more comments
Series implements support for 'onboard' naming scheme for network
interfaces (1), which is based on PCI firmware spec and lets user
to
Hello Eric,
I am seeing some test failures after todays' rebase on latest master for the
"cross-i386-user", while on Friday it was ok:
https://gitlab.com/hw-claudio/qemu/-/jobs/1098390932
Running test test-cutils
**
ERROR:../tests/unit/test-cutils.c:2290:test_qemu_strtosz_metric: assertion
Daniel P. Berrangé writes:
> On Mon, Mar 15, 2021 at 06:04:10PM +0100, Thomas Huth wrote:
>> On 15/03/2021 17.57, Peter Maydell wrote:
>> > On Mon, 15 Mar 2021 at 16:53, Alex Bennée wrote:
>> > > -Prefer g_new(T, n) instead of g_malloc(sizeof(T) ``*`` n) for the
>> > > following
>> > > +Care
Mahmoud Mandour writes:
> Given this is start-up code I think you could use g_new instead of
> g_try_new. As it will abort on no memory you can avoid the early return
> check bellow. Also is elf_phdata never persists beyond this function you
> could use g_autofree (and use g_steal_pointer
On 3/11/21 5:11 PM, Philippe Mathieu-Daudé wrote:
> Introduce the 'query-accels' QMP command which returns a list
> of built-in accelerators names.
accelerator names
>
> - Accelerator is an QAPI enum of all existing accelerators,
is a QAPI enum
>
> - AcceleratorInfo is a QAPI structure
The same information is available via the 'recording' and 'busy' fields.
Reviewed-by: Vladimir Sementsov-Ogievskiy
Signed-off-by: Daniel P. Berrangé
---
block/dirty-bitmap.c | 38
docs/system/deprecated.rst | 7 -
docs/system/removed-features.rst | 7 +
101 - 200 of 505 matches
Mail list logo
