On 05.12.18 01:26, Dan Williams wrote:
On Tue, Dec 4, 2018 at 4:01 PM Alexander Duyck
> On Tue, 2018-12-04 at 18:24 -0500, Barret Rhoden wrote:
>> Hi -
>> On 2018-12-04 at 14:51 Alexander Duyck
>> <alexander.h.duyck(a)linux.intel.com> wrote:
>>>> I think the confusion arises from the fact that there are a few MMIO
>>>> resources with a struct page and all the rest MMIO resources without.
>>>> The problem comes from the coarse definition of pfn_valid(), it may
>>>> return 'true' for things that are not System-RAM, because
>>>> may be something as simplistic as a single "address < X"
>>>> PageReserved is a fallback to clarify the pfn_valid() result. The
>>>> typical case is that MMIO space is not caught up in this linear map
>>>> confusion. An MMIO address may or may not have an associated 'struct
>>>> page' and in most cases it does not.
>>> Okay. I think I understand this somewhat now. So the page might be
>>> physically there, but with the reserved bit it is not supposed to be
>>> My main concern with just dropping the bit is that we start seeing some
>>> other uses that I was not certain what the impact would be. For example
>>> the functions like kvm_set_pfn_accessed start going in and manipulating
>>> things that I am not sure should be messed with for a DAX page.
>> One thing regarding the accessed and dirty bits is that we might want
>> to have DAX pages marked dirty/accessed, even if we can't LRU-reclaim
>> or swap them. I don't have a real example and I'm fairly ignorant
>> about the specifics here. But one possibility would be using the A/D
>> bits to detect changes to a guest's memory for VM migration. Maybe
>> there would be issues with KSM too.
> I get that, but the issue is that the code associated with those bits
> currently assumes you are working with either an anonymous swap backed
> page or a page cache page. We should really be updating that logic now,
> and then enabling DAX to access it rather than trying to do things the
> other way around which is how this feels.
Agree. I understand the concern about unintended side effects of
dropping PageReserved for dax pages, but they simply don't fit the
definition of the intended use of PageReserved. We've already had
fallout from legacy code paths doing the wrong thing with dax pages
where PageReserved wouldn't have helped. For example, see commit
6e2608dfd934 "xfs, dax: introduce xfs_dax_aops", or commit
6100e34b2526 "mm, memory_failure: Teach memory_failure() about
dev_pagemap pages". So formerly teaching kvm about these page
semantics and dropping the reliance on a side effect of PageReserved()
seems the right direction.
That said, for mark_page_accessed(), it does not look like it will
have any effect on dax pages. PageLRU will be false,
__lru_cache_activate_page() will not find a page on a percpu pagevec,
and workingset_activation() won't find an associated memcg. I would
not be surprised if mark_page_accessed() is already being called today
via the ext4 + dax use case.
I agree to what Dan says here. I'd vote for getting rid of the
PageReserved bit for these pages and rather fixing the fallout from that
(if any, I also doubt that there will be much). One thing I already
mentioned in another thread is hindering hibernation code from touching
ZONE_DEVICE memory is one thing to take care of.
PageReserved as part of a user space process can mean many things (and I
still have a patch pending for submission to document that). It can mean
zero pages, VDSO pages, MMIO pages and right now DAX pages. For the
first three, we don't want to touch the struct page ever
(->PageReserved). For DAX it should not harm (-> no need for PageReserved).
David / dhildenb