From: Thomas Monjalon <thomas@monjalon.net>
To: Takeshi Yoshimura <tyos@jp.ibm.com>
Cc: dev@dpdk.org, David Christensen <drc@linux.vnet.ibm.com>,
Burakov@dpdk.org, Anatoly <anatoly.burakov@intel.com>,
David Christensen <drc@ibm.com>,
Pradeep Satyanarayana <pradeep@us.ibm.com>
Subject: Re: [dpdk-dev] [PATCH v3] vfio: fix expanding DMA area in ppc64le
Date: Tue, 16 Jul 2019 12:56:52 +0200 [thread overview]
Message-ID: <2496149.faZSPxUDDV@xps> (raw)
In-Reply-To: <5b04e7ba-1778-db57-0b87-825f765605bd@linux.vnet.ibm.com>
16/07/2019 02:20, David Christensen:
> > In ppc64le, expanding DMA areas always fail because we cannot remove
> > a DMA window. As a result, we cannot allocate more than one memseg in
> > ppc64le. This is because vfio_spapr_dma_mem_map() doesn't unmap all
> > the mapped DMA before removing the window. This patch fixes this
> > incorrect behavior.
> >
> > I also fixed the order of ioctl for unregister and unmap. The ioctl
> > for unregister sometimes report device busy errors due to the
> > existence of mapped area.
> >
> > Signed-off-by: Takeshi Yoshimura <tyos@jp.ibm.com>
> > ---
> Acked-by: David Christensen <drc@linux.vnet.ibm.com>
Applied, thanks
next prev parent reply other threads:[~2019-07-16 10:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 6:33 [dpdk-dev] [PATCH] vfio: fix expanding DMA area in ppc64le Takeshi Yoshimura
2019-06-12 14:06 ` Aaron Conole
2019-06-13 2:22 ` Takeshi Yoshimura
2019-06-18 2:37 ` Mo, YufengX
2019-06-13 2:30 ` Takeshi T Yoshimura
2019-06-13 17:37 ` David Christensen
2019-06-14 7:34 ` David Marchand
2019-06-14 7:49 ` [dpdk-dev] [PATCH v2] " Takeshi Yoshimura
2019-07-13 1:15 ` [dpdk-dev] [PATCH v3] " Takeshi Yoshimura
2019-07-16 0:20 ` David Christensen
2019-07-16 10:56 ` Thomas Monjalon [this message]
2019-06-18 2:39 ` [dpdk-dev] [PATCH] " Mo, YufengX
2019-06-26 9:43 ` Burakov, Anatoly
2019-06-28 11:38 ` Takeshi T Yoshimura
2019-06-28 13:47 ` Burakov, Anatoly
2019-06-28 14:04 ` Burakov, Anatoly
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=2496149.faZSPxUDDV@xps \
--to=thomas@monjalon.net \
--cc=Burakov@dpdk.org \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=drc@ibm.com \
--cc=drc@linux.vnet.ibm.com \
--cc=pradeep@us.ibm.com \
--cc=tyos@jp.ibm.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
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.