From: Andy King <acking@vmware.com>
To: gregkh@linuxfoundation.org
Cc: pv-drivers@vmware.com, David Miller <davem@davemloft.net>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 0/2] VMCI: Add support for virtual IOMMU
Date: Wed, 21 Aug 2013 06:43:38 -0700 (PDT) [thread overview]
Message-ID: <1988970649.33605490.1377092618300.JavaMail.root@vmware.com> (raw)
In-Reply-To: <1377019803-1490-1-git-send-email-acking@vmware.com>
Greg,
I'd like to withdraw this in light of DaveM's comments on
a similar patch to vmxnet3 regarding dma_alloc_coherent() vs
pci_alloc_consistent(). I'll fix it and send out a new patchset.
Sorry about this!
Thanks!
- Andy
----- Original Message -----
> This patchset adds support for virtual IOMMU to the VMCI module. We switch
> to
> DMA consistent mappings for queuepair and doorbell pages that are passed to
> the
> device, which allows the module to work in the presence of vIOMMU/VT-d.
>
> Andy King (2):
> VMCI: Remove non-blocking/pinned queuepair support
> VMCI: Add support for virtual IOMMU
>
> drivers/misc/vmw_vmci/vmci_driver.c | 2 +-
> drivers/misc/vmw_vmci/vmci_driver.h | 7 +
> drivers/misc/vmw_vmci/vmci_guest.c | 21 ++-
> drivers/misc/vmw_vmci/vmci_queue_pair.c | 312
> ++++++++++++-------------------
> drivers/misc/vmw_vmci/vmci_queue_pair.h | 18 --
> 5 files changed, 140 insertions(+), 220 deletions(-)
>
> --
> 1.7.4.1
>
next prev parent reply other threads:[~2013-08-21 13:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 17:30 [PATCH 0/2] VMCI: Add support for virtual IOMMU Andy King
2013-08-20 17:30 ` [PATCH 1/2] VMCI: Remove non-blocking/pinned queuepair support Andy King
2013-08-20 17:30 ` [PATCH 2/2] VMCI: Add support for virtual IOMMU Andy King
2013-08-21 13:43 ` Andy King [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-08-23 16:22 [PATCH 0/2] " Andy King
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=1988970649.33605490.1377092618300.JavaMail.root@vmware.com \
--to=acking@vmware.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pv-drivers@vmware.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).