Re: [Qemu-devel] [Qemu-ppc] [PATCH v2 02/19] spapr: introduce a skeleton for the XIVE interrupt controller

On 13/02/18 01:40, Benjamin Herrenschmidt wrote: > On Mon, 2018-02-12 at 13:20 +0100, Andrea Bolognani wrote: >> On Mon, 2018-02-12 at 13:02 +1100, Alexey Kardashevskiy wrote: >>> On 12/02/18 09:55, Benjamin Herrenschmidt wrote: >>>> Well, we have a problem t

Re: [Qemu-devel] [PATCH qemu v7 2/4] vfio/pci: Relax DMA map errors for MMIO regions

On 12/02/18 16:19, David Gibson wrote: > On Fri, Feb 09, 2018 at 06:55:01PM +1100, Alexey Kardashevskiy wrote: >> At the moment if vfio_memory_listener is registered in the system memory >> address space, it maps/unmaps every RAM memory region for DMA. >> It expects system pag

Re: [Qemu-devel] [PATCH v2 02/19] spapr: introduce a skeleton for the XIVE interrupt controller

On 12/02/18 09:55, Benjamin Herrenschmidt wrote: > On Sun, 2018-02-11 at 19:08 +1100, David Gibson wrote: >> On Thu, Jan 18, 2018 at 08:27:52AM +1100, Benjamin Herrenschmidt wrote: >>> On Wed, 2018-01-17 at 15:39 +0100, Cédric Le Goater wrote: Migration is a problem. We will need both backend

[Qemu-devel] [PATCH qemu v7 1/4] linux-headers: update to f1517df8701c

Update headers against f1517df8701c. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f1517df8701c Signed-off-by: Alexey Kardashevskiy <a...@ozlabs.ru> -- Pulled because of new VFIO_REGION_INFO_CAP_MSIX_MAPPABLE --- include/standard-headers/linux/input

[Qemu-devel] [PATCH qemu v7 2/4] vfio/pci: Relax DMA map errors for MMIO regions

are checked (aka "RAM device" regions). If the amount of errors printed is overwhelming, the MSIX relocation could be used to avoid excessive error output. This is unlikely to cause any behavioral change. Signed-off-by: Alexey Kardashevskiy <a...@ozlabs.ru> --- hw/vf

[Qemu-devel] [PATCH qemu v7 3/4] vfio-pci: Allow mmap of MSIX BAR

use of it so from now on QEMU tries mapping the entire BAR as a whole and emulate MSIX on top of that. [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a32295c612c57990d17fb0f41e7134394b2f35f6 Signed-off-by: Alexey Kardashevskiy <a...@ozlabs.ru> --- Chang

[Qemu-devel] [PATCH qemu v7 4/4] ppc/spapr, vfio: Turn off MSIX emulation for VFIO devices

to the guest for the pseries platform in order to achieve the maximum MMIO preformance for certain devices. Tested on: LSI Logic / Symbios Logic SAS3008 PCI-Express Fusion-MPT SAS-3 (rev 02) Signed-off-by: Alexey Kardashevskiy <a...@ozlabs.ru> --- Need to split this in two? --- hw/ppc/spapr.

[Qemu-devel] [PATCH qemu v7 0/4] vfio-pci: Allow mmap of MSIX BAR

7: * split into many patches * test iova/llsize against pgmask in vfio_listener_region_add/del * s/vfio_is_cap_present/vfio_has_region_cap/ * added comments here and there * s/vdev->msix->table_bar/region->nr/ Alexey Kardashevskiy (4): linux-headers: update to f1517df8701c vfio/pci: R

Re: [Qemu-devel] [RFC PATCH qemu] slirp: Update forwarding IP address if guest receiver non-default IP

On 01/02/18 20:36, Alexey Kardashevskiy wrote: > If we run QEMU with -netdev user,id=USER0,hostfwd=tcp::-:22, it starts > a DHCP server and starts allocating client IPs from 10.0.2.15 so > this is what the guest normally receives. Since QEMU automatically adds > the DHCP star

Re: [Qemu-devel] [PATCH qemu v2] machine: Polish -machine xxx,help

On 02/02/18 13:45, Alexey Kardashevskiy wrote: > On 29/01/18 16:03, Alexey Kardashevskiy wrote: >> On 15/12/17 15:47, Alexey Kardashevskiy wrote: >>> On 26/10/17 12:41, Alexey Kardashevskiy wrote: >>>> The "-machine xxx,help" prints kernel-irqchip possibl

Re: [Qemu-devel] [RFC PATCH] vfio/pci: Add ioeventfd support

On 08/02/18 01:12, Alex Williamson wrote: > On Wed, 7 Feb 2018 15:48:26 +1100 > Alexey Kardashevskiy <a...@ozlabs.ru> wrote: > >> On 07/02/18 15:25, Alex Williamson wrote: >>> On Wed, 7 Feb 2018 15:09:22 +1100 >>> Alexey Kardashevskiy <a...@ozlabs

Re: [Qemu-devel] [RFC PATCH] vfio/pci: Add ioeventfd support

On 07/02/18 15:25, Alex Williamson wrote: > On Wed, 7 Feb 2018 15:09:22 +1100 > Alexey Kardashevskiy <a...@ozlabs.ru> wrote: >> On 07/02/18 11:08, Alex Williamson wrote: >>> diff --git a/include/uapi/linux/vfio.h b/include/uapi/linux/vfio.h >>> ind

Re: [Qemu-devel] [RFC PATCH] vfio/pci: Add ioeventfd support

On 07/02/18 11:08, Alex Williamson wrote: > The ioeventfd here is actually irqfd handling of an ioeventfd such as > supported in KVM. A user is able to pre-program a device write to > occur when the eventfd triggers. This is yet another instance of > eventfd-irqfd triggering between KVM and

Re: [Qemu-devel] [RFC PATCH qemu] qmp: Add qom-list-properties to list QOM object properties

On 02/02/18 18:37, Markus Armbruster wrote: > Alexey Kardashevskiy <a...@ozlabs.ru> writes: > >> On 01/02/18 04:22, Markus Armbruster wrote: >>> Alexey Kardashevskiy <a...@ozlabs.ru> writes: >>> >>>> There is already 'device-list-proper

Re: [Qemu-devel] [PATCH qemu v2] machine: Polish -machine xxx,help

On 29/01/18 16:03, Alexey Kardashevskiy wrote: > On 15/12/17 15:47, Alexey Kardashevskiy wrote: >> On 26/10/17 12:41, Alexey Kardashevskiy wrote: >>> The "-machine xxx,help" prints kernel-irqchip possible values as >>> "OnOffSplit", this adds sepa

Re: [Qemu-devel] [RFC PATCH qemu] qmp: Add qom-list-properties to list QOM object properties

On 01/02/18 04:22, Markus Armbruster wrote: > Alexey Kardashevskiy <a...@ozlabs.ru> writes: > >> There is already 'device-list-properties' which does most of the job, >> however it does not handle everything returned by qom-list-types such >> as machines as they inh

[Qemu-devel] [RFC PATCH qemu] slirp: Update forwarding IP address if guest receiver non-default IP

), the forwarding stops working. The guest can still reach the outer world (which is expected). This updates the forwarding table when QEMU confirms the requested IP to the guest. Signed-off-by: Alexey Kardashevskiy <a...@ozlabs.ru> --- Does this look any useful? Sure I can remove /var/li

