16.09.2019 16:26, Max Reitz wrote:
> On 13.09.19 10:58, Max Reitz wrote:
>> On 16.08.19 17:30, Vladimir Sementsov-Ogievskiy wrote:
>>> Hi all!
>>>
>>> Here is an asynchronous scheme for handling fragmented qcow2
>>> reads and writes. Both qcow2 read and write functions loops through
>>> sequential
On 13.09.19 10:58, Max Reitz wrote:
> On 16.08.19 17:30, Vladimir Sementsov-Ogievskiy wrote:
>> Hi all!
>>
>> Here is an asynchronous scheme for handling fragmented qcow2
>> reads and writes. Both qcow2 read and write functions loops through
>> sequential portions of data. The series aim it to para
13.09.2019 11:58, Max Reitz wrote:
> On 16.08.19 17:30, Vladimir Sementsov-Ogievskiy wrote:
>> Hi all!
>>
>> Here is an asynchronous scheme for handling fragmented qcow2
>> reads and writes. Both qcow2 read and write functions loops through
>> sequential portions of data. The series aim it to paral
On 16.08.19 17:30, Vladimir Sementsov-Ogievskiy wrote:
> Hi all!
>
> Here is an asynchronous scheme for handling fragmented qcow2
> reads and writes. Both qcow2 read and write functions loops through
> sequential portions of data. The series aim it to parallelize these
> loops iterations.
> It imp
Pinging, as Stefan's branch merged into master and now these series based on
master.
16.08.2019 18:30, Vladimir Sementsov-Ogievskiy wrote:
> Hi all!
>
> Here is an asynchronous scheme for handling fragmented qcow2
> reads and writes. Both qcow2 read and write functions loops through
> sequential
On Thu, 22 Aug 2019 at 18:24, Eric Auger wrote:
>
> As of today when a guest is assigned with a host PCI device and
> an SMMUv3, VFIO calls memory_region_iommu_replay() default
> implementation. This translates the whole address range and
> completely stalls the execution. As VFIO/SMMUv3 integrati
As of today when a guest is assigned with a host PCI device and
an SMMUv3, VFIO calls memory_region_iommu_replay() default
implementation. This translates the whole address range and
completely stalls the execution. As VFIO/SMMUv3 integration
is not supported yet (it requires SMMUv3 HW nested pagin
Hi all!
Here is an asynchronous scheme for handling fragmented qcow2
reads and writes. Both qcow2 read and write functions loops through
sequential portions of data. The series aim it to parallelize these
loops iterations.
It improves performance for fragmented qcow2 images, I've tested it
as desc
Patchew URL: https://patchew.org/QEMU/20190716024726.17864-1-npig...@gmail.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Subject: [Qemu-devel] [PATCH v4 0/5] spapr: implement dispatch and suspend calls
Message-id: 20190716024726.17864-1
This series follows on from the previous that added H_PROD and
H_CONFER, but I've now aimed to make it conform better to PAPR.
It's still not completely there (as explained in comments), but
it's better than before and actually better matches KVM that
does implement the prod bit and dispatch count
On Wed, 26 Jun 2019 at 18:43, Laurent Vivier wrote:
>
> On 26/06/2019 04:31, elohi...@gmail.com wrote:
> > From: Xie Yongji
>
> Could you use the same address to send the series?
> Or may be you need to add a Signed-off-by with your name and this address?
>
> I don't know what is the rule when so
This is v4 of a proposed patch set for fixing file ID collisions with 9pfs.
v3->v4:
* Rebased to latest git master head.
* Splitted Antonios' patch set to its original 4 individual patches.
(was merged previously as only 1 patch).
* Addressed discussed issues directly on Antonios' pat
On 26/06/2019 04:31, elohi...@gmail.com wrote:
> From: Xie Yongji
Could you use the same address to send the series?
Or may be you need to add a Signed-off-by with your name and this address?
I don't know what is the rule when someone send a patch with a different
address than the author one but
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 introduces a "use-started" property to avoid a migration
issue under Greg Kurz's sug
From: Aleksandar Markovic
This series contains various improvements and additions of MSA ASE
TCG tests.
v3->v4:
- patches 1 and 2 from v3 got reviewed and integrated into upstream,
so they are now removed in v4
- added tests for MSA int multiply instructions
- added support for MSA bi
* Jason Wang (jasow...@redhat.com) wrote:
>
> On 2019/6/13 下午5:59, Dr. David Alan Gilbert (git) wrote:
> > From: "Dr. David Alan Gilbert"
> >
> > Laine asked for some extra features on the network announce support;
>
>
> It's better to explain why this feature is needed.
Yes, I'll reword.
>
On 2019/6/13 下午5:59, Dr. David Alan Gilbert (git) wrote:
From: "Dr. David Alan Gilbert"
Laine asked for some extra features on the network announce support;
It's better to explain why this feature is needed. Is this because
libvirt can change the host network topology on the fly?
Thank
From: "Dr. David Alan Gilbert"
Laine asked for some extra features on the network announce support;
The first allows the announce timer to announce on a subset of the
interfaces.
The second allows there to be multiple timers, each with their own
parameters (including the interface list).
Signe
c2077e2c "pci: Adjust PCI config limit based on bus topology"
introduced checking the availability of extended config space for
PCI-E devices which are in a bus topology that doesn't permit extended
config space access (e.g. under PCI-E to PCI then PCI to PCI-E
bridges).
This caused some problems
From: Aleksandar Markovic
This is a collection of misc patches for Linux user that I recently
accumulated from variuous sources. All of them originate from problems
observed on mips target. However, these changes actually affect and fix
problems on multiple targets.
v3->v4:
- improved commit
This patch series has implementation for "virtio pmem".
"virtio pmem" is fake persistent memory(nvdimm) in guest
which allows to bypass the guest page cache. This also
implements a VIRTIO based asynchronous flush mechanism.
Sharing guest kernel driver in this patchset with the
changes
From: Mateja Marjanovic
Fix support for MSA instructions while executing QEMU on a
machine that uses big endian MIPS CPU. This is achieved by
changing the implementation of helpers for MSA instructions
ST., LD., INSERT. (and D on MIPS64),
COPY_S. (and D on MIPS64) and COPY_U. (and W
on MIPS64). I
ping
10.01.2019 18:28, Vladimir Sementsov-Ogievskiy wrote:
> ping
>
> 14.12.2018 16:42, Vladimir Sementsov-Ogievskiy wrote:
>> Hi all!
>>
>> These series are derived from "[PATCH v3 0/8] qcow2 check improvements"
>> (https://lists.gnu.org/archive/html/qemu-devel/2018-10/msg02284.html)
>>
>> Some
This is the 4th version of the patch set. Updated as per the review
from Alistair, it has the riscv_csrrw_debug function added, and
Reviewed-By lines added. Otherwise it is the same as the 3rd version.
Jim
This patch series is based on "[PATCH v3 0/4] QEMU changes to do PVH boot" and
provides a PVH option rom that can be used with SeaBIOS to boot uncompressed
kernel using the x86/HVM direct boot ABI.
Patches 1 and 2 are to prepare the PVH option rom, moving common functions in
the new headers. Patc
ping
14.12.2018 16:42, Vladimir Sementsov-Ogievskiy wrote:
> Hi all!
>
> These series are derived from "[PATCH v3 0/8] qcow2 check improvements"
> (https://lists.gnu.org/archive/html/qemu-devel/2018-10/msg02284.html)
>
> Some patches are new, some patches are not included and are postponed to
>
On 1/2/19 4:21 PM, no-re...@patchew.org wrote:
> Patchew URL:
> https://patchew.org/QEMU/20181228173356.15359-1-phi...@redhat.com/
[...]> === OUTPUT BEGIN ===
> Checking PATCH 1/5: qemu/compiler: Define QEMU_NONSTRING...
> WARNING: architecture specific defines should be avoided
> #53: FILE: inclu
Patchew URL: https://patchew.org/QEMU/20181228173356.15359-1-phi...@redhat.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20181228173356.15359-1-phi...@redhat.com
Subject: [Qemu-devel] [PATCH v4 0/5] Fix strncpy
GCC 8 new warning prevents builds to success since quite some time.
First report on the mailing list is in July 2018:
https://lists.gnu.org/archive/html/qemu-devel/2018-07/msg03723.html
Since v3:
- patch 1: make sens of description (eblake)
- patch 2: append QEMU_NONSTRING instead of prepending it
Add testing to test the bitmap-merge API.
V4:
- Removed patches 1-5 which have been staged
- Rewrite qmp_log entirely, split into three patches
- Pretty-printing has been extended to log() as well as qmp_log()
- Adjust iotest 236 to be format generic instead of qcow2 [Vladimir]
- Adjust iotes
Hi all!
These series are derived from "[PATCH v3 0/8] qcow2 check improvements"
(https://lists.gnu.org/archive/html/qemu-devel/2018-10/msg02284.html)
Some patches are new, some patches are not included and are postponed to
part II.
So, here:
01,03 - unchanged
02: handle broken iotest
04-05: new
Patchew URL: https://patchew.org/QEMU/20181207115343.6747-1-kw...@redhat.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 20181207115343.6747-1-kw...@redhat.com
Subject: [Qemu-devel] [PATCH v4 0/5] vmdk: Implement blockdev
I picked up the patch series from Fam and rebased it to current master
(which involved a major rework on the test case) and tried to address
Markus' review comments for v2. I did not do any further review of the
actual code, but it passes the tests, so I guess having it in tree is
better than conti
Dear all,
The given feature discards blocks with copy-on-read operation while the
streaming process runs. Adding the 'discard' argument to the QMP block-stream
command allows dropping a block in the backing chain after it has been copied
to the active layer. That will elude the block duplication i
The first patches are simple cleanups:
- patch 1 move the pvpanic device with the 'ocmmon objects' so we compile
it once for the x86/arm/aarch64 archs,
- patch 2 simply renames ISA fields/definitions to generic ones.
Then instead of add/use the MMIO pvpanic device in the virt machine in an
uniqu
This series makes the qcow2 L2 cache assignment aware of the image size,
with the intention for it to cover the entire image. The importance of
this change is in noticeable performance improvement, especially with
heavy random I/O. The memory overhead is not big in most cases, as only
1 MB of cache
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 1530781798-183214-1-git-send-email-robert...@linux.intel.com
Subject: [Qemu-devel] [PATCH v4 0/5] Add Icelake CPU model
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=base
n=1
This patch set defines the new guest CPU models of Icelake.
The first patch defines new indices for IA32_PRED_CMD MSR (IBPB) and
IA32_ARCH_CAPABILITIES MSR.
Other patches add CPUID bits feature words for new features, like PCONFIG,
WBNOINVD. The final patch defines Icelake-{Server,Client} CPU mod
Based on a patch by Martin Schrodt.
v4: rebase to latest master, move enable-by-default to separate patch.
v3: rebase to latest master, solve compat.h conflict.
v2: drop underrun detection, handle overruns only.
Gerd Hoffmann (5):
audio/hda: create millisecond timers that handle IO
audio/hda:
Hi,
The following patches implement the TPM Physical Presence Interface
that allows a user to set a command via ACPI (sysfs entry in Linux)
that, upon the next reboot, the firmware looks for and acts upon by
sending sequences of commands to the TPM.
A dedicated memory region is added to the TPM C
On Wed, May 30, 2018 at 02:41:51PM -0400, Cleber Rosa wrote:
> TL;DR
> =
>
> Another version, with a minimalist approach, of the acceptance tests
> infrastructure for QEMU, based on the Avocado Testing Framework.
Queued on python-next. Thank you very much, and sorry for taking
so long to que
On Tue, Jun 05, 2018 at 11:49:07AM -0300, Philippe Mathieu-Daudé wrote:
> Hi Eduardo,
>
> On 05/30/2018 03:41 PM, Cleber Rosa wrote:
> > TL;DR
> > =
> >
> > Another version, with a minimalist approach, of the acceptance tests
> > infrastructure for QEMU, based on the Avocado Testing Framework
Hi Eduardo,
On 05/30/2018 03:41 PM, Cleber Rosa wrote:
> TL;DR
> =
>
> Another version, with a minimalist approach, of the acceptance tests
> infrastructure for QEMU, based on the Avocado Testing Framework.
What do you think of this series?
Are you OK to take it via your tree, or should it
TL;DR
=
Another version, with a minimalist approach, of the acceptance tests
infrastructure for QEMU, based on the Avocado Testing Framework.
Background
==
The previous version, still considered an RFC, sent to the list by
Eduardo[1] was based on the work held in Amador's branch[2].
Hello,
This adds support for the Hash Page Table MMU mode on POWER9 PowerNV
machines. The Radix Tree mode support for the host is still to be done
but we are getting close.
Thanks,
C.
Changes since v3:
- removed spapr_hpt_base() ops
- split hash MMU definitions patch
Cédric Le Goater (5):
On Sun, 22 Apr 2018 12:17:22 -0400
Tony Krowiak wrote:
> On 04/19/2018 07:51 AM, Cornelia Huck wrote:
> > On Sun, 15 Apr 2018 15:07:19 -0400
> > Tony Krowiak wrote:
> >
> >> default-configs/s390x-softmmu.mak |1 +
> >> docs/vfio-ap.txt | 649
> >> +
On 04/19/2018 07:51 AM, Cornelia Huck wrote:
On Sun, 15 Apr 2018 15:07:19 -0400
Tony Krowiak wrote:
default-configs/s390x-softmmu.mak |1 +
docs/vfio-ap.txt | 649 +
hw/s390x/Makefile.objs|1 +
hw/s390x/ap-device.c
On Sun, 15 Apr 2018 15:07:19 -0400
Tony Krowiak wrote:
> default-configs/s390x-softmmu.mak |1 +
> docs/vfio-ap.txt | 649
> +
> hw/s390x/Makefile.objs|1 +
> hw/s390x/ap-device.c | 39 +++
> hw/vfio/Makefi
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 1523819244-29954-1-git-send-email-akrow...@linux.vnet.ibm.com
Subject: [Qemu-devel] [PATCH v4 0/5] s390x: vfio-ap: guest dedicated crypto
adapters
=== TEST SCRIPT BEGIN
This patch series is the QEMU counterpart to the KVM/kernel support for
guest dedicated crypto adapters. The KVM/kernel model is built on the
VFIO mediated device framework and provides the infrastructure for
granting exclusive guest access to crypto devices installed on the linux
host. This pa
Tested-by: Kash Pande
signature.asc
Description: OpenPGP digital signature
This series enables the TOPOEXT feature for AMD CPUs. This is required to
support hyperthreading on kvm guests.
This addresses the issues reported in these bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1481253
https://bugs.launchpad.net/qemu/+bug/1703506
v4:
1.Removed the checks under cpuid
On 03/08/18 10:33 +0800, Haozhong Zhang wrote:
> (Patch 5 is only for reviewers to run test cases in patch 4)
>
> ACPI 6.2A Table 5-129 "SPA Range Structure" requires the proximity
> domain of a NVDIMM SPA range must match with corresponding entry in
> SRAT table.
>
> The address ranges of vNVDIM
(Patch 5 is only for reviewers to run test cases in patch 4)
ACPI 6.2A Table 5-129 "SPA Range Structure" requires the proximity
domain of a NVDIMM SPA range must match with corresponding entry in
SRAT table.
The address ranges of vNVDIMM in QEMU are allocated from the
hot-pluggable address space,
On 3 March 2018 at 14:38, Richard Henderson
wrote:
> Changes since v3:
> * Review comments applied.
> * Frame allocation generalized in patch 5; hopefully this
> eliminates some of the confusion seen during review.
>
> Changes since v2:
> * 5 patches merged,
> * The PR_SVE_SET/GET_VL p
Changes since v3:
* Review comments applied.
* Frame allocation generalized in patch 5; hopefully this
eliminates some of the confusion seen during review.
Changes since v2:
* 5 patches merged,
* The PR_SVE_SET/GET_VL patch is more specifically user-only.
* Split the signal frame pat
In v4:
- patch 2 has even more wording tweaks [Kevin]
- patch 3 is new [Berto]
- patch 5 fixes an off-by-one [Berto]
Eric Blake (5):
qcow2: Prefer byte-based calls into bs->file
qcow2: Document some maximum size constraints
qcow2: Reduce REFT_OFFSET_MASK
qcow2: Don't allow overflow during
v4:
4/5: Remove getumask and set default permissions to 0644
5/5: Remove usb_mtp_object_lookup_name out of #ifdef CONFIG_INOTIFY1
Test compilation on freebsd
v3:
3/5: Add a property that sets r/w to on/off (default:off)
Restructure ifdefs
4/5: Sort the response codes
5/5: Use ac
Queued on machine-next, thanks!
--
Eduardo
v4:
- drop not needed leftover from previous impl. hunk in arm
CPU_RESOLVING_TYPE patch
- squash CPU_RESOLVING_TYPE patches into one
- move test cases from CPU_RESOLVING_TYPE patches into test patch
- silence microblaze(el) test waring as its cpu doesn't work
with 'none' machine
-
On Fri, Feb 2, 2018 at 6:01 AM, wrote:
> === OUTPUT BEGIN ===
> Checking PATCH 1/5: test-coroutine: add simple CoMutex test...
> ERROR: do not initialise statics to 0 or NULL
> #30: FILE: tests/test-coroutine.c:198:
> +static bool locked = false;
>
> total: 1 errors, 0 warnings, 74 lines checked
On Thu, Jan 11, 2018 at 4:58 AM, Eduardo Habkost wrote:
> On Thu, Jan 11, 2018 at 11:25:08AM +0100, Igor Mammedov wrote:
>> On Wed, 10 Jan 2018 19:48:00 -0200
>> Eduardo Habkost wrote:
>>
>> > On Wed, Jan 10, 2018 at 01:30:29PM -0800, Alistair Francis wrote:
>> > > On Thu, Dec 28, 2017 at 6:59 AM
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20180201212917.18131-1-pbonz...@redhat.com
Subject: [Qemu-devel] [PATCH v4 0/5] coroutine-lock: polymorphic CoQueue
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=base
n=1
There are cases in which a queued coroutine must be restarted from
non-coroutine context (with qemu_co_enter_next). In this cases,
qemu_co_enter_next also needs to be thread-safe, but it cannot use a
CoMutex and so cannot qemu_co_queue_wait. This happens in curl (which
right now is rolling its ow
This series fixes alignment issues, cleans up a bit the TPM IO thread
handling, allows to report backend error to hw/frontend, and
implements the CRB device.
It is a resend of '[PATCH v2 0/5] tpm: CRB device and cleanups', '[PATCH
v3] tpm: add CRB device', and '[PATCH] tpm: fix alignment issues'
c
Hi,
This series failed docker-quick@centos6 build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: cover.1516277913.git.arei.gong...@huawei.com
Subject: [Qemu-devel] [PATCH v4 0/5
Hi,
This series failed docker-build@min-glib build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: cover.1516277913.git.arei.gong...@huawei.com
Subject: [Qemu-devel] [PATCH v4 0/5
From: Gonglei
I posted the RFC verion a few months ago for DPDK
vhost-crypto implmention, and now it's time to send
the formal version. Because we need an user space scheme
for better performance.
The vhost user crypto server side patches had been
sent to DPDK community, pls see
[RFC PATCH 0/6]
On Thu, Jan 11, 2018 at 11:25:08AM +0100, Igor Mammedov wrote:
> On Wed, 10 Jan 2018 19:48:00 -0200
> Eduardo Habkost wrote:
>
> > On Wed, Jan 10, 2018 at 01:30:29PM -0800, Alistair Francis wrote:
> > > On Thu, Dec 28, 2017 at 6:59 AM, Eduardo Habkost
> > > wrote:
> > > > On Thu, Dec 28, 2017
On Wed, 10 Jan 2018 19:48:00 -0200
Eduardo Habkost wrote:
> On Wed, Jan 10, 2018 at 01:30:29PM -0800, Alistair Francis wrote:
> > On Thu, Dec 28, 2017 at 6:59 AM, Eduardo Habkost
> > wrote:
> > > On Thu, Dec 28, 2017 at 02:39:31PM +0100, Igor Mammedov wrote:
> > >> On Fri, 22 Dec 2017 11:47
On Wed, Jan 10, 2018 at 01:30:29PM -0800, Alistair Francis wrote:
> On Thu, Dec 28, 2017 at 6:59 AM, Eduardo Habkost wrote:
> > On Thu, Dec 28, 2017 at 02:39:31PM +0100, Igor Mammedov wrote:
> >> On Fri, 22 Dec 2017 11:47:00 -0800
> >> Alistair Francis wrote:
> >>
> >> > On Fri, Dec 22, 2017 at 1
On Thu, Dec 28, 2017 at 6:59 AM, Eduardo Habkost wrote:
> On Thu, Dec 28, 2017 at 02:39:31PM +0100, Igor Mammedov wrote:
>> On Fri, 22 Dec 2017 11:47:00 -0800
>> Alistair Francis wrote:
>>
>> > On Fri, Dec 22, 2017 at 10:45 AM, Alistair Francis
>> > wrote:
>> > > On Wed, Dec 20, 2017 at 2:06 PM,
V3 -> V4:
- Fixed documentation (added more impl details)
- Fixed compilation errors discovered by patchew.
- Addressed Michael S. Tsirkin comments:
- Removed unnecessary typedefs and replace them with
macros in VMware header files, together with explanations.
- Moved more code from v
On Thu, Dec 28, 2017 at 02:39:31PM +0100, Igor Mammedov wrote:
> On Fri, 22 Dec 2017 11:47:00 -0800
> Alistair Francis wrote:
>
> > On Fri, Dec 22, 2017 at 10:45 AM, Alistair Francis
> > wrote:
> > > On Wed, Dec 20, 2017 at 2:06 PM, Eduardo Habkost
> > > wrote:
> > >> On Tue, Dec 19, 2017 at 0
On Fri, 22 Dec 2017 11:47:00 -0800
Alistair Francis wrote:
> On Fri, Dec 22, 2017 at 10:45 AM, Alistair Francis
> wrote:
> > On Wed, Dec 20, 2017 at 2:06 PM, Eduardo Habkost
> > wrote:
> >> On Tue, Dec 19, 2017 at 05:03:59PM -0800, Alistair Francis wrote:
> >>> On Tue, Dec 19, 2017 at 4:55 PM,
On Fri, Dec 22, 2017 at 11:47:00AM -0800, Alistair Francis wrote:
> On Fri, Dec 22, 2017 at 10:45 AM, Alistair Francis
> wrote:
> > On Wed, Dec 20, 2017 at 2:06 PM, Eduardo Habkost
> > wrote:
> >> On Tue, Dec 19, 2017 at 05:03:59PM -0800, Alistair Francis wrote:
> >>> On Tue, Dec 19, 2017 at 4:5
On Fri, Dec 22, 2017 at 10:45 AM, Alistair Francis
wrote:
> On Wed, Dec 20, 2017 at 2:06 PM, Eduardo Habkost wrote:
>> On Tue, Dec 19, 2017 at 05:03:59PM -0800, Alistair Francis wrote:
>>> On Tue, Dec 19, 2017 at 4:55 PM, Alistair Francis
>>> wrote:
>>> > On Tue, Dec 19, 2017 at 4:43 PM, Peter M
On Wed, Dec 20, 2017 at 2:06 PM, Eduardo Habkost wrote:
> On Tue, Dec 19, 2017 at 05:03:59PM -0800, Alistair Francis wrote:
>> On Tue, Dec 19, 2017 at 4:55 PM, Alistair Francis
>> wrote:
>> > On Tue, Dec 19, 2017 at 4:43 PM, Peter Maydell
>> > wrote:
>> >> On 20 December 2017 at 00:27, Alistair
On Tue, Dec 19, 2017 at 05:03:59PM -0800, Alistair Francis wrote:
> On Tue, Dec 19, 2017 at 4:55 PM, Alistair Francis
> wrote:
> > On Tue, Dec 19, 2017 at 4:43 PM, Peter Maydell
> > wrote:
> >> On 20 December 2017 at 00:27, Alistair Francis
> >> wrote:
> >>> There are numorous QEMU machines tha
On Tue, Dec 19, 2017 at 4:55 PM, Alistair Francis
wrote:
> On Tue, Dec 19, 2017 at 4:43 PM, Peter Maydell
> wrote:
>> On 20 December 2017 at 00:27, Alistair Francis
>> wrote:
>>> There are numorous QEMU machines that only have a single or a handful of
>>> valid CPU options. To simplyfy the mana
On Tue, Dec 19, 2017 at 4:43 PM, Peter Maydell wrote:
> On 20 December 2017 at 00:27, Alistair Francis
> wrote:
>> There are numorous QEMU machines that only have a single or a handful of
>> valid CPU options. To simplyfy the management of specificying which CPU
>> is/isn't valid let's create a p
On 20 December 2017 at 00:27, Alistair Francis
wrote:
> There are numorous QEMU machines that only have a single or a handful of
> valid CPU options. To simplyfy the management of specificying which CPU
> is/isn't valid let's create a property that can be set in the machine
> init. We can then che
There are numorous QEMU machines that only have a single or a handful of
valid CPU options. To simplyfy the management of specificying which CPU
is/isn't valid let's create a property that can be set in the machine
init. We can then check to see if the user supplied CPU is in that list
or not.
I h
On Tue, Oct 31, 2017 at 04:19:33PM +0100, Marc-André Lureau wrote:
> Hi,
>
> This series adds DMA operations support to the qemu fw_cfg kernel
> module and populates "etc/vmcoreinfo" with vmcoreinfo location
> details.
>
> Note: the support for this entry handling has been merged for next
> qemu
Hi,
This series adds DMA operations support to the qemu fw_cfg kernel
module and populates "etc/vmcoreinfo" with vmcoreinfo location
details.
Note: the support for this entry handling has been merged for next
qemu release (2.11)
v4:
- export paddr_vmcoreinfo_note() to fix fw_cfg.ko build
- fix b
On Thu, Sep 28, 2017 at 10:59:53AM +0800, Peter Xu wrote:
> v4:
> - fix comment in patch 1 [Fam, Stefan]
> - add one more patch from Stefan to fix the aio glib warning
>
> v3:
> - pick up r-bs (one missing for Fam's on last patch)
> - fix patch 1 to create isolated internal container
>
> v2:
> -
v4:
- fix comment in patch 1 [Fam, Stefan]
- add one more patch from Stefan to fix the aio glib warning
v3:
- pick up r-bs (one missing for Fam's on last patch)
- fix patch 1 to create isolated internal container
v2:
- add one patch to provide object_get_internal_root() [Daniel]
- patch 2: use th
Hi Peter,
> -Original Message-
> From: Peter Xu [mailto:pet...@redhat.com]
> Sent: Wednesday, September 27, 2017 12:32 PM
> To: Bharat Bhushan
> Cc: eric.au...@redhat.com; eric.auger@gmail.com;
> peter.mayd...@linaro.org; alex.william...@redhat.com; m...@redhat.com;
> qemu-...@nongnu.
On Wed, Sep 27, 2017 at 06:46:18AM +, Bharat Bhushan wrote:
> Hi Peter,
Hi, Bharat!
>
> While vfio with virtio-iommu I observed one issue, When virtio-iommu device
> exists but guest kernel does not have virtio-iommu driver (not enabled in
> Config) then IOMMU faults are reported on host.
Hi Peter,
While vfio with virtio-iommu I observed one issue, When virtio-iommu device
exists but guest kernel does not have virtio-iommu driver (not enabled in
Config) then IOMMU faults are reported on host.
This is because no mapping is created in IOMMU, not even default guest-physical
to re
This patch series integrates VFIO/VHOST with virtio-iommu.
This version is mainly about rebasing on v4 version on
virtio-iommu device framework from Eric Augur and
addresing review comments.
This patch series allows PCI pass-through using virtio-iommu.
This series is based on:
- virtio-iommu
On Thu, 21 Sep 2017 20:08:36 +0200
Halil Pasic wrote:
> Abstract
>
>
> The objective of this series is introducing CCW IDA (indirect data
> access) support to our virtual channel subsystem implementation. Briefly
> CCW IDA can be thought of as a kind of a scatter gather support for a
>
[Restored cc:s]
On Tue, 26 Sep 2017 12:45:11 +0200
Halil Pasic wrote:
> On 09/26/2017 12:18 PM, Cornelia Huck wrote:
> > On Thu, 21 Sep 2017 20:08:36 +0200
> > Halil Pasic wrote:
> >
> >> Abstract
> >>
> >>
> >> The objective of this series is introducing CCW IDA (indirect data
> >>
On 09/26/2017 12:18 PM, Cornelia Huck wrote:
> On Thu, 21 Sep 2017 20:08:36 +0200
> Halil Pasic wrote:
>
>> Abstract
>>
>>
>> The objective of this series is introducing CCW IDA (indirect data
>> access) support to our virtual channel subsystem implementation. Briefly
>> CCW IDA can be
On Thu, 21 Sep 2017 20:08:36 +0200
Halil Pasic wrote:
> Abstract
>
>
> The objective of this series is introducing CCW IDA (indirect data
> access) support to our virtual channel subsystem implementation. Briefly
> CCW IDA can be thought of as a kind of a scatter gather support for a
>
Abstract
The objective of this series is introducing CCW IDA (indirect data
access) support to our virtual channel subsystem implementation. Briefly
CCW IDA can be thought of as a kind of a scatter gather support for a
single CCW. If certain flags are set, the cda is to be interpreted as
On Friday 18 August 2017 04:03 PM, David Gibson wrote:
> On Fri, Aug 18, 2017 at 03:36:44PM +0530, Aravinda Prasad wrote:
>> This series of patches adds support for FWNMI in PowerKVM guests.
>>
>> Memory error such as bit flips that cannot be corrected
>> by hardware is passed on to the kernel fo
On Fri, Aug 18, 2017 at 03:36:44PM +0530, Aravinda Prasad wrote:
> This series of patches adds support for FWNMI in PowerKVM guests.
>
> Memory error such as bit flips that cannot be corrected
> by hardware is passed on to the kernel for handling
> by raising machine check exception (an NMI). Upon
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 150305073858.13788.4068645609072927349.stgit@aravinda
Subject: [Qemu-devel] [PATCH v4 0/5] target-ppc/spapr: Add FWNMI support in
QEMU for PowerKVM guests
=== TEST SCRIPT
This series of patches adds support for FWNMI in PowerKVM guests.
Memory error such as bit flips that cannot be corrected
by hardware is passed on to the kernel for handling
by raising machine check exception (an NMI). Upon such
machine check exception, if the address in error belongs
to guest the
1 - 100 of 259 matches
Mail list logo
