linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Christoph Hellwig <hch@lst.de>,
	linux-mm@kvack.org, linux-riscv@lists.infradead.org,
	will@kernel.org, m.szyprowski@samsung.com,
	linux-arch@vger.kernel.org, f.fainelli@gmail.com,
	frowand.list@gmail.com, devicetree@vger.kernel.org,
	Arnd Bergmann <arnd@arndb.de>,
	marc.zyngier@arm.com, robh+dt@kernel.org,
	linux-rpi-kernel@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org, phill@raspberryi.org,
	mbrugger@suse.com, eric@anholt.net, linux-kernel@vger.kernel.org,
	iommu@lists.linux-foundation.org, wahrenst@gmx.net,
	akpm@linux-foundation.org, Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH v2 01/11] asm-generic: add dma_zone_size
Date: Mon, 2 Sep 2019 15:01:01 +0200	[thread overview]
Message-ID: <20190902130101.GA2051@lst.de> (raw)
In-Reply-To: <bdeda2206b751a1c6a8d2e0732186792282633c6.camel@suse.de>

On Fri, Aug 30, 2019 at 07:24:25PM +0200, Nicolas Saenz Julienne wrote:
> I'll be happy to implement it that way. I agree it's a good compromise.
> 
> @Christoph, do you still want the patch where I create 'zone_dma_bits'? With a
> hardcoded ZONE_DMA it's not absolutely necessary. Though I remember you said it
> was a first step towards being able to initialize dma-direct's min_mask in
> meminit.

I do like the variable better than the current #define.  I wonder if
really want a mask or a max_zone_dma_address like variable.  So for this
series feel free to drop the patch.   I'll see if I'll pick it up
later or if we can find some way to automatically propagate that
information from the zone initialization.


  reply	other threads:[~2019-09-02 13:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190820145821.27214-1-nsaenzjulienne@suse.de>
     [not found] ` <20190820145821.27214-5-nsaenzjulienne@suse.de>
2019-08-20 17:14   ` [PATCH v2 04/11] of/fdt: add early_init_dt_get_dma_zone_size() Rob Herring
     [not found] ` <20190820145821.27214-4-nsaenzjulienne@suse.de>
2019-08-20 17:16   ` [PATCH v2 03/11] of/fdt: add of_fdt_machine_is_compatible function Rob Herring
2019-08-20 17:27     ` Nicolas Saenz Julienne
     [not found] ` <20190820145821.27214-11-nsaenzjulienne@suse.de>
2019-08-26  7:06   ` [PATCH v2 10/11] arm64: edit zone_dma_bits to fine tune dma-direct min mask Christoph Hellwig
2019-08-26 11:08     ` Nicolas Saenz Julienne
2019-08-27  7:03       ` Petr Tesarik
     [not found] ` <20190820145821.27214-12-nsaenzjulienne@suse.de>
2019-08-26  7:07   ` [PATCH v2 11/11] mm: refresh ZONE_DMA and ZONE_DMA32 comments in 'enum zone_type' Christoph Hellwig
     [not found] ` <20190820145821.27214-2-nsaenzjulienne@suse.de>
2019-08-26  7:09   ` [PATCH v2 01/11] asm-generic: add dma_zone_size Christoph Hellwig
2019-08-26 13:46     ` Nicolas Saenz Julienne
2019-08-28  9:44       ` Nicolas Saenz Julienne
2019-08-30 14:45       ` Catalin Marinas
2019-08-30 17:24         ` Nicolas Saenz Julienne
2019-09-02 13:01           ` Christoph Hellwig [this message]
     [not found] ` <20190820145821.27214-10-nsaenzjulienne@suse.de>
2019-08-26  7:05   ` [PATCH v2 09/11] dma-direct: turn ARCH_ZONE_DMA_BITS into a variable Christoph Hellwig
2019-08-26 11:33   ` Michael Ellerman

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=20190902130101.GA2051@lst.de \
    --to=hch@lst.de \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=eric@anholt.net \
    --cc=f.fainelli@gmail.com \
    --cc=frowand.list@gmail.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=m.szyprowski@samsung.com \
    --cc=marc.zyngier@arm.com \
    --cc=mbrugger@suse.com \
    --cc=nsaenzjulienne@suse.de \
    --cc=phill@raspberryi.org \
    --cc=robh+dt@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=wahrenst@gmx.net \
    --cc=will@kernel.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