From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: linux-s390 <linux-s390@vger.kernel.org>,
Joerg Roedel <jroedel@suse.de>, KVM <kvm@vger.kernel.org>,
Michael Tsirkin <mst@redhat.com>,
benh@kernel.crashing.org,
Sebastian Ott <sebott@linux.vnet.ibm.com>,
virtualization@lists.linux-foundation.org,
Andy Lutomirski <luto@kernel.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
dwmw2@infradead.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 3/3] s390/dma: Allow per device dma ops
Date: Thu, 5 Nov 2015 10:33:41 +0100 [thread overview]
Message-ID: <563B2275.3010406@de.ibm.com> (raw)
In-Reply-To: <20151103132615.53002e05.cornelia.huck@de.ibm.com>
Am 03.11.2015 um 13:26 schrieb Cornelia Huck:
> On Tue, 3 Nov 2015 12:54:39 +0100
> Christian Borntraeger <borntraeger@de.ibm.com> wrote:
>
>> As virtio-ccw now has dma ops, we can no longer default to the PCI ones.
>> Make use of dev_archdata to keep the dma_ops per device. The pci devices
>> now use that to override the default, and the default is changed to use
>> the noop ops for everything that is not PCI. To compile without PCI
>> support we also have to enable the DMA api with virtio.
>
> Not only with virtio, but generally, right?
Yes, will update the patch description.
>
>> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
>> Reviewed-by: Joerg Roedel <jroedel@suse.de>
>> Acked-by: Sebastian Ott <sebott@linux.vnet.ibm.com>
>> ---
>> arch/s390/Kconfig | 3 ++-
>> arch/s390/include/asm/device.h | 6 +++++-
>> arch/s390/include/asm/dma-mapping.h | 6 ++++--
>> arch/s390/pci/pci.c | 1 +
>> arch/s390/pci/pci_dma.c | 4 ++--
>> 5 files changed, 14 insertions(+), 6 deletions(-)
>>
>> diff --git a/arch/s390/Kconfig b/arch/s390/Kconfig
>> index 1d57000..04f0e02 100644
>> --- a/arch/s390/Kconfig
>> +++ b/arch/s390/Kconfig
>> @@ -113,6 +113,7 @@ config S390
>> select GENERIC_FIND_FIRST_BIT
>> select GENERIC_SMP_IDLE_THREAD
>> select GENERIC_TIME_VSYSCALL
>> + select HAS_DMA
>> select HAVE_ALIGNED_STRUCT_PAGE if SLUB
>> select HAVE_ARCH_AUDITSYSCALL
>> select HAVE_ARCH_EARLY_PFN_TO_NID
>> @@ -124,6 +125,7 @@ config S390
>> select HAVE_CMPXCHG_DOUBLE
>> select HAVE_CMPXCHG_LOCAL
>> select HAVE_DEBUG_KMEMLEAK
>> + select HAVE_DMA_ATTRS
>> select HAVE_DYNAMIC_FTRACE
>> select HAVE_DYNAMIC_FTRACE_WITH_REGS
>> select HAVE_FTRACE_MCOUNT_RECORD
>> @@ -580,7 +582,6 @@ config QDIO
>>
>> menuconfig PCI
>> bool "PCI support"
>> - select HAVE_DMA_ATTRS
>> select PCI_MSI
>> help
>> Enable PCI support.
>
> Hm. Further down in this file, there's
>
> config HAS_DMA
> def_bool PCI
> select HAVE_DMA_API_DEBUG
>
> Should we maybe select HAVE_DMA_API_DEBUG above, drop the HAS_DMA
> config option and rely on not defining NO_DMA instead?
Hmm, yes. That would simplify things a lot. Right now we include
lib/Kconfig (which defines HAS_DMA) and define it ourselfes in
arch/s390/Kconfig. WHoever comes first wins. Adding a select statement
would make this even more complicated.
Andy, I will simply send you a respin of this patch.
next prev parent reply other threads:[~2015-11-05 9:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1446551679-33492-1-git-send-email-borntraeger@de.ibm.com>
2015-11-03 11:54 ` [PATCH 1/3] dma: Provide simple noop dma ops Christian Borntraeger
2015-11-05 13:31 ` Joerg Roedel
2015-11-03 11:54 ` [PATCH 2/3] alpha/dma: use common " Christian Borntraeger
2015-11-03 11:54 ` [PATCH 3/3] s390/dma: Allow per device " Christian Borntraeger
[not found] ` <1446551679-33492-4-git-send-email-borntraeger@de.ibm.com>
2015-11-03 12:26 ` Cornelia Huck
2015-11-05 9:33 ` Christian Borntraeger [this message]
2015-11-05 19:22 ` Andy Lutomirski
2015-10-30 13:20 [PATCHv2 0/3] dma ops and virtio Christian Borntraeger
2015-10-30 13:20 ` [PATCH 3/3] s390/dma: Allow per device dma ops Christian Borntraeger
[not found] ` <1446211237-111298-4-git-send-email-borntraeger@de.ibm.com>
2015-11-02 15:21 ` Joerg Roedel
2015-11-02 16:38 ` Sebastian Ott
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=563B2275.3010406@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=cornelia.huck@de.ibm.com \
--cc=dwmw2@infradead.org \
--cc=hch@lst.de \
--cc=jroedel@suse.de \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=schwidefsky@de.ibm.com \
--cc=sebott@linux.vnet.ibm.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).