From: Andi Kleen <andi@firstfloor.org>
To: Amit Shah <amit.shah@qumranet.com>
Cc: kvm-devel@lists.sourceforge.net, chrisw@redhat.com,
allen.m.kay@intel.com, linux-kernel@vger.kernel.org,
gcosta@redhat.com, avi@qumranet.com,
virtualization@lists.linux-foundation.org, BENAMI@il.ibm.com
Subject: Re: [PATCH] x86 DMA: Handle devices assigned to the guest by the host
Date: Tue, 29 Apr 2008 15:14:23 +0200 [thread overview]
Message-ID: <87wsmghkgg.fsf@basil.nowhere.org> (raw)
In-Reply-To: <1209465451-3758-2-git-send-email-amit.shah@qumranet.com> (Amit Shah's message of "Tue, 29 Apr 2008 13:37:29 +0300")
Amit Shah <amit.shah@qumranet.com> writes:
> diff --git a/arch/x86/kernel/pci-dma.c b/arch/x86/kernel/pci-dma.c
> index 388b113..678cafb 100644
> --- a/arch/x86/kernel/pci-dma.c
> +++ b/arch/x86/kernel/pci-dma.c
> @@ -443,6 +443,17 @@ dma_alloc_coherent(struct device *dev, size_t size, dma_addr_t *dma_handle,
> memset(memory, 0, size);
> if (!mmu) {
> *dma_handle = bus;
> + if (unlikely(dma_ops->is_pv_device) &&
> + unlikely(dma_ops->is_pv_device(dev, dev->bus_id))) {
First double unlikely in a condition is useless. Just drop them.
And then ->is_xyz() in a generic vops interface is about as ugly
and non generic as you can get. dma_alloc_coherent is not performance
critical, so you should rather change the interface that ->alloc_coherent
is always called and the other handlers handle the !mmu case correctly.
In fact they need that already I guess (e.g. on DMAR there is not really
a nommu case)
-Andi
next prev parent reply other threads:[~2008-04-29 13:15 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 10:37 PV DMA for PCI passthrough devices for KVM Amit Shah
2008-04-29 10:37 ` Amit Shah
2008-04-29 10:37 ` [PATCH] x86 DMA: Handle devices assigned to the guest by the host Amit Shah
2008-04-29 10:37 ` Amit Shah
2008-04-29 10:37 ` [PATCH] KVM x86: Handle hypercalls for assigned PCI devices Amit Shah
2008-04-29 10:37 ` Amit Shah
2008-04-29 10:37 ` Amit Shah
2008-04-29 10:37 ` [PATCH] KVM PV Guest: Implement paravirtualized DMA Amit Shah
2008-04-29 10:37 ` Amit Shah
2008-04-29 13:31 ` Andi Kleen
2008-04-29 13:31 ` Andi Kleen
2008-04-29 13:59 ` Amit Shah
2008-04-29 13:59 ` Amit Shah
2008-04-29 10:37 ` Amit Shah
2008-04-29 14:44 ` [PATCH] KVM x86: Handle hypercalls for assigned PCI devices Glauber Costa
2008-04-29 14:44 ` Glauber Costa
2008-04-29 15:58 ` Amit Shah
2008-04-29 22:48 ` Avi Kivity
2008-04-29 22:48 ` Avi Kivity
2008-04-29 22:48 ` Avi Kivity
2008-04-30 6:05 ` Muli Ben-Yehuda
2008-04-30 6:05 ` Muli Ben-Yehuda
2008-04-30 6:05 ` Muli Ben-Yehuda
2008-05-01 13:18 ` Amit Shah
2008-05-01 13:18 ` Amit Shah
2008-05-01 13:18 ` Amit Shah
2008-04-29 15:58 ` Amit Shah
2008-04-29 13:14 ` [PATCH] x86 DMA: Handle devices assigned to the guest by the host Andi Kleen
2008-04-29 13:14 ` Andi Kleen [this message]
2008-04-29 13:49 ` Amit Shah
2008-04-29 13:49 ` Amit Shah
2008-04-30 6:29 ` Muli Ben-Yehuda
2008-04-30 6:29 ` Muli Ben-Yehuda
2008-04-29 10:37 ` Amit Shah
2008-04-29 13:15 ` PV DMA for PCI passthrough devices for KVM Andi Kleen
2008-04-29 13:15 ` Andi Kleen
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=87wsmghkgg.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=BENAMI@il.ibm.com \
--cc=allen.m.kay@intel.com \
--cc=amit.shah@qumranet.com \
--cc=avi@qumranet.com \
--cc=chrisw@redhat.com \
--cc=gcosta@redhat.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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.