From: Gerd Hoffmann <kraxel@redhat.com>
To: Muli Ben-Yehuda <muli@il.ibm.com>
Cc: Amit Shah <amit.shah@qumranet.com>,
kvm-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [kvm-devel] [PATCH 3/8] KVM: PVDMA Guest: Guest-side routines for paravirtualized DMA
Date: Mon, 12 Nov 2007 15:53:59 +0100 [thread overview]
Message-ID: <47386907.5080101@redhat.com> (raw)
In-Reply-To: <20071112105001.GF3299@rhun.haifa.ibm.com>
Muli Ben-Yehuda wrote:
> On Wed, Nov 07, 2007 at 04:21:04PM +0200, Amit Shah wrote:
>
>> We make the dma_mapping_ops structure to point to our structure so
>> that every DMA access goes through us. (This is the reason this only
>> works for 64-bit guest. 32-bit guest doesn't yet have a dma_ops
>> struct.)
>
> I need the same facility for Calgary for falling back to swiotlb if a
> translation is disabled on some slot, and IB needs the same facility
> for some IB adapters (e.g., ipath). Perhaps it's time to consider
> stackable dma-ops (unless someone has a better idea...).
Hmm, at least the later sounds like for per-device dma_ops would be more
useful that stackable ones, as each stack instance just checks "should I
do something for device $foo, if not, call the next one ...".
cheers,
Gerd
WARNING: multiple messages have this Message-ID (diff)
From: Gerd Hoffmann <kraxel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Muli Ben-Yehuda <muli-7z/5BgaJwgfQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 3/8] KVM: PVDMA Guest: Guest-side routines for paravirtualized DMA
Date: Mon, 12 Nov 2007 15:53:59 +0100 [thread overview]
Message-ID: <47386907.5080101@redhat.com> (raw)
In-Reply-To: <20071112105001.GF3299-WD1JZD8MxeCTrf4lBMg6DdBPR1lH4CV8@public.gmane.org>
Muli Ben-Yehuda wrote:
> On Wed, Nov 07, 2007 at 04:21:04PM +0200, Amit Shah wrote:
>
>> We make the dma_mapping_ops structure to point to our structure so
>> that every DMA access goes through us. (This is the reason this only
>> works for 64-bit guest. 32-bit guest doesn't yet have a dma_ops
>> struct.)
>
> I need the same facility for Calgary for falling back to swiotlb if a
> translation is disabled on some slot, and IB needs the same facility
> for some IB adapters (e.g., ipath). Perhaps it's time to consider
> stackable dma-ops (unless someone has a better idea...).
Hmm, at least the later sounds like for per-device dma_ops would be more
useful that stackable ones, as each stack instance just checks "should I
do something for device $foo, if not, call the next one ...".
cheers,
Gerd
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-11-12 14:54 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 14:21 RFC: Paravirtualized DMA accesses for KVM Amit Shah
2007-11-07 14:21 ` Amit Shah
2007-11-07 14:21 ` [PATCH 1/8] KVM: PVDMA Host: Handle reqeusts for guest DMA mappings Amit Shah
2007-11-07 14:21 ` Amit Shah
2007-11-07 14:21 ` Amit Shah
2007-11-07 14:21 ` [PATCH 2/8] KVM: Move #include asm/kvm_para.h outside of __KERNEL__ Amit Shah
2007-11-07 14:21 ` Amit Shah
2007-11-07 14:21 ` Amit Shah
2007-11-07 14:21 ` [PATCH 3/8] KVM: PVDMA Guest: Guest-side routines for paravirtualized DMA Amit Shah
2007-11-07 14:21 ` Amit Shah
2007-11-07 14:21 ` Amit Shah
2007-11-12 10:50 ` [kvm-devel] " Muli Ben-Yehuda
2007-11-12 10:50 ` Muli Ben-Yehuda
2007-11-12 11:56 ` [kvm-devel] " Amit Shah
2007-11-12 11:56 ` Amit Shah
2007-11-12 13:32 ` [kvm-devel] " Muli Ben-Yehuda
2007-11-12 13:32 ` Muli Ben-Yehuda
2007-11-12 13:55 ` [kvm-devel] " Amit Shah
2007-11-12 13:55 ` Amit Shah
2007-11-12 14:01 ` [kvm-devel] " Muli Ben-Yehuda
2007-11-12 14:01 ` Muli Ben-Yehuda
2007-11-12 14:53 ` Gerd Hoffmann [this message]
2007-11-12 14:53 ` Gerd Hoffmann
2007-11-12 16:00 ` [kvm-devel] " Joerg Roedel
2007-11-12 16:00 ` Joerg Roedel
2007-11-07 14:21 ` [PATCH 4/8] KVM: PVDMA: Introduce is_pv_device() dma operation Amit Shah
2007-11-07 14:21 ` Amit Shah
2007-11-07 14:21 ` Amit Shah
2007-11-12 10:52 ` [kvm-devel] " Muli Ben-Yehuda
2007-11-12 10:52 ` Muli Ben-Yehuda
2007-11-07 14:21 ` [PATCH 5/8] KVM: PVDMA: Update dma_alloc_coherent to make it paravirt-aware Amit Shah
2007-11-07 14:21 ` Amit Shah
2007-11-07 14:21 ` Amit Shah
2007-11-12 10:56 ` [kvm-devel] " Muli Ben-Yehuda
2007-11-12 10:56 ` Muli Ben-Yehuda
2007-11-12 11:59 ` [kvm-devel] " Amit Shah
2007-11-12 11:59 ` Amit Shah
2007-11-07 14:21 ` [PATCH 6/8] KVM: PVDMA Guest: Add Makefile rule Amit Shah
2007-11-07 14:21 ` Amit Shah
2007-11-07 14:21 ` Amit Shah
2007-11-07 14:21 ` [PATCH 7/8] PVDMA: Guest: Add Kconfig options to select PVDMA Amit Shah
2007-11-07 14:21 ` Amit Shah
2007-11-07 14:21 ` Amit Shah
2007-11-07 14:21 ` [PATCH 8/8] KVM: Update drivers/Makefile to check for CONFIG_VIRTUALIZATION Amit Shah
2007-11-07 14:21 ` Amit Shah
2007-11-07 14:21 ` Amit Shah
2007-11-12 15:55 ` [kvm-devel] [PATCH 1/8] KVM: PVDMA Host: Handle reqeusts for guest DMA mappings Joerg Roedel
2007-11-12 15:55 ` Joerg Roedel
2007-11-12 17:07 ` [kvm-devel] " Amit Shah
2007-11-12 17:07 ` Amit Shah
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=47386907.5080101@redhat.com \
--to=kraxel@redhat.com \
--cc=amit.shah@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=muli@il.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.