All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xensource.com>
To: "Langsdorf, Mark" <mark.langsdorf@amd.com>,
	xen-devel@lists.xensource.com
Subject: Re: [PATCH] Make x86_64 swiotlb code to support dma_ops [2/2]
Date: Wed, 28 Feb 2007 21:43:07 +0000	[thread overview]
Message-ID: <C20BA7EB.30A0%keir@xensource.com> (raw)
In-Reply-To: <1449F58C868D8D4E9C72945771150BDFD9668D@SAUSEXMB1.amd.com>

On 28/2/07 21:35, "Langsdorf, Mark" <mark.langsdorf@amd.com> wrote:

>> Other points that I can see from a quick browse include the fact that
>> alloc_coherent() still looks broken afaics
> 
> The i386 swiotlb implementation doesn't seem to have an
> alloc_coherent().  Since all this patch is intended to do
> is move swiotlb into the x86_64 directory, I'm not sure
> how to resolve the broken implementation.

By pulling in a new arch/x86_64/pci-dma-xen.c you are replacing the
implementations of things like dma_alloc_coherent(). These replacements,
being pretty much unmodified from the x86/64 native originals, simply aren't
going to work on Xen. I'm not sure how far we'll need to deviate -- I
suspect we'll end up with a file that look much like the i386/pci-dma-xen.c
but with calls to swiotlb_xxx() replaced with dma_ops->xxx. Maybe we could
even stick with just i386/pci-dma-xen.c and macro up the uses of
swiotlb_xxx() (so that they can be replaced with uses of dma_ops->xxx for
x86/64 by cpp).

 -- Keir

  reply	other threads:[~2007-02-28 21:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-28 20:17 [PATCH] Make x86_64 swiotlb code to support dma_ops [2/2] Langsdorf, Mark
2007-02-28 21:23 ` Keir Fraser
2007-02-28 21:35   ` Langsdorf, Mark
2007-02-28 21:43     ` Keir Fraser [this message]
2007-02-28 22:19       ` Langsdorf, Mark
2007-03-01  8:05         ` Jan Beulich

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=C20BA7EB.30A0%keir@xensource.com \
    --to=keir@xensource.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.