[Qemu-devel] [PATCH qemu] slirp/debug: Print IP addresses in human readable form

Signed-off-by: Alexey Kardashevskiy <a...@ozlabs.ru> --- slirp/arp_table.c | 4 ++-- slirp/socket.c| 8 slirp/udp.c | 4 ++-- 3 files changed, 8 insertions(+), 8 deletions(-) diff --git a/slirp/arp_table.c b/slirp/arp_table.c index 3547043..bac608f 100644 --- a

Re: [Qemu-devel] [RFC PATCH qemu v6] vfio-pci: Allow mmap of MSIX BAR

On 01/02/18 05:57, Alex Williamson wrote: > On Wed, 31 Jan 2018 18:24:45 +1100 > Alexey Kardashevskiy <a...@ozlabs.ru> wrote: > >> This makes use of a new VFIO_REGION_INFO_CAP_MSIX_MAPPABLE capability >> which tells that a region with MSIX data can be mapped entirely,

Re: [Qemu-devel] [RFC PATCH qemu] qmp: Add qom-list-properties to list QOM object properties

On 23/01/18 23:49, David Gibson wrote: > On Tue, Jan 23, 2018 at 01:03:39PM +0100, Andrea Bolognani wrote: >> On Tue, 2018-01-23 at 22:20 +1100, David Gibson wrote: David, I know you're busy with linux.conf.au, but it would be really helpful if you could carve out five minutes to look

[Qemu-devel] [RFC PATCH qemu v6] vfio-pci: Allow mmap of MSIX BAR

ocation could be used to avoid excessive error output. This requires the kernel change - "vfio-pci: Allow mapping MSIX BAR" - for the new capability: https://www.spinics.net/lists/kvm/msg160282.html Signed-off-by: Alexey Kardashevskiy <a...@ozlabs.ru> --- Changes: v6: * dropped that s

[Qemu-devel] [PATCH qemu v5 1/2] vfio/common: Add 'p2p' property to enable DMA mapping of MMIO regions

periment when needed. This adds necessary checks to the vfio_listener_region_del() hook. Signed-off-by: Alexey Kardashevskiy <a...@ozlabs.ru> --- include/hw/vfio/vfio-common.h | 1 + hw/vfio/common.c | 59 ++- hw/vfio/pci.c |

[Qemu-devel] [PATCH qemu v5 0/2] vfio-pci: Allow mmap of MSIX BAR

se comment. Thanks. Alexey Kardashevskiy (2): vfio/common: Add 'p2p' property to enable DMA mapping of MMIO regions RFC: vfio-pci: Allow mmap of MSIX BAR include/hw/vfio/vfio-common.h | 2 ++ linux-headers/linux/vfio.h| 5 +++ hw/ppc/spapr.c| 7 hw/vfi

[Qemu-devel] [PATCH qemu v5 2/2] RFC: vfio-pci: Allow mmap of MSIX BAR

w property also does not appear in "-machine pseries,help". This requires the kernel change - "vfio-pci: Allow mapping MSIX BAR" - for the new capability: https://www.spinics.net/lists/kvm/msg160282.html Signed-off-by: Alexey Kardashevskiy <a...@ozlabs.ru> --- Changes: v5

Re: [Qemu-devel] [PATCH qemu] configure: Allow capstone=git only if git update is not disabled

On 15/01/18 17:48, Thomas Huth wrote: > On 15.01.2018 03:35, Alexey Kardashevskiy wrote: >> Even with --disable-git-update, ./configure tries updating the capstone >> submodule instead of marking it "no"; this disables capstone submodule >> if git update is disabl

Re: [Qemu-devel] [PATCH qemu v2] machine: Polish -machine xxx,help

On 15/12/17 15:47, Alexey Kardashevskiy wrote: > On 26/10/17 12:41, Alexey Kardashevskiy wrote: >> The "-machine xxx,help" prints kernel-irqchip possible values as >> "OnOffSplit", this adds separators to the printed line. >> >> Also, since only lower

Re: [Qemu-devel] [PATCH qemu v4] RFC: vfio-pci: Allow mmap of MSIX BAR

On 26/01/18 00:56, Auger Eric wrote: > Hi Alexey, > > On 25/01/18 05:22, Alexey Kardashevskiy wrote: >> This makes use of a new VFIO_REGION_INFO_CAP_MSIX_MAPPABLE capability >> which tells that a region with MSIX data can be mapped entirely, i.e. >> the VFIO PCI driver

Re: [Qemu-devel] [PATCH] spapr_pci: fix MSI/MSIX selection

ev); > -if (max_msi) { > -_FDT(fdt_setprop_cell(fdt, offset, "ibm,req#msi", max_msi)); > +if (msi_present(dev)) { > +max_msi = msi_nr_vectors_allocated(dev); > +if (max_msi) { > +_FDT(fdt_setprop_cell(fdt, offset, "ibm,req#m

Re: [Qemu-devel] [QEMU-PPC] [PATCH V5 2/7] target/ppc/spapr_caps: Add macro to generate spapr_caps migration vmstate

On 29/01/18 10:43, Suraj Jitindar Singh wrote: > On Fri, 2018-01-19 at 16:18 +1100, Alexey Kardashevskiy wrote: >> On 19/01/18 16:00, Suraj Jitindar Singh wrote: >>> The vmstate description and the contained needed function for >>> migration >>> of

[Qemu-devel] [PATCH qemu v4] RFC: vfio-pci: Allow mmap of MSIX BAR

his requires the kernel change - "vfio-pci: Allow mapping MSIX BAR" - for the new capability: https://www.spinics.net/lists/kvm/msg160282.html Signed-off-by: Alexey Kardashevskiy <a...@ozlabs.ru> --- Changes: v4: * silenced dma map errors if unaligned mapping is

[Qemu-devel] [PATCH qemu] vfio/common: Remove redundand copy of local variable

There is already @hostwin in vfio_listener_region_add() so there is no point in having the other one. Fixes: 2e4109de "vfio/spapr: Create DMA window dynamically (SPAPR IOMMU v2)" Signed-off-by: Alexey Kardashevskiy <a...@ozlabs.ru> --- hw/vfio/common.c | 1 - 1 file changed, 1 d

[Qemu-devel] [PATCH qemu v3] RFC: vfio-pci: Allow mmap of MSIX BAR

r/and a size not aligned which will make vfio_dma_map() fail; to address this, this makes treats such failures as non-fatal. This requires the kernel change - "vfio-pci: Allow mapping MSIX BAR" - for the new capability: https://www.spinics.net/lists/kvm/msg160282.html Signed-off-

Re: [Qemu-devel] [PATCH qemu v2] RFC: vfio-pci: Allow mmap of MSIX BAR

On 20/01/18 02:57, Alex Williamson wrote: > On Fri, 19 Jan 2018 19:55:49 +1100 > Alexey Kardashevskiy <a...@ozlabs.ru> wrote: > >> On 19/01/18 08:59, Alex Williamson wrote: >>> On Tue, 16 Jan 2018 16:17:58 +1100 >>> Alexey Kardashevskiy <a...@ozlabs.ru&g

Re: [Qemu-devel] [PATCH qemu v2] RFC: vfio-pci: Allow mmap of MSIX BAR

On 19/01/18 08:59, Alex Williamson wrote: > On Tue, 16 Jan 2018 16:17:58 +1100 > Alexey Kardashevskiy <a...@ozlabs.ru> wrote: > >> On 06/01/18 02:29, Alex Williamson wrote: >>> On Fri, 5 Jan 2018 10:48:07 +0100 >>> Auger Eric <eric.au...@redhat.com>

Re: [Qemu-devel] [PATCH qemu] spapr_pci: Alias MMIO windows to PHB address space

On 18/01/18 16:33, Alexey Kardashevskiy wrote: > On 18/01/18 14:47, Alexey Kardashevskiy wrote: >> At the moment the sPAPR PHB MMIO space does not have an address space >> object as it does not really need one - guest accesses it via virtual >> addresses (and we provide mapp

Re: [Qemu-devel] [RFC PATCH qemu] qmp: Add qom-list-properties to list QOM object properties

On 19/01/18 17:15, Alexey Kardashevskiy wrote: > On 19/01/18 16:19, David Gibson wrote: >> On Fri, Jan 19, 2018 at 04:09:06PM +1100, Alexey Kardashevskiy wrote: >>> There is already 'device-list-properties' which does most of the job, >>> however it does not handle ever

Re: [Qemu-devel] [RFC PATCH qemu] qmp: Add qom-list-properties to list QOM object properties

On 19/01/18 16:19, David Gibson wrote: > On Fri, Jan 19, 2018 at 04:09:06PM +1100, Alexey Kardashevskiy wrote: >> There is already 'device-list-properties' which does most of the job, >> however it does not handle everything returned by qom-list-types such >> as machines as

Re: [Qemu-devel] [QEMU-PPC] [PATCH V5 2/7] target/ppc/spapr_caps: Add macro to generate spapr_caps migration vmstate

On 19/01/18 16:00, Suraj Jitindar Singh wrote: > The vmstate description and the contained needed function for migration > of spapr_caps is the same for each cap, with the name of the cap > substituted. As such introduce a macro to allow for easier generation of > these. > > Convert the three

[Qemu-devel] [RFC PATCH qemu] qmp: Add qom-list-properties to list QOM object properties

class and its instance. It is pretty much a simplified copy of the device-list-properties handler. Since it creates an object instance, device properties should appear in the output as they are copied to QOM properties at the instance_init hook. Signed-off-by: Alexey Kardashevskiy <a...@ozlabs

Re: [Qemu-devel] [PATCH qemu v2] RFC: vfio-pci: Allow mmap of MSIX BAR

On 19/01/18 14:25, Alex Williamson wrote: > On Fri, 19 Jan 2018 13:41:41 +1100 > Alexey Kardashevskiy <a...@ozlabs.ru> wrote: > >> On 19/01/18 08:59, Alex Williamson wrote: >>> On Tue, 16 Jan 2018 16:17:58 +1100 >>> Alexey Kardashevskiy <a...@ozlabs.ru&g

Re: [Qemu-devel] [Qemu-ppc] [QEMU-PPC] [PATCH V3 0/6] target/ppc: Rework spapr_caps

On 19/01/18 13:22, David Gibson wrote: > On Thu, Jan 18, 2018 at 04:55:39PM +0100, Andrea Bolognani wrote: >> On Thu, 2018-01-18 at 15:27 +1100, David Gibson wrote: I looked further and device-list-properties looks like it would do the trick; however it doesn't seem to work for machines:

Re: [Qemu-devel] [PATCH qemu v2] RFC: vfio-pci: Allow mmap of MSIX BAR

On 19/01/18 08:59, Alex Williamson wrote: > On Tue, 16 Jan 2018 16:17:58 +1100 > Alexey Kardashevskiy <a...@ozlabs.ru> wrote: > >> On 06/01/18 02:29, Alex Williamson wrote: >>> On Fri, 5 Jan 2018 10:48:07 +0100 >>> Auger Eric <eric.au...@redhat.com>

Re: [Qemu-devel] [PATCH for-2.11] vfio: Fix vfio-kvm group registration

On 19/01/18 09:15, Alex Williamson wrote: > On Thu, 18 Jan 2018 20:29:48 +1100 > Alexey Kardashevskiy <a...@ozlabs.ru> wrote: > >> On 06/12/17 12:30, Alex Williamson wrote: >>> On Wed, 6 Dec 2017 12:02:01 +1100 >>> Alexey Kardashevskiy <a...@ozlabs.ru&g

Re: [Qemu-devel] [PATCH for-2.11] vfio: Fix vfio-kvm group registration

On 06/12/17 12:30, Alex Williamson wrote: > On Wed, 6 Dec 2017 12:02:01 +1100 > Alexey Kardashevskiy <a...@ozlabs.ru> wrote: > >> On 06/12/17 08:09, Alex Williamson wrote: >>> Commit 8c37faa475f3 ("vfio-pci, ppc64/spapr: Reorder group-to-container >>&

Re: [Qemu-devel] [Qemu-ppc] [QEMU-PPC] [PATCH V3 6/6] target/ppc/spapr: Add H-Call H_GET_CPU_CHARACTERISTICS

On 18/01/18 16:53, David Gibson wrote: > On Thu, Jan 18, 2018 at 04:44:28PM +1100, Alexey Kardashevskiy wrote: >> On 18/01/18 16:20, David Gibson wrote: >>> On Mon, Jan 15, 2018 at 05:32:35PM +1100, Suraj Jitindar Singh wrote: >>>> The new H-Call H_GET_CPU_CHARAC

Re: [Qemu-devel] [Qemu-ppc] [QEMU-PPC] [PATCH V3 6/6] target/ppc/spapr: Add H-Call H_GET_CPU_CHARACTERISTICS

On 18/01/18 16:20, David Gibson wrote: > On Mon, Jan 15, 2018 at 05:32:35PM +1100, Suraj Jitindar Singh wrote: >> The new H-Call H_GET_CPU_CHARACTERISTICS is used by the guest to query >> behaviours and available characteristics of the cpu. >> >> Implement the handler for this new H-Call which

Re: [Qemu-devel] [PATCH qemu] spapr_pci: Alias MMIO windows to PHB address space

On 18/01/18 14:47, Alexey Kardashevskiy wrote: > At the moment the sPAPR PHB MMIO space does not have an address space > object as it does not really need one - guest accesses it via virtual > addresses (and we provide mappings to the CPU space), the device drivers > in QEMU access M

[Qemu-devel] [PATCH qemu] spapr_pci: Alias MMIO windows to PHB address space

80003000-800030ff (prio 0, i/o): msix-table + 80003800-80003807 (prio 0, i/o): msix-pba 0400-0400 (prio 0, i/o): msi 0800-08007fff (prio 0, i/o): tce-iommu-8001 The major point for this is to help debugging overlapped r

Re: [Qemu-devel] [Qemu-ppc] [QEMU-PPC] [PATCH V3 0/6] target/ppc: Rework spapr_caps

On 17/01/18 10:30, David Gibson wrote: > On Wed, Jan 17, 2018 at 10:26:28AM +1100, Alexey Kardashevskiy wrote: >> On 17/01/18 09:34, David Gibson wrote: >>> On Tue, Jan 16, 2018 at 03:46:20PM +0100, Andrea Bolognani wrote: >>>> On Wed, 2018-01-17 at 00:54 +1100, Davi

Re: [Qemu-devel] [Qemu-ppc] [QEMU-PPC] [PATCH V3 0/6] target/ppc: Rework spapr_caps

On 17/01/18 09:34, David Gibson wrote: > On Tue, Jan 16, 2018 at 03:46:20PM +0100, Andrea Bolognani wrote: >> On Wed, 2018-01-17 at 00:54 +1100, David Gibson wrote: Correct me if I'm wrong, but it seems to me like there's no way to figure out through QMP whether these new machine options

Re: [Qemu-devel] [PATCH qemu v2] RFC: vfio-pci: Allow mmap of MSIX BAR

On 06/01/18 02:29, Alex Williamson wrote: > On Fri, 5 Jan 2018 10:48:07 +0100 > Auger Eric <eric.au...@redhat.com> wrote: > >> Hi Alexey, >> >> On 15/12/17 07:29, Alexey Kardashevskiy wrote: >>> This makes use of a new VFIO_REGION_INFO_CAP_MSIX_MAPPABL

Re: [Qemu-devel] [PATCH qemu 0/3] spapr/iommu: Enable in-kernel TCE acceleration via VFIO KVM device

On 03/01/18 04:51, Paolo Bonzini wrote: > On 02/01/2018 06:28, Alexey Kardashevskiy wrote: >> This is my current queue of the in-kernel TCE acceleration >> enablement. >> >> Changes since >> https://lists.gnu.org/archive/html/qemu-devel/2017-12/msg01918.html : &

Re: [Qemu-devel] [PATCH qemu v2] kvm: Add kvm_set_user_memory tracepoint

Ping? It is quite simple... On 02/01/18 14:40, Alexey Kardashevskiy wrote: > On 15/12/17 20:46, Darren Kenny wrote: >> On Fri, Dec 15, 2017 at 04:23:26PM +1100, Alexey Kardashevskiy wrote: >>> This adds a tracepoint to trace the KVM_SET_USER_MEMORY_REGION ioctl >>>

Re: [Qemu-devel] [PATCH v2 0/5] vfio/pci: MSI-X MMIO relocation

ccess. Instead, auto is now a placeholder for > a device/platform lookup for known good combinations (though if I'm > pessimistic, even that might depend on guest and driver versions). > Thanks, Tested-by: Alexey Kardashevskiy <a...@ozlabs.ru> > > Alex > > ---

Re: [Qemu-devel] question about share flatviews

On 14/01/18 23:20, CheneyLin wrote: > Hi， Paolo, > > Alexey > commit 967dc9b > > commit 967dc9b > > > commit 967dc9b > > commit 967dc9b Share FlatView's and dispatch trees between address spaces > > commit 967dc9b. > > .  > > I'm wondering why we have to shares flatviews between different

[Qemu-devel] [PATCH qemu] configure: Allow capstone=git only if git update is not disabled

Even with --disable-git-update, ./configure tries updating the capstone submodule instead of marking it "no"; this disables capstone submodule if git update is disabled. Signed-off-by: Alexey Kardashevskiy <a...@ozlabs.ru> --- configure | 2 +- 1 file changed, 1 insertion(+), 1 d

[Qemu-devel] [PATCH qemu] target/ppc: Yet another fix for KVM-HV HPTE accessors

gative values which then are converted to size_t for memset() and that throws seg fault. This fixes the math. While here, fix the last @i increment as well. Fixes: 1ad9f0a464fe "target/ppc: Fix KVM-HV HPTE accessors" Signed-off-by: Alexey Kardashevskiy <a...@ozlabs.ru> --- Record #0:

Re: [Qemu-devel] [PATCH qemu v3] RFC: ppc/spapr: Receive and store device tree blob from SLOF

On 03/01/18 11:09, David Gibson wrote: > On Tue, Jan 02, 2018 at 05:13:09PM +1100, Alexey Kardashevskiy wrote: >> On 11/12/17 17:20, Alexey Kardashevskiy wrote: >>> On 09/11/17 17:38, David Gibson wrote: >>>> On Tue, Nov 07, 2017 at 06:14:04PM +1100, Alexey Kardashe

Re: [Qemu-devel] [PATCH] spapr: Correct compatibility mode setting for hotplugged CPUs

n all CPUs at machine > reset, so we change that to only set the mode for the boot cpu. > > Signed-off-by: David Gibson <da...@gibson.dropbear.id.au> Reviewed-by: Alexey Kardashevskiy <a...@ozlabs.ru> > --- > hw/ppc/spapr.c | 2 +- > hw/ppc/spapr_rtas

Re: [Qemu-devel] [PATCH qemu v3] RFC: ppc/spapr: Receive and store device tree blob from SLOF

On 11/12/17 17:20, Alexey Kardashevskiy wrote: > On 09/11/17 17:38, David Gibson wrote: >> On Tue, Nov 07, 2017 at 06:14:04PM +1100, Alexey Kardashevskiy wrote: >>> On 20/10/17 11:46, Alexey Kardashevskiy wrote: >>>> On 19/10/17 17:24, David Gibson wrote: >>&g

Re: [Qemu-devel] [RFC 0/3] Extend vhost-user to support VFIO based accelerators

On 02/01/18 16:49, Liang, Cunming wrote: > > >> -Original Message----- >> From: Alexey Kardashevskiy [mailto:a...@ozlabs.ru] >> Sent: Tuesday, January 2, 2018 10:42 AM >> To: Bie, Tiwei <tiwei@intel.com>; virtio-...@lists.oasis-open.org; qemu-

[Qemu-devel] [PATCH qemu 3/3] spapr/iommu: Enable in-kernel TCE acceleration via VFIO KVM device

the KVM_DEV_VFIO_GROUP_SET_SPAPR_TCE ioctl and establish LIOBN-to-IOMMU link. This changes spapr_tce_set_need_vfio() to avoid TCE table reallocation if the kernel supports the TCE acceleration. Signed-off-by: Alexey Kardashevskiy <a...@ozlabs.ru> --- target/ppc/kvm_ppc.h | 6 ++ hw/ppc/spapr_iommu.

[Qemu-devel] [PATCH qemu 1/3] memory/iommu: Add get_attr()

This adds get_attr() to IOMMUMemoryRegionClass, like iommu_ops::domain_get_attr in the Linux kernel. This defines the first attribute - IOMMU_ATTR_SPAPR_TCE_FD - which will be used between the pSeries machine and VFIO-PCI. Signed-off-by: Alexey Kardashevskiy <a...@ozlabs.ru> --- includ

[Qemu-devel] [PATCH qemu 0/3] spapr/iommu: Enable in-kernel TCE acceleration via VFIO KVM device

acros". Please comment. Thanks. Alexey Kardashevskiy (3): memory/iommu: Add get_attr() vfio/spapr: Use iommu memory region's get_attr() spapr/iommu: Enable in-kernel TCE acceleration via VFIO KVM device include/exec/memory.h | 22 ++ target/ppc/kvm_ppc.h | 6

[Qemu-devel] [PATCH qemu 2/3] vfio/spapr: Use iommu memory region's get_attr()

. Signed-off-by: Alexey Kardashevskiy <a...@ozlabs.ru> --- hw/vfio/common.c | 26 ++ hw/vfio/trace-events | 1 + 2 files changed, 27 insertions(+) diff --git a/hw/vfio/common.c b/hw/vfio/common.c index b77be3a..ebe28fe 100644 --- a/hw/vfio/common.c +++ b/h

Re: [Qemu-devel] [PATCH qemu v2] kvm: Add kvm_set_user_memory tracepoint

On 15/12/17 20:46, Darren Kenny wrote: > On Fri, Dec 15, 2017 at 04:23:26PM +1100, Alexey Kardashevskiy wrote: >> This adds a tracepoint to trace the KVM_SET_USER_MEMORY_REGION ioctl >> parameters which is quite useful for debugging VFIO memory regions >> being actuall

Re: [Qemu-devel] [RFC 0/3] Extend vhost-user to support VFIO based accelerators

On 22/12/17 17:41, Tiwei Bie wrote: > This RFC patch set does some small extensions to vhost-user protocol > to support VFIO based accelerators, and makes it possible to get the > similar performance of VFIO passthru while keeping the virtio device > emulation in QEMU. > > When we have virtio

Re: [Qemu-devel] [PATCH qemu] RFC: spapr/iommu: Enable in-kernel TCE acceleration via VFIO KVM device

On 20/12/17 20:04, Paolo Bonzini wrote: > On 20/12/2017 02:47, Alexey Kardashevskiy wrote: >>> - if we foresee having more IOMMU devices in KVM, let's rename >>> KVM_DEV_VFIO_GROUP_SET_SPAPR_TCE to KVM_DEV_VFIO_GROUP_ATTACH_IOMMU and >>> add a

Re: [Qemu-devel] [PATCH qemu] RFC: spapr/iommu: Enable in-kernel TCE acceleration via VFIO KVM device

On 20/12/17 01:59, Paolo Bonzini wrote: > On 19/12/2017 15:09, Alex Williamson wrote: >> On Tue, 19 Dec 2017 12:12:35 +0100 >> Paolo Bonzini wrote: >> >>> On 12/12/2017 06:46, Alex Williamson wrote: > +enum IOMMUMemoryRegionAttr { > +IOMMU_ATTR_KVM_FD

Re: [Qemu-devel] [PATCH qemu v2] RFC: vfio-pci: Allow mmap of MSIX BAR

On 20/12/17 04:26, Alex Williamson wrote: > On Tue, 19 Dec 2017 15:52:02 +1100 > David Gibson <da...@gibson.dropbear.id.au> wrote: > >> On Fri, Dec 15, 2017 at 05:29:14PM +1100, Alexey Kardashevskiy wrote: >>> This makes use of a new VFIO_REGION_INFO_CAP_MSIX_MAPPA

Re: [Qemu-devel] [RFC/RFT PATCH 5/5] vfio/pci: Allow relocating MSI-X MMIO

On 19/12/17 17:56, Alex Williamson wrote: > On Tue, 19 Dec 2017 17:02:59 +1100 > Alexey Kardashevskiy <a...@ozlabs.ru> wrote: > >> On 19/12/17 14:40, Alex Williamson wrote: >>> On Tue, 19 Dec 2017 14:07:13 +1100 >>> Alexey Kardashevskiy <a...@ozlabs.ru&g

Re: [Qemu-devel] [PATCH] hw/ppc: Remove the deprecated spapr-pci-vfio-host-bridge device

hat.com> Reviewed-by: Alexey Kardashevskiy <a...@ozlabs.ru> > --- > hw/ppc/spapr_pci_vfio.c | 47 > --- > qemu-doc.texi | 5 - > scripts/device-crash-test | 1 - > 3 files changed, 53 deletions(-) >

Re: [Qemu-devel] [RFC/RFT PATCH 5/5] vfio/pci: Allow relocating MSI-X MMIO

On 19/12/17 14:40, Alex Williamson wrote: > On Tue, 19 Dec 2017 14:07:13 +1100 > Alexey Kardashevskiy <a...@ozlabs.ru> wrote: > >> On 18/12/17 16:02, Alex Williamson wrote: >>> With recently proposed kernel side vfio-pci changes, the MSI-X vector >>>

Re: [Qemu-devel] [RFC/RFT PATCH 2/5] vfio/pci: Add base BAR MemoryRegion

On 19/12/17 14:56, Alex Williamson wrote: > On Tue, 19 Dec 2017 14:44:51 +1100 > Alexey Kardashevskiy <a...@ozlabs.ru> wrote: > >> On 18/12/17 16:02, Alex Williamson wrote: >>> Add one more layer to our stack of MemoryRegions, this base region >>> a

Re: [Qemu-devel] [RFC/RFT PATCH 2/5] vfio/pci: Add base BAR MemoryRegion

On 18/12/17 16:02, Alex Williamson wrote: > Add one more layer to our stack of MemoryRegions, this base region > allows us to register BARs independently of the vfio region or to > extend the size of BARs which do map to a region. This will be > useful when we want hypervisor defined BARs or

Re: [Qemu-devel] [RFC/RFT PATCH 5/5] vfio/pci: Allow relocating MSI-X MMIO

On 18/12/17 16:02, Alex Williamson wrote: > With recently proposed kernel side vfio-pci changes, the MSI-X vector > table area can be mmap'd from userspace, allowing direct access to > non-MSI-X registers within the host page size of this area. However, > we only get that direct access if QEMU

Re: [Qemu-devel] [RFC/RFT PATCH 5/5] vfio/pci: Allow relocating MSI-X MMIO

On 19/12/17 01:28, Alex Williamson wrote: > On Tue, 19 Dec 2017 00:55:32 +1100 > Alexey Kardashevskiy <a...@ozlabs.ru> wrote: > >> On 19/12/17 00:28, Alex Williamson wrote: >>> On Mon, 18 Dec 2017 20:04:23 +1100 >>> Alexey Kardashevskiy <a...@ozlabs.ru&g

Re: [Qemu-devel] [RFC/RFT PATCH 5/5] vfio/pci: Allow relocating MSI-X MMIO

On 19/12/17 00:28, Alex Williamson wrote: > On Mon, 18 Dec 2017 20:04:23 +1100 > Alexey Kardashevskiy <a...@ozlabs.ru> wrote: > >> On 18/12/17 16:02, Alex Williamson wrote: >>> With recently proposed kernel side vfio-pci changes, the MSI-X vector >>>

Re: [Qemu-devel] [RFC/RFT PATCH 5/5] vfio/pci: Allow relocating MSI-X MMIO

On 18/12/17 16:02, Alex Williamson wrote: > With recently proposed kernel side vfio-pci changes, the MSI-X vector > table area can be mmap'd from userspace, allowing direct access to > non-MSI-X registers within the host page size of this area. However, > we only get that direct access if QEMU

[Qemu-devel] [GIT PULL for qemu-pseries] pseries: Update SLOF firmware image to qemu-slof-20171214

The following changes since commit 6b092cf3141ec02fa5f533ecdcd24264febfcd76: pseries: Update SLOF firmware image to qemu-slof-20171214 (2017-12-18 13:16:40 +1100) are available in the git repository at: g...@github.com:aik/qemu.git tags/qemu-slof-20171214 for you to fetch changes up to

Re: [Qemu-devel] [Qemu-ppc] [PATCH] ppc/pnv: change powernv_ prefix to pnv_ for overall naming consistency

On 15/12/17 17:17, Cédric Le Goater wrote: > Signed-off-by: Cédric Le Goater > --- > hw/ppc/pnv.c | 84 > ++-- > hw/ppc/pnv_core.c| 8 ++--- > hw/ppc/pnv_lpc.c | 2 +- > include/hw/ppc/pnv.h | 8 ++--- > 4 files

[Qemu-devel] [PATCH qemu v2] RFC: vfio-pci: Allow mmap of MSIX BAR

gned to the page size, the KVM memory listener does not register it with the KVM as a memory slot and MSIX is emulated by QEMU as before. This requires the kernel change - "vfio-pci: Allow mapping MSIX BAR" - for the new capability: https://www.spinics.net/lists/kvm/msg160282.html Signed-off-

Re: [Qemu-devel] [PATCH qemu v2] vfio/spapr: Allow fallback to SPAPR TCE IOMMU v1

On 15/12/17 17:01, David Gibson wrote: > On Tue, Dec 12, 2017 at 04:16:19PM +1100, Alexey Kardashevskiy wrote: >> The vfio_iommu_spapr_tce driver advertises kernel's support for >> v1 and v2 IOMMU support, however it is not always possible to use >> the requested IOMMU type. F

[Qemu-devel] [PATCH qemu v2] kvm: Add kvm_set_user_memory tracepoint

This adds a tracepoint to trace the KVM_SET_USER_MEMORY_REGION ioctl parameters which is quite useful for debugging VFIO memory regions being actually registered with KVM. Signed-off-by: Alexey Kardashevskiy <a...@ozlabs.ru> --- Changes: v2: * added forgotten change to trace-events --- acc

Re: [Qemu-devel] [PATCH qemu v2] machine: Polish -machine xxx,help

On 26/10/17 12:41, Alexey Kardashevskiy wrote: > The "-machine xxx,help" prints kernel-irqchip possible values as > "OnOffSplit", this adds separators to the printed line. > > Also, since only lower case letters are specified in qapi/common.json, > this change

[Qemu-devel] [PATCH qemu] kvm: Add kvm_set_user_memory tracepoint

This adds a tracepoint to trace the KVM_SET_USER_MEMORY_REGION ioctl parameters which is quite useful for debugging VFIO memory regions being actually registered with KVM. Signed-off-by: Alexey Kardashevskiy <a...@ozlabs.ru> --- accel/kvm/kvm-all.c | 6 +- 1 file changed, 5 insertions

Re: [Qemu-devel] [PATCH qemu] RFC: vfio-pci: Allow mmap of MSIX BAR

On 12/12/17 17:06, Alexey Kardashevskiy wrote: > On 12/12/17 16:54, Alex Williamson wrote: >> On Tue, 12 Dec 2017 16:21:31 +1100 >> Alexey Kardashevskiy <a...@ozlabs.ru> wrote: >> >>> This makes use of a new VFIO_REGION_INFO_CAP_MSIX_MAPPABLE capability >>

Re: [Qemu-devel] [PATCH qemu] RFC: vfio-pci: Allow mmap of MSIX BAR

On 12/12/17 16:54, Alex Williamson wrote: > On Tue, 12 Dec 2017 16:21:31 +1100 > Alexey Kardashevskiy <a...@ozlabs.ru> wrote: > >> This makes use of a new VFIO_REGION_INFO_CAP_MSIX_MAPPABLE capability >> which tells that a region with MSIX data can be mapped entirely,

Re: [Qemu-devel] [PATCH qemu] RFC: vfio-pci: Allow mmap of MSIX BAR

On 12/12/17 16:21, Alexey Kardashevskiy wrote: > This makes use of a new VFIO_REGION_INFO_CAP_MSIX_MAPPABLE capability > which tells that a region with MSIX data can be mapped entirely, i.e. > the VFIO PCI driver won't prevent MSIX vectors area from being mapped. > > This adds

[Qemu-devel] [PATCH qemu] RFC: vfio-pci: Allow mmap of MSIX BAR

rue" by default and "false" for pseries-2.12+ machines. This requites kernel's "vfio-pci: Allow mapping MSIX BAR" https://www.spinics.net/lists/kvm/msg160282.html Signed-off-by: Alexey Kardashevskiy <a...@ozlabs.ru> --- This is an RFC as it requires kernel headers up

[Qemu-devel] [PATCH qemu] RFC: spapr/iommu: Enable in-kernel TCE acceleration via VFIO KVM device

-by: Alexey Kardashevskiy <a...@ozlabs.ru> --- Assuming it is accepted, does it make sense to split include/exec/memory.h out and get merged separately? --- include/exec/memory.h | 10 ++ target/ppc/kvm_ppc.h | 6 ++ hw/ppc/spapr_iommu.c | 19 +++ hw/vfio/co

[Qemu-devel] [PATCH qemu v2] vfio-pci: Remove unused fields from VFIOMSIXInfo

When support for multiple mappings per a region were added, this was left behind, let's finish and remove unused bits. Fixes: db0da029a185 "vfio: Generalize region support" Signed-off-by: Alexey Kardashevskiy <a...@ozlabs.ru> --- Changes: v2: * updated commit log --- hw/vfio

[Qemu-devel] [PATCH qemu v2] vfio/spapr: Allow fallback to SPAPR TCE IOMMU v1

a fallback to the v1 IOMMU if v2 cannot be used. Fixes: 318f67ce1371 "vfio: spapr: Add DMA memory preregistering (SPAPR IOMMU v2)" Signed-off-by: Alexey Kardashevskiy <a...@ozlabs.ru> --- Changes: v2: * updated commit log --- hw/vfio/common.c | 5 + 1 file changed, 5 insertions(+)

Re: [Qemu-devel] [PATCH qemu v3] RFC: ppc/spapr: Receive and store device tree blob from SLOF

On 09/11/17 17:38, David Gibson wrote: > On Tue, Nov 07, 2017 at 06:14:04PM +1100, Alexey Kardashevskiy wrote: >> On 20/10/17 11:46, Alexey Kardashevskiy wrote: >>> On 19/10/17 17:24, David Gibson wrote: >>>> On Tue, Oct 17, 2017 at 04:55:03PM +1100, Alexey Kardashe

Re: [Qemu-devel] [PATCH for-2.11] vfio: Fix vfio-kvm group registration

On 06/12/17 12:30, Alex Williamson wrote: > On Wed, 6 Dec 2017 12:02:01 +1100 > Alexey Kardashevskiy <a...@ozlabs.ru> wrote: > >> On 06/12/17 08:09, Alex Williamson wrote: >>> Commit 8c37faa475f3 ("vfio-pci, ppc64/spapr: Reorder group-to-container >>&

Re: [Qemu-devel] [PATCH for-2.11] vfio: Fix vfio-kvm group registration

t words) to propose for 2.11 at this late date. If > the first group is hot unplugged then KVM may revert to code emulation > that assumes no non-coherent DMA is present on some systems. Also for > KVMGT, if the vGPU is not the first device registered, then the > notifier to enab

Re: [Qemu-devel] [PATCH qemu v5 1/2] memory/iommu/vfio: Define add_vfio_group() callback

On 01/12/17 10:09, Alex Williamson wrote: > On Fri, 1 Dec 2017 08:56:42 +1100 > Alexey Kardashevskiy <a...@ozlabs.ru> wrote: > >> On 05/10/17 16:50, Alexey Kardashevskiy wrote: >>> The new callback will be called when a new VFIO IOMMU group is added. >>> >

Re: [Qemu-devel] [PATCH qemu v5 1/2] memory/iommu/vfio: Define add_vfio_group() callback

On 05/10/17 16:50, Alexey Kardashevskiy wrote: > The new callback will be called when a new VFIO IOMMU group is added. > > This should cause no behavioral change, the next patch will. > > Signed-off-by: Alexey Kardashevskiy <a...@ozlabs.ru> What about this one

Re: [Qemu-devel] [PATCH qemu] vfio-pci: Remove unused fields from VFIOMSIXInfo

On 30/11/17 13:05, Alex Williamson wrote: > On Thu, 30 Nov 2017 12:56:09 +1100 > Alexey Kardashevskiy <a...@ozlabs.ru> wrote: > >> On 30/11/17 02:36, Alex Williamson wrote: >>> On Wed, 22 Nov 2017 18:39:47 +1100 >>> Alexey Kardashevskiy <a...@ozlabs.ru&g

Re: [Qemu-devel] [PATCH qemu] vfio/spapr: Allow fallback to SPAPR TCE IOMMU v1

On 30/11/17 02:26, Alex Williamson wrote: > On Wed, 22 Nov 2017 16:15:52 +1100 > Alexey Kardashevskiy <a...@ozlabs.ru> wrote: > >> The vfio_iommu_spapr_tce driver always advertises v1 and v2 IOMMU support, >> however PR KVM (a special version of KVM designed to work in

<    2   3   4   5   6   7   8   9   10   11   >