linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Mark" <markk@clara.co.uk>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
	akpm@linux-foundation.org, Rik van Riel <riel@redhat.com>,
	linux-nvdimm@ml01.01.org,
	Dave Hansen <dave.hansen@linux.intel.com>,
	linux-kernel@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
	linux-mm@kvack.org, Ingo Molnar <mingo@redhat.com>,
	Mel Gorman <mgorman@suse.de>, "H. Peter Anvin" <hpa@zytor.com>,
	Jerome Glisse <j.glisse@gmail.com>
Subject: Re: [RFC PATCH] mm: support CONFIG_ZONE_DEVICE + CONFIG_ZONE_DMA
Date: Tue, 26 Jan 2016 19:10:51 -0000	[thread overview]
Message-ID: <f210f47beb9713da6ca43bac792cdbbf.squirrel@ssl-webmail-vh.clara.net> (raw)
In-Reply-To: <20160126060028.GB2053@sudip-laptop>

On Tue, January 26, 2016 06:00, Sudip Mukherjee wrote:
> On Mon, Jan 25, 2016 at 04:06:40PM -0800, Dan Williams wrote:
>> It appears devices requiring ZONE_DMA are still prevalent (see link
>> below).  For this reason the proposal to require turning off ZONE_DMA to
>> enable ZONE_DEVICE is untenable in the short term.  We want a single
>> kernel image to be able to support legacy devices as well as next
>> generation persistent memory platforms.
>>
>> Towards this end, alias ZONE_DMA and ZONE_DEVICE to work around needing
>> to maintain a unique zone number for ZONE_DEVICE.  Record the geometry
>> of ZONE_DMA at init (->init_spanned_pages) and use that information in
>> is_zone_device_page() to differentiate pages allocated via
>> devm_memremap_pages() vs true ZONE_DMA pages.  Otherwise, use the
>> simpler definition of is_zone_device_page() when ZONE_DMA is turned off.
>>
>> Note that this also teaches the memory hot remove path that the zone may
>> not have sections for all pfn spans (->zone_dyn_start_pfn).
>>
>> A user visible implication of this change is potentially an unexpectedly
>> high "spanned" value in /proc/zoneinfo for the DMA zone.
>>
>> Cc: H. Peter Anvin <hpa@zytor.com>
>> Cc: Ingo Molnar <mingo@redhat.com>
>> Cc: Rik van Riel <riel@redhat.com>
>> Cc: Mel Gorman <mgorman@suse.de>
>> Cc: Jerome Glisse <j.glisse@gmail.com>
>> Cc: Christoph Hellwig <hch@lst.de>
>> Cc: Dave Hansen <dave.hansen@linux.intel.com>
>> Link: https://bugzilla.kernel.org/show_bug.cgi?id=110931
>> Fixes: 033fbae988fc ("mm: ZONE_DEVICE for "device memory"")
>> Reported-by: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
>
> It should actually be Reported-by: Mark <markk@clara.co.uk>
>
> Hi Mark,
> Can you please test this patch available at
> https://patchwork.kernel.org/patch/8116991/
> in your setup..

I applied that patch to 4.5-rc1 and it seems to work. At least, there is
no error message in dmesg output any more. I didn't actually try using the
parallel port (need to find a parallel printer cable). Presumably a
parallel printer would work whether DMA is used or not, just slower and
using more CPU time in the PIO case. Also, I don't have any hardware that
needs CONFIG_ZONE_DEVICE.

The config file I used to compile the kernel can be downloaded from
https://www.mediafire.com/?1do33bkko41ypo3
if anyone feels like taking a look.

Perhaps someone with one of the affected PCI sound cards could also test
the patch, since those presumably don't work/build at all without it.
Hopefully someone else has a PC with native parallel port to confirm the
fix. (Native floppy controller may be another affected device.)


Mark


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2016-01-26 19:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-26  0:06 Dan Williams
2016-01-26  6:00 ` Sudip Mukherjee
2016-01-26 17:07   ` Dan Williams
2016-01-26 19:10   ` Mark [this message]
2016-01-26 21:42 ` Vlastimil Babka
2016-01-26 21:48   ` Dan Williams
2016-01-26 22:11 ` Andrew Morton
2016-01-26 22:33   ` Dan Williams
2016-01-26 22:51     ` Andrew Morton
2016-01-26 23:11       ` Dan Williams
2016-01-27  1:18         ` Joonsoo Kim
2016-01-27  1:37           ` Dan Williams
2016-01-27  2:15             ` Joonsoo Kim
2016-01-27  3:23               ` Dan Williams
2016-01-27  3:52                 ` Joonsoo Kim
2016-01-27  4:26                   ` Dan Williams
2016-01-27  5:52                     ` Joonsoo Kim
2016-01-27  7:46             ` Mel Gorman

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=f210f47beb9713da6ca43bac792cdbbf.squirrel@ssl-webmail-vh.clara.net \
    --to=markk@clara.co.uk \
    --cc=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=hch@lst.de \
    --cc=hpa@zytor.com \
    --cc=j.glisse@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-nvdimm@ml01.01.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=riel@redhat.com \
    --cc=sudipm.mukherjee@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox