From: Jon Mason <jdmason@us.ibm.com>
To: "Langsdorf, Mark" <mark.langsdorf@amd.com>
Cc: "Muli Ben-Yehuda (IBM)" <MULI@il.ibm.com>, xen-devel@lists.xensource.com
Subject: Re: Using arch/x86_64/pci-dma in x86_64 Xen
Date: Thu, 4 May 2006 11:18:02 -0500 [thread overview]
Message-ID: <20060504161802.GA14361@us.ibm.com> (raw)
In-Reply-To: <84EA05E2CA77634C82730353CBE3A84303218C70@SAUSEXMB1.amd.com>
On Thu, May 04, 2006 at 09:57:35AM -0500, Langsdorf, Mark wrote:
> The current implementation of pci-dma in x86_64 Xen
> Linux is to use the i386 implementation. I don't
> believe this is sustainable in the long term, as
> x86_64 Xen is going to need more DMA solutions than
> just SWIOTLB and plain hardware as various IOMMU
> implementations arrive.
>
> The mainstream kernel has a clean abstraction layer
> with the dma_ops that should be portable to Xen dom0
> and domU. I've started implementing this in a
> pci-dma-xen for x86_64 Xen Linux. Am I stepping on
> anyone's toes or is there anyone I should be
> co-ordinating this with?
This is long overdue. Thanks for starting the work.
Muli and I have been peripherally looking at this, but have not done any
work on it yet. Please keep us in the loop, and let us know if you need
any help :)
Thanks,
Jon
>
> -Mark Langsdorf
> AMD, Inc.
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2006-05-04 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-04 14:57 Using arch/x86_64/pci-dma in x86_64 Xen Langsdorf, Mark
2006-05-04 16:18 ` Jon Mason [this message]
2006-05-07 12:19 ` Muli Ben-Yehuda
2006-05-07 19:45 ` Christian Limpach
-- strict thread matches above, loose matches on Subject: below --
2006-05-08 13:31 Langsdorf, Mark
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=20060504161802.GA14361@us.ibm.com \
--to=jdmason@us.ibm.com \
--cc=MULI@il.ibm.com \
--cc=mark.langsdorf@amd.com \
--cc=xen-devel@lists.xensource.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.