This series allows the memory_region_register_iommu_notifier()
to fail. As of now, when a MAP notifier is attempted to be
registered along with SMMUv3, Intel iommu without caching mode
or AMD IOMMU, we exit in the IOMMU MR notify_flag_changed()
callback. In case of VFIO assigned device hotplug, thi
From: "Dr. David Alan Gilbert"
This patch uses glib's g_auto mechanism to automatically free
rcu_read_lock's at the end of the block. Given that humans
have a habit of forgetting an error path somewhere it's
best to leave it to the compiler.
(Note I've found the actual cause of my deadlock act
On Wed, 4 Sep 2019 at 12:22, Alex Bennée wrote:
>
> Hi Peter,
>
> Here is version 2 of the ARM semi-hosting cleanup patches. The re-base
> had failed due to a change in the gen_exception_internal_insn API
> which now takes the PC instead of offset from pc_next. There is also
> the a minor indentat
Hi Peter,
Here is version 2 of the ARM semi-hosting cleanup patches. The re-base
had failed due to a change in the gen_exception_internal_insn API
which now takes the PC instead of offset from pc_next. There is also
the a minor indentation fix.
Alex Bennée (4):
target/arm: handle M-profile semi
Cover from Samuel Ortiz from (part 1) [1]:
This patchset allows for building and running ARM targets with TCG
disabled. [...]
The rationale behind this work comes from the NEMU project where we're
trying to only support x86 and ARM 64-bit architectures, without
including the TCG code ba
Am 02.09.2019 um 21:33 hat Max Reitz geschrieben:
> (v2 for “block: Let blockdev-create return 0 on success”)
>
> Jobs are expected to return 0 on success, so this extends to
> .bdrv_co_create(). After some inspection, it turns out that vpc is the
> only block driver that may return a positive va
(v2 for “block: Let blockdev-create return 0 on success”)
Jobs are expected to return 0 on success, so this extends to
.bdrv_co_create(). After some inspection, it turns out that vpc is the
only block driver that may return a positive value instead (to indicate
success). Fix that.
Without this
Patchew URL:
https://patchew.org/QEMU/20190821122315.18015-1-kbast...@mail.uni-paderborn.de/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Subject: [Qemu-devel] [PATCH v2 0/5] tricore: Convert to translate_loop (resend)
Message
Patchew URL:
https://patchew.org/QEMU/20190821122315.18015-1-kbast...@mail.uni-paderborn.de/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Subject: [Qemu-devel] [PATCH v2 0/5] tricore: Convert to translate_loop (resend)
Message
Patchew URL:
https://patchew.org/QEMU/20190821122315.18015-1-kbast...@mail.uni-paderborn.de/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Subject: [Qemu-devel] [PATCH v2 0/5] tricore: Convert to translate_loop (resend)
Message
(sorry about the noise, git-sendmail just quit with "Temporary local problem -
please try later" after sending two of the mails)
Hi,
I finally came around to port TriCore to the "new" translate_loop
infrastructure. This is necessary such that TriCore can be used in the upcoming
plugin API [1].
C
Hi,
I finally came around to port TriCore to the "new" translate_loop
infrastructure. This is necessary such that TriCore can be used in the upcoming
plugin API [1].
Cheers,
Bastian
[1] (https://lists.gnu.org/archive/html/qemu-devel/2019-06/msg03165.html)
v1 -> v2:
[03/05] Now also save hfl
Hi
In this v2:
- dropped the already included patches upstream
- dropped the semaphore changes
- add backlog listen parameter through all the call chain (danp suggestion)
- also add the change for qio_channel_socket_async(), for consistency
(it has zero users on tree anyways)
- for "fd" case, I
Currently, attaching zoned block devices (i.e. storage devices
compliant to ZAC/ZBC standards) using several virtio methods doesn't
work properly as zoned devices appear as regular block devices at the
guest. This may cause unexpected i/o errors and, potentially, some
data corruption.
To be more p
Patchew URL:
https://patchew.org/QEMU/20190709194330.837-1-marcandre.lur...@redhat.com/
Hi,
This series failed the asan build test. Please find the testing commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ===
#!/bin/ba
Hi,
podman allows to run containers in a similar fashion as docker, but
without daemon or root privileges. Thank you podman!
There is a weird issue with getaddrinfo(), that I reported upstream
https://github.com/containers/libpod/issues/3535. For now, it is
worked around with extra socket_check_p
Changes from v1:
* Fix whitespace error
* Fix cpu_lds*_code(), where cut-and-paste failed to extend the data.
Noticable with check-tcg with docker cross-compiler for cris-linux-user.
Blurb from v1:
While I could not replicate the failure Peter reported, the apparent
root cause -- the old
On 2019/6/10 上午12:44, Zhang Chen wrote:
From: Zhang Chen
Xen COLO based on KVM COLO architecture, it shared COLO proxy and block
replication with KVM COLO. The only differece is Xen COLO have own
COLO-frame to handle live migration related function, so we need this
series make Xen COLO frame
Hi,
These are some rather selfish iotests patches. The first patch helps me
personally because I tend to run the tests over SSH and forget to set
$DISPLAY. That makes test 139 skip the tests annotated with
skip_if_unsupprted(), because iotests.py can no longer determine the
list of whitelisted f
10, 2019 1:56 PM
> >> To: Jason Wang ; Li Zhijian
> >> ; Dr. David Alan Gilbert
> >> ; Juan Quintela ;
> >> zhanghailiang ; qemu-dev
> >> ; Stefano Stabellini ;
> >> Paul Durrant
> >> Cc: Zhang Chen
> >> Subject: Re: [Qemu-devel] [
Behalf Of Zhang, Chen
Sent: Monday, June 10, 2019 1:56 PM
To: Jason Wang ; Li Zhijian ;
Dr. David Alan Gilbert ; Juan Quintela
; zhanghailiang ;
qemu-dev ; Stefano Stabellini
; Paul Durrant
Cc: Zhang Chen
Subject: Re: [Qemu-devel] [PATCH V2 0/5] Add Xen COLO support
-Original Message-
From
David Alan Gilbert ; Juan Quintela
> ; zhanghailiang ;
> qemu-dev ; Stefano Stabellini
> ; Paul Durrant
> Cc: Zhang Chen
> Subject: Re: [Qemu-devel] [PATCH V2 0/5] Add Xen COLO support
>
>
>
> > -Original Message-
> > From: Jason Wang [mailto:jasow..
Patchew URL:
https://patchew.org/QEMU/20190619075643.10048-1-david.bren...@efs-auto.org/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Subject: [Qemu-devel] [PATCH v2 0/5] tricore: adding new instructions and
fixing issues
Type: series
Patchew URL:
https://patchew.org/QEMU/20190619075643.10048-1-david.bren...@efs-auto.org/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Subject: [Qemu-devel] [PATCH v2 0/5] tricore: adding new instructions and
fixing issues
Type: series
From: David Brenken
Hello everyone,
as discussed here is the second version of the patchset.
- We changed the implementation of the RRPW_INSERT to make use of
tcg_gen_deposit_tl.
- We added more information of the implementation of QSEED in the code
and changed parts of the implementation.
- We
> -Original Message-
> From: Jason Wang [mailto:jasow...@redhat.com]
> Sent: Monday, June 10, 2019 12:09 PM
> To: Zhang, Chen ; Li Zhijian ;
> Dr. David Alan Gilbert ; Juan Quintela
> ; zhanghailiang ;
> qemu-dev ; Stefano Stabellini
> ; Paul Durrant
> Cc: Zhang Chen
> Subject: Re: [PAT
On 2019/6/10 上午12:44, Zhang Chen wrote:
From: Zhang Chen
Xen COLO based on KVM COLO architecture, it shared COLO proxy and block
replication with KVM COLO. The only differece is Xen COLO have own
COLO-frame to handle live migration related function, so we need this
series make Xen COLO frame
From: Zhang Chen
Xen COLO based on KVM COLO architecture, it shared COLO proxy and block
replication with KVM COLO. The only differece is Xen COLO have own
COLO-frame to handle live migration related function, so we need this
series make Xen COLO frame can communicate with other COLO modules in
q
From: Xie Yongji
We introduced two flags "started" and "start_on_kick" to indicate virtio
device's state before. But there still are some problems with them. So
we try to fixup them in this patchset.
The patch 1 fixes a regression bug that old guest is not able to boot with
vhost-user-blk device
On Wed, 2019-04-17 at 22:53 +0300, Maxim Levitsky wrote:
> Hi!
> These are few assorted fixes and features for the userspace
> nvme driver.
>
> Tested that on my laptop with my Samsung X5 thunderbolt drive, which
> happens to have 4K sectors, support for discard and write zeros.
>
> Also bunch of
This is the third part of vector instruction support for s390x. It is based
on part 2, which is will send a pull-request for to Conny soon.
Part 1: Vector Support Instructions
Part 2: Vector Integer Instructions
Part 3: Vector String Instructions
Part 4: Vector Floating-Point Instructions
The cur
v2: codestyle fixes.
Gerd Hoffmann (5):
usb-hub: tweak feature names
usb-hub: make number of ports runtime-configurable
usb-hub: add helpers to update port state
usb-hub: add usb_hub_port_update()
usb-hub: emulate per port power switching
hw/usb/dev-hub.c | 221
This patch implement the QEMU part to retrieve ZPCI specific
information from the host.
The Linux part has been posted on a separate patch on the LKML.
Subject: [PATCH 0/4] Retrieving zPCI specific info with VFIO
Message-Id: <1557476555-20256-1-git-send-email-pmo...@linux.ibm.com>
We use the
Multi-chip packaging technology allows integration of multi-cores in one die
and multi-dies in one single package, for example Intel CLX-AP or AMD EPYC.
This kind of integration can be enabled by high-performance, heterogeneous,
multi-dies interconnect technology, providing a more cost-effective m
Philippe Mathieu-Daudé 于2019年5月21日周二 上午5:29写道：
> Hi Li,
>
> On 5/17/19 4:28 AM, Li Qiang wrote:
> > Ping.
> >
> > Li Qiang mailto:liq...@gmail.com>> 于2019年5月9日周四
> > 下午5:57写道：
> >
> > Ping this serials.
>
> I apologize I hold this series for too long.
> With your v1 I wanted to clarif
Hi Li,
On 5/17/19 4:28 AM, Li Qiang wrote:
> Ping.
>
> Li Qiang mailto:liq...@gmail.com>> 于2019年5月9日周四
> 下午5:57写道：
>
> Ping this serials.
I apologize I hold this series for too long.
With your v1 I wanted to clarify the commit descriptions without asking
you to send a v2, then I rew
Ping.
Li Qiang 于2019年5月9日周四 下午5:57写道：
> Ping this serials.
>
> Thanks,
> Li Qiang
>
> Li Qiang 于2019年4月24日周三 下午10:07写道：
>
>> In the disscuss of adding reboot timeout test case:
>> https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg03304.html
>>
>> Philippe suggested we should uses
Ping this serials.
Thanks,
Li Qiang
Li Qiang 于2019年4月24日周三 下午10:07写道：
> In the disscuss of adding reboot timeout test case:
> https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg03304.html
>
> Philippe suggested we should uses the only related option for one
> specific test. However cu
Currently, 233 cannot reliably run concurrently to other NBD TCP tests.
When it starts, it looks for a free port and then attempts to use that
for the whole duration of the test run. This is a TOCTTOU race
condition: It does not reserve that port, so another NBD TCP test that
runs in parallel can
Am 01.05.2019 um 20:13 hat Alberto Garcia geschrieben:
> Hi,
>
> this API only had a few users left so it can be easily removed.
Thanks, applied to the block branch.
Kevin
Hi,
this API only had a few users left so it can be easily removed.
Regards,
Berto
v2:
- Patch 2: Add QEMU_BUILD_BUG_ON(sizeof(VdiHeader) != 512) [Kevin]
Correct size parameter in bdrv_pwrite() call [Kevin]
Return 0 on success, never a positive number [Kevin]
- Patch 3: Ch
v2:
- Rewrite most patches based on the feedback from v1
Alistair Francis (5):
util/qemu-sockets: Fix GCC 9 build warnings
hw/usb/hcd-xhci: Fix GCC 9 build warning
hw/usb/dev-mtp: Fix GCC 9 build warning
linux-user/uname: Fix GCC 9 build warnings
linux-user/elfload: Fix GCC 9 build warn
Thomas Huth 于2019年4月29日周一 下午9:18写道：
> On 29/04/2019 07.09, Li Qiang wrote:
> >
> >
> > Li Qiang mailto:liq...@gmail.com>> 于2019年4月25日周
> > 四 下午10:29写道：
> >
> >
> >
> > Thomas Huth mailto:th...@redhat.com>> 于2019年4月
> > 25日周四 下午5:57写道：
> >
> > On 24/04/2019 16.06, Li Qiang wrote:
>
On 29/04/2019 07.09, Li Qiang wrote:
>
>
> Li Qiang mailto:liq...@gmail.com>> 于2019年4月25日周
> 四 下午10:29写道：
>
>
>
> Thomas Huth mailto:th...@redhat.com>> 于2019年4月
> 25日周四 下午5:57写道：
>
> On 24/04/2019 16.06, Li Qiang wrote:
> > In the disscuss of adding reboot timeout test
Li Qiang 于2019年4月25日周四 下午10:29写道：
>
>
> Thomas Huth 于2019年4月25日周四 下午5:57写道：
>
>> On 24/04/2019 16.06, Li Qiang wrote:
>> > In the disscuss of adding reboot timeout test case:
>> > https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg03304.html
>> >
>> > Philippe suggested we should uses the
Thomas Huth 于2019年4月25日周四 下午5:57写道：
> On 24/04/2019 16.06, Li Qiang wrote:
> > In the disscuss of adding reboot timeout test case:
> > https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg03304.html
> >
> > Philippe suggested we should uses the only related option for one
> > specific test. H
On 24/04/2019 16.06, Li Qiang wrote:
> In the disscuss of adding reboot timeout test case:
> https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg03304.html
>
> Philippe suggested we should uses the only related option for one
> specific test. However currently we uses one QTestState for all t
In the disscuss of adding reboot timeout test case:
https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg03304.html
Philippe suggested we should uses the only related option for one
specific test. However currently we uses one QTestState for all the
test cases. In order to achieve Philippe's i
From: Aleksandar Markovic
This is a collection of misc patches for kinux user that I recently
collected. Most of them originate from problems observed on target
mips. However, all of them actually fix problems on multiple
targets.
v1->v2:
- added the patch on setsockopt()'s option IPV6_ADD_ME
Hi!
These are few assorted fixes and features for the userspace
nvme driver.
Tested that on my laptop with my Samsung X5 thunderbolt drive, which
happens to have 4K sectors, support for discard and write zeros.
Also bunch of fixes sitting in my queue from the period when I developed
the nvme-mdev
This series addresses all the warnings I see when building on Fedora 30
x86_64 with GCC 9 (gcc-9.0.1-0.10.fc30.x86_64).
Changed in v2:
- Dropped patches mistakenly included due to not correctly rebasing
- Dropped s390x patches already merged
- Dropped usb-mtp patches which need much more work
v2:
* PATCH 1-4: Complete rewrite of fatally flawed PATCH v1 1/2 [Igor]
Markus Armbruster (5):
Revert "vl: Fix to create migration object before block backends
again"
Revert "migration: move only_migratable to MigrationState"
migration: Support adding migration blockers earlier
vl: Doc
On 28/03/19 17:00, Laurent Vivier wrote:
> This cleanup removes hardware objects from the list of files to be
> built for linux-user only targets.
>
> It also builds traces files only when the related file is built.
>
> Tested with all combinations of --{disable,enable}-{system,user,tools}
>
> v
This cleanup removes hardware objects from the list of files to be
built for linux-user only targets.
It also builds traces files only when the related file is built.
Tested with all combinations of --{disable,enable}-{system,user,tools}
v2:
- add CONFIG_TOOLS and CONFIG_BLOCK
- replace GENE
Hi,
This series contains Kconfig fixes to be able to run binaries
built using: './configure --without-default-devices' when using
the --nodefault option.
v2: Removed machines that run with --nodefault (Paolo)
v1: https://lists.gnu.org/archive/html/qemu-devel/2019-03/msg05366.html
Regards,
Phil.
On Wed, Mar 06, 2019 at 07:55:27PM +0800, Peter Xu wrote:
> v2:
> - add comment in patch 4
> - add another patch to comment why we need explicit aio_poll() in
> iothread_run loop
>
> When I first read the iothread code, the gcontext confused me for
> quite a while. Meanwhile, I've been tackling
On 05/03/19 20:55, Sven Schnelle wrote:
> Hi,
>
> this series contains a few cosmetic cleanups and one small bugfix for the
> LSI53C895 emulation.
>
> Regards
> Sven
>
> Sven Schnelle (5):
> lsi: use ldn_le_p()/stn_le_p()
> lsi: use enum type for s->waiting
> lsi: use enum type for s->msg_
v2:
- add comment in patch 4
- add another patch to comment why we need explicit aio_poll() in
iothread_run loop
When I first read the iothread code, the gcontext confused me for
quite a while. Meanwhile, I've been tackling with some races due to
this complexity as well. How much we'll pay for
Hi,
this series contains a few cosmetic cleanups and one small bugfix for the
LSI53C895 emulation.
Regards
Sven
Sven Schnelle (5):
lsi: use ldn_le_p()/stn_le_p()
lsi: use enum type for s->waiting
lsi: use enum type for s->msg_action
lsi: use SCSI phase names instead of numbers in trace
Hi,
I misidentified a bunch of individual contributors as academics in the
last series so I've fixed that now. I've also added Janus Technologies
for Marcus. If everyone is happy with these changes I'll send in the
PR.
The following patches need review
patch 0003/contrib gitdm add more individua
On Mon, Feb 11, 2019 at 04:03:57PM +, Dr. David Alan Gilbert wrote:
> * Yury Kotov (yury-ko...@yandex-team.ru) wrote:
> > Hi,
> >
> > The series adds a migration capability, which allows to skip shared RAM
> > blocks
> > during the migration. It's useful for fast local migration. E.g. to upda
* Yury Kotov (yury-ko...@yandex-team.ru) wrote:
> Hi,
>
> The series adds a migration capability, which allows to skip shared RAM blocks
> during the migration. It's useful for fast local migration. E.g. to update
> QEMU
> for the running guests.
>
> Usage example:
> 1. Start source VM:
>qem
Ping
04.02.2019, 16:27, "Yury Kotov" :
> Hi,
>
> The series adds a migration capability, which allows to skip shared RAM blocks
> during the migration. It's useful for fast local migration. E.g. to update
> QEMU
> for the running guests.
>
> Usage example:
> 1. Start source VM:
> qemu-system-x
Generic tcg now has support for folding of OR,
and has grown min/max primitives.
r~
Richard Henderson (5):
target/arm: Rely on optimization within tcg_gen_gvec_or
target/arm: Use vector minmax expanders for aarch64
target/arm: Use vector minmax expanders for aarch32
target/arm: Use tcg
Hi,
The series adds a migration capability, which allows to skip shared RAM blocks
during the migration. It's useful for fast local migration. E.g. to update QEMU
for the running guests.
Usage example:
1. Start source VM:
qemu-system-x86 \
-m 4G \
-object
memory-backend-file,id=mem0
On 02/01/19 23:24, Michael S. Tsirkin wrote:
> On Thu, Jan 31, 2019 at 03:23:50PM +0100, Laszlo Ersek wrote:
>> On 01/24/19 21:39, Laszlo Ersek wrote:
>>> Previous version (v1):
>>> http://mid.mail-archive.com/20190118223400.24311-1-lersek@redhat.com
>>>
>>> Updates in v2 have been noted on each pa
On Thu, Jan 31, 2019 at 03:23:50PM +0100, Laszlo Ersek wrote:
> On 01/24/19 21:39, Laszlo Ersek wrote:
> > Previous version (v1):
> > http://mid.mail-archive.com/20190118223400.24311-1-lersek@redhat.com
> >
> > Updates in v2 have been noted on each patch in the series.
>
> ping
Oh sorry I notice
On Thu, Jan 31, 2019 at 12:15:17PM -0500, Michael S. Tsirkin wrote:
> On Thu, Jan 31, 2019 at 04:19:09PM +0100, Stefano Garzarella wrote:
> > This series adds the support of DISCARD and WRITE ZEROES commands
> > and extends the virtio-blk-test to test WRITE_ZEROES command when
> > the feature is en
On Thu, Jan 31, 2019 at 04:19:09PM +0100, Stefano Garzarella wrote:
> This series adds the support of DISCARD and WRITE ZEROES commands
> and extends the virtio-blk-test to test WRITE_ZEROES command when
> the feature is enabled.
>
> v2:
> - added patch 1 to use virtio_blk_handle_rw_error() with d
This series adds the support of DISCARD and WRITE ZEROES commands
and extends the virtio-blk-test to test WRITE_ZEROES command when
the feature is enabled.
v2:
- added patch 1 to use virtio_blk_handle_rw_error() with discard operation
- added patch 2 to make those new features machine-type depende
On Thu, Jan 31, 2019 at 03:23:50PM +0100, Laszlo Ersek wrote:
> On 01/24/19 21:39, Laszlo Ersek wrote:
> > Previous version (v1):
> > http://mid.mail-archive.com/20190118223400.24311-1-lersek@redhat.com
> >
> > Updates in v2 have been noted on each patch in the series.
>
> ping
I'll queue this,
On 31/01/19 14:53, Thomas Huth wrote:
> Here's now my stab at expressing the ppc machine dependencies with
> Kconfig. I've carefully stepped through the dependencies and tried to
> built each machine separately (which should be possible now, apart
> from some few quirks like the RTAS dependency in
On 01/24/19 21:39, Laszlo Ersek wrote:
> Previous version (v1):
> http://mid.mail-archive.com/20190118223400.24311-1-lersek@redhat.com
>
> Updates in v2 have been noted on each patch in the series.
ping
>
> Cc: "Michael S. Tsirkin"
> Cc: Ard Biesheuvel
> Cc: Gerd Hoffmann
> Cc: Igor Mammedov
Here's now my stab at expressing the ppc machine dependencies with
Kconfig. I've carefully stepped through the dependencies and tried to
built each machine separately (which should be possible now, apart
from some few quirks like the RTAS dependency in qtest.c which I will
address later).
v2: Adre
Previous version (v1):
20190118223400.24311-1-lersek@redhat.com">http://mid.mail-archive.com/20190118223400.24311-1-lersek@redhat.com
Updates in v2 have been noted on each patch in the series.
Cc: "Michael S. Tsirkin"
Cc: Ard Biesheuvel
Cc: Gerd Hoffmann
Cc: Igor Mammedov
Cc: Philippe Mathieu
On Thu, 24 Jan 2019 at 13:38, Peter Maydell wrote:
>
> On Wed, 23 Jan 2019 at 21:23, Stefan Hajnoczi wrote:
> >
> > v2:
> > * Add Patch 2 to call memory_region_flush_rom_device() from pflash devices
> >[Peter]
> >
> > This series adds the Non-Volatile Memory Controller, which controls access
On Wed, 23 Jan 2019 at 21:23, Stefan Hajnoczi wrote:
>
> v2:
> * Add Patch 2 to call memory_region_flush_rom_device() from pflash devices
>[Peter]
>
> This series adds the Non-Volatile Memory Controller, which controls access to
> the User Information Control Registers (UICR), Factory Informa
v2:
* Add Patch 2 to call memory_region_flush_rom_device() from pflash devices
[Peter]
This series adds the Non-Volatile Memory Controller, which controls access to
the User Information Control Registers (UICR), Factory Information Control
Registers (FICR), and flash memory.
This is the last
[This is the Linux kernel part, git tree is available at
https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/vfio-ccw.git
vfio-ccw-eagain-caps
The companion QEMU patches are available at
https://github.com/cohuck/qemu vfio-ccw-caps]
Currently, vfio-ccw only relays START SUBCHANNEL requests t
vhost does not have to be supported only if KVM is present, in fact
vhost-user does not even need any kind of kernel support. This series
changes this. The rationale is that, when vhost-user-test.c will be
converted to qgraph, it will be able to test vhost-user support
for virtio-mmio backend eve
Patchew URL:
https://patchew.org/QEMU/1546883690-17798-1-git-send-email-venu.busire...@oracle.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Subject: [Qemu-devel] [PATCH v2 0/5] Support for datapath switching during live
migration
Implement the infrastructure to support datapath switching during live
migration involving SR-IOV devices.
1. This patch is based off on the current VIRTIO_NET_F_STANDBY feature
bit and MAC address device pairing.
2. This set of events will be consumed by userspace management software
to or
From: Aleksandar Markovic
Clean up several misc issues in nanoMIPS disassembler. There are
more issues to be cleaned, and this is meant to be just the first
phase. Complete cleanup should happen over the course of next
few months.
v1->v2:
- patch 5 was somehow lost in v1, now should be fine.
Hi all.
v2:
05: fix compilation of test-crypto-block (I am ashamed:(
and change QCryptoBlock interface to be a bit more safe.
These series are preliminary step before moving encryption code in
qcow2 to the threads. The first attempt of doing it is on list
([PATCH 00/11] qcow2: encryption thre
Long long ago, linux kernel have supported up to 4G initrd, but it's header
still hard code to allow loading initrd below 2G only.
cutting from arch/x86/head.S:
# (Header version 0x0203 or later) the highest safe address for the contents
# of an initrd. The current kernel allows up to 4 GB, but
On 12/11/18 04:07, Xiao Guangrong wrote:
>
> Hi,
>
> Ping...
Hi Guangrong, I think this isn't being reviewed because we're in freeze.
Paolo
> On 11/6/18 8:20 PM, guangrong.x...@gmail.com wrote:
>> From: Xiao Guangrong
>>
>> Changelog in v2:
>> These changes are based on Paolo's suggestion:
>>
Hi,
Ping...
On 11/6/18 8:20 PM, guangrong.x...@gmail.com wrote:
From: Xiao Guangrong
Changelog in v2:
These changes are based on Paolo's suggestion:
1) rename the lockless multithreads model to threaded workqueue
2) hugely improve the internal design, that make all the request be
a larg
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20181106122025.3487-1-xiaoguangr...@tencent.com
Subject: [Qemu-devel] [PATCH v2 0/5] migration: improve multithreads
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=base
n=1
From: Xiao Guangrong
Changelog in v2:
These changes are based on Paolo's suggestion:
1) rename the lockless multithreads model to threaded workqueue
2) hugely improve the internal design, that make all the request be
a large array, properly partition it, assign requests to threads
respectiv
On 05.11.18 15:18, Kevin Wolf wrote:
> Am 19.10.2018 um 18:49 hat Max Reitz geschrieben:
>> I noticed that with the (more or less) recent series from Marc-André the
>> output of qemu-img amend -f qcow2 -o help changed to this:
>>
>> $ ./qemu-img amend -f qcow2 -o help
>> Creation options for 'qcow2
Am 19.10.2018 um 18:49 hat Max Reitz geschrieben:
> I noticed that with the (more or less) recent series from Marc-André the
> output of qemu-img amend -f qcow2 -o help changed to this:
>
> $ ./qemu-img amend -f qcow2 -o help
> Creation options for 'qcow2':
> qcow2-create-opts.backing_file=str - F
On Sun, Nov 04, 2018 at 11:25:00AM +, Marc Zyngier wrote:
> diff --git a/arch/arm64/kvm/sys_regs.c b/arch/arm64/kvm/sys_regs.c
> index 22fbbdbece3c..d50f912d3f4a 100644
> --- a/arch/arm64/kvm/sys_regs.c
> +++ b/arch/arm64/kvm/sys_regs.c
> @@ -314,10 +314,15 @@ static bool trap_raz_wi(struct kvm
Ping. I don't quite want the help output to change in 3.1 only to
change it to something else in 3.2.
(And at some point into freeze we have to consider just merging one of
the many simple 082 reference output "fixes", which I really don't want,
because I still consider the test "broken for a rea
Hi Richard,
On Sun, 04 Nov 2018 09:50:29 +,
Richard Henderson wrote:
>
> On 11/3/18 12:32 PM, Marc Zyngier wrote:
> > We actively hide the LORegion feature from the guest since
> > cc33c4e20185a391766ed5e78e2acc97e17ba511 (in the 4.17 time frame), so
> > you shouldn't be able to obtain these
On 11/3/18 12:32 PM, Marc Zyngier wrote:
> We actively hide the LORegion feature from the guest since
> cc33c4e20185a391766ed5e78e2acc97e17ba511 (in the 4.17 time frame), so
> you shouldn't be able to obtain these on a recent host.
I don't think that patch is ideal.
In particular, LOR is a mandat
On Sat, 3 Nov 2018 09:53:44 +
Richard Henderson wrote:
Hi Richard,
> Although, while I have you, Christopher, is there a way to extract the Limited
> Ordering Region registers without modifying guest state? Those are
> multiplexed
> with LORN_EL1.
We actively hide the LORegion feature fro
On 11/2/18 7:35 PM, Christoffer Dall wrote:
>> It looks like the kernel can handle reads of ID_ISAR0_EL1
>> through ID_ISAR5_EL1, but not ID_ISAR6_EL1, any of the
>> MVFR*_EL1 or ID_AA64_ISAR* or ID_AA64PFR*.
>>
>> This is probably because the kernel is way too old to be
>> interestingly supportabl
On Fri, Nov 02, 2018 at 04:36:35PM +, Peter Maydell wrote:
> On 2 November 2018 at 14:54, Richard Henderson
> wrote:
> > My previous patch set for replacing feature bits with id registers
> > failed to consider that these id registers are beginning to control
> > migration, and thus we must fi
On 2 November 2018 at 14:54, Richard Henderson
wrote:
> My previous patch set for replacing feature bits with id registers
> failed to consider that these id registers are beginning to control
> migration, and thus we must fill them in for KVM as well.
>
> Thus, we want to initialize these values
My previous patch set for replacing feature bits with id registers
failed to consider that these id registers are beginning to control
migration, and thus we must fill them in for KVM as well.
Thus, we want to initialize these values within CPU from the host.
Finally, re-send the T32EE conversion
1 - 100 of 724 matches
Mail list logo
