All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Andrii Anisov <andrii_anisov@epam.com>
Cc: xen-devel@lists.xenproject.org, julien.grall@arm.com,
	sstabellini@kernel.org, Andrii Anisov <andrii.anisov@gmail.com>
Subject: Re: [RFC 0/2] XEN SWIOTLB for ARM dma operations extension
Date: Wed, 11 Jan 2017 11:10:49 -0500	[thread overview]
Message-ID: <20170111161048.GH28754@char.us.oracle.com> (raw)
In-Reply-To: <c42c44cc-ed46-08fb-d122-dfd85323dce9@epam.com>

On Wed, Jan 11, 2017 at 06:09:03PM +0200, Andrii Anisov wrote:
> Dear Konrad,
> 
> Please see my comments below:
> > It would be good to have that as part of this patchset, otherwise
> > this is kind of non-compiling type patch.
> I'm not really sure what do you mean.

As in attaching an rework of the patch to this patchset.

> The patch I refer was done for LK 3.4 if I remember, it is not applicable to
> 4.6 I'm currently working with.
> Moreover xen-swiotlb infrastructure changed significantly so the patch is
> completely reworked. The only
> common code is that mmap is defined in ARM specific xen_swiotlb_dma_ops.
> I just refer to it and left author and signed-of-s as a respect to the work
> done few years ago.
> 
> > But more importantly, I think you need to also to take into account
> > Stefano's comments:
> I've encapsulated all the code changes in an arch/arm/xen/mm.c so I don't
> think your doubts and Stephano's comment
> about x86 build impact is relevant here.
> 
> -- 
> 
> *Andrii Anisov*
> 
> *Lead Systems Engineer*
> 
> *Office: *+380 44 390 5457 <tel:+380%2044%20390%205457> *x* 66766
> <tel:66766>*Cell: *+380 50 5738852 <tel:+380%2050%205738852>*Email:
> *andrii_anisov@epam.com <mailto:andrii_anisov@epam.com>
> 
> *Kyiv**,* *Ukraine *(GMT+3)*epam.com <http://www.epam.com>*
> 
> CONFIDENTIALITY CAUTION AND DISCLAIMER
> This message is intended only for the use of the individual(s) or
> entity(ies) to which it is addressed and contains information that is
> legally privileged and confidential. If you are not the intended recipient,
> or the person responsible for delivering the message to the intended
> recipient, you are hereby notified that any dissemination, distribution or
> copying of this communication is strictly prohibited. All unintended
> recipients are obliged to delete this message and destroy any printed
> copies.
> 

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

      reply	other threads:[~2017-01-11 16:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-10 16:44 [RFC 0/2] XEN SWIOTLB for ARM dma operations extension Andrii Anisov
2017-01-10 16:44 ` [RFC 1/2] swiotlb-xen: implement xen_swiotlb_dma_mmap callback Andrii Anisov
2017-01-10 16:44 ` [RFC 2/2] swiotlb-xen: implement xen_swiotlb_get_sgtable callback Andrii Anisov
2017-01-10 18:50 ` [RFC 0/2] XEN SWIOTLB for ARM dma operations extension Konrad Rzeszutek Wilk
2017-01-11 16:09   ` Andrii Anisov
2017-01-11 16:10     ` Konrad Rzeszutek Wilk [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=20170111161048.GH28754@char.us.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=andrii.anisov@gmail.com \
    --cc=andrii_anisov@epam.com \
    --cc=julien.grall@arm.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.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.