From: Alexey Kardashevskiy <aik@ozlabs.ru> To: David Gibson <david@gibson.dropbear.id.au> Cc: linuxppc-dev@lists.ozlabs.org, kvm@vger.kernel.org, Alistair Popple <alistair@popple.id.au>, Alex Williamson <alex.williamson@redhat.com>, Oliver O'Halloran <oohall@gmail.com> Subject: Re: [PATCH kernel RFC 0/4] powerpc/powenv/ioda: Allow huge DMA window at 4GB Date: Thu, 23 Jan 2020 19:42:26 +1100 Message-ID: <df097089-5477-1aa9-cf79-07241579cb73@ozlabs.ru> (raw) In-Reply-To: <20200123011730.GL2347@umbus.fritz.box> On 23/01/2020 12:17, David Gibson wrote: > On Thu, Jan 23, 2020 at 11:53:32AM +1100, Alexey Kardashevskiy wrote: >> Anyone, ping? > > Sorry, I've totally lost track of this one. I think you'll need to > repost. It has not changed and still applies, and the question is more about how we proceed with this feature that the patches themselves. Or it is just not in your mailbox anymore so you cannot reply? :) > > >> >> >> On 10/01/2020 15:18, Alexey Kardashevskiy wrote: >>> >>> >>> On 02/12/2019 12:59, Alexey Kardashevskiy wrote: >>>> Here is an attempt to support bigger DMA space for devices >>>> supporting DMA masks less than 59 bits (GPUs come into mind >>>> first). POWER9 PHBs have an option to map 2 windows at 0 >>>> and select a windows based on DMA address being below or above >>>> 4GB. >>>> >>>> This adds the "iommu=iommu_bypass" kernel parameter and >>>> supports VFIO+pseries machine - current this requires telling >>>> upstream+unmodified QEMU about this via >>>> -global spapr-pci-host-bridge.dma64_win_addr=0x100000000 >>>> or per-phb property. 4/4 advertises the new option but >>>> there is no automation around it in QEMU (should it be?). >>>> >>>> For now it is either 1<<59 or 4GB mode; dynamic switching is >>>> not supported (could be via sysfs). >>>> >>>> This is based on sha1 >>>> a6ed68d6468b Linus Torvalds "Merge tag 'drm-next-2019-11-27' of git://anongit.freedesktop.org/drm/drm". >>>> >>>> Please comment. Thanks. >>> >>> >>> David, Alistair, ping? Thanks, >> >> >>> >>> >>>> >>>> >>>> >>>> Alexey Kardashevskiy (4): >>>> powerpc/powernv/ioda: Rework for huge DMA window at 4GB >>>> powerpc/powernv/ioda: Allow smaller TCE table levels >>>> powerpc/powernv/phb4: Add 4GB IOMMU bypass mode >>>> vfio/spapr_tce: Advertise and allow a huge DMA windows at 4GB >>>> >>>> arch/powerpc/include/asm/iommu.h | 1 + >>>> arch/powerpc/include/asm/opal-api.h | 11 +- >>>> arch/powerpc/include/asm/opal.h | 2 + >>>> arch/powerpc/platforms/powernv/pci.h | 1 + >>>> include/uapi/linux/vfio.h | 2 + >>>> arch/powerpc/platforms/powernv/opal-call.c | 2 + >>>> arch/powerpc/platforms/powernv/pci-ioda-tce.c | 4 +- >>>> arch/powerpc/platforms/powernv/pci-ioda.c | 219 ++++++++++++++---- >>>> drivers/vfio/vfio_iommu_spapr_tce.c | 10 +- >>>> 9 files changed, 202 insertions(+), 50 deletions(-) >>>> >>> >> > -- Alexey
prev parent reply index Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-12-02 1:59 Alexey Kardashevskiy 2019-12-02 1:59 ` [PATCH kernel RFC 1/4] powerpc/powernv/ioda: Rework for " Alexey Kardashevskiy 2019-12-02 1:59 ` [PATCH kernel RFC 2/4] powerpc/powernv/ioda: Allow smaller TCE table levels Alexey Kardashevskiy 2019-12-02 1:59 ` [PATCH kernel RFC 3/4] powerpc/powernv/phb4: Add 4GB IOMMU bypass mode Alexey Kardashevskiy 2019-12-02 1:59 ` [PATCH kernel RFC 4/4] vfio/spapr_tce: Advertise and allow a huge DMA windows at 4GB Alexey Kardashevskiy 2019-12-02 5:36 ` [PATCH kernel RFC 0/4] powerpc/powenv/ioda: Allow huge DMA window " Alistair Popple 2019-12-02 5:58 ` Alexey Kardashevskiy 2019-12-02 5:51 ` [PATCH kernel RFC 00/4] powerpc/powernv/ioda: Move TCE bypass base to PE Alexey Kardashevskiy 2020-01-10 4:18 ` [PATCH kernel RFC 0/4] powerpc/powenv/ioda: Allow huge DMA window at 4GB Alexey Kardashevskiy 2020-01-23 0:53 ` Alexey Kardashevskiy 2020-01-23 1:17 ` David Gibson 2020-01-23 8:42 ` Alexey Kardashevskiy [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=df097089-5477-1aa9-cf79-07241579cb73@ozlabs.ru \ --to=aik@ozlabs.ru \ --cc=alex.williamson@redhat.com \ --cc=alistair@popple.id.au \ --cc=david@gibson.dropbear.id.au \ --cc=kvm@vger.kernel.org \ --cc=linuxppc-dev@lists.ozlabs.org \ --cc=oohall@gmail.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
KVM Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/kvm/0 kvm/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 kvm kvm/ https://lore.kernel.org/kvm \ kvm@vger.kernel.org public-inbox-index kvm Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.kvm AGPL code for this site: git clone https://public-inbox.org/public-inbox.git