From: David Gibson <david@gibson.dropbear.id.au>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Alex Williamson <alex.williamson@redhat.com>,
kvm@vger.kernel.org, Eric Auger <eric.auger@redhat.com>
Subject: Re: [RFC PATCH kernel] vfio-pci: Allow write combining
Date: Tue, 14 Nov 2017 13:23:50 +1100 [thread overview]
Message-ID: <20171114022350.GA20747@umbus.fritz.box> (raw)
In-Reply-To: <672c7172-addd-a0ca-f810-5a8deca67ff5@ozlabs.ru>
[-- Attachment #1: Type: text/plain, Size: 2283 bytes --]
On Mon, Nov 06, 2017 at 04:44:03PM +1100, Alexey Kardashevskiy wrote:
> On 16/10/17 19:01, David Gibson wrote:
> > On Mon, Oct 16, 2017 at 06:36:29PM +1100, Alexey Kardashevskiy wrote:
> >> On 16/10/17 17:00, David Gibson wrote:
> >>> On Mon, Oct 16, 2017 at 04:54:08PM +1100, Alexey Kardashevskiy wrote:
> >>>> On 12/10/17 02:35, Benjamin Herrenschmidt wrote:
> >>>>> On Wed, 2017-10-11 at 13:56 +1100, Alexey Kardashevskiy wrote:
> >>>>>> Oopsie. This is because I overlooked it. Others do not use it. So I do need
> >>>>>> a file. But in the current scheme where all BARs share one fd - it won't
> >>>>>> work - I simply cannot allow WC on non-prefetchable BARs :-/
> >>>>>
> >>>>> This is an oversight in the design of VFIO-PCI, it should have a way to
> >>>>> specify write combine, either implicitely via such an arch hook, or
> >>>>> explicitely via an ioctl prior to mapping the BARs for example.
> >>>>>
> >>>>> Alex, what do you reckon is the best approach here ?
> >>>>
> >>>> /me wonders if it is yet another issue for the dead issues bucket, just
> >>>> like the msix mapping one :)
> >>>
> >>> Maybe. Alexey, maybe you can make up a list of things that we (me,
> >>> you, BenH) need to discuss with Alex W at KVM Forum?
> >>
> >> "you" - you meant me? I am not coming over there :(
> >
> > Oh.. I thought you were.
> >
> >> The list is:
> >>
> >> 1. Allow msix mapping to the userspace (to address non-64k-aligned msix bar)
We have a new plan on this - I'll discuss it over IRC.
> >> 2. Allow write combining in vfio for the userspace (kvm guest is kinda
> >> special and may simply ignore mapping flags in some configs but PPC radix
> >> guests still rely on this)
AIUI this isn't for radix, but for DPDK things that we need this. Ben
talked about it a bit, but I don't know what the outcome was.
> >> 3. what callback and where needs to be added to inform HV/PR KVM about VFIO
> >> group, like IOMMUMR::add_vfio_group() proposal or something.
This was discussed, and I'm still thinking about it. It's kind of
curly.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-11-14 2:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 2:50 [RFC PATCH kernel] vfio-pci: Allow write combining Alexey Kardashevskiy
2017-10-10 21:55 ` Alex Williamson
2017-10-11 2:05 ` Alexey Kardashevskiy
2017-10-11 2:42 ` Alex Williamson
2017-10-11 2:56 ` Alexey Kardashevskiy
2017-10-11 15:35 ` Benjamin Herrenschmidt
2017-10-16 5:54 ` Alexey Kardashevskiy
2017-10-16 6:00 ` David Gibson
2017-10-16 7:36 ` Alexey Kardashevskiy
2017-10-16 8:01 ` David Gibson
2017-11-06 5:44 ` Alexey Kardashevskiy
2017-11-14 2:23 ` David Gibson [this message]
2017-11-14 2:29 ` Benjamin Herrenschmidt
2017-11-14 16:28 ` Alex Williamson
2017-11-24 4:58 ` Alexey Kardashevskiy
2017-11-29 18:47 ` Alex Williamson
2017-11-30 4:20 ` David Gibson
2017-11-30 20:06 ` Benjamin Herrenschmidt
2017-10-16 8:38 ` Benjamin Herrenschmidt
2017-10-16 11:11 ` Alexey Kardashevskiy
2017-10-18 7:33 ` Benjamin Herrenschmidt
2017-10-18 9:00 ` Alexey Kardashevskiy
2017-10-18 14:21 ` Benjamin Herrenschmidt
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=20171114022350.GA20747@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=eric.auger@redhat.com \
--cc=kvm@vger.kernel.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.