From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: linux-mm@kvack.org
Subject: Re: [PATCH 7/8] vrange: Add method to purge volatile ranges
Date: Tue, 01 Oct 2013 16:00:27 +0200 [thread overview]
Message-ID: <1380636027.30613.1.camel@AMDC1943> (raw)
In-Reply-To: <20130619043419.GA10961@bbox>
Hi
On śro, 2013-06-19 at 13:34 +0900, Minchan Kim wrote:
> +int try_to_discard_one(struct vrange_root *vroot, struct page *page,
> + struct vm_area_struct *vma, unsigned long addr)
> +{
> + struct mm_struct *mm = vma->vm_mm;
> + pte_t *pte;
> + pte_t pteval;
> + spinlock_t *ptl;
> + int ret = 0;
> + bool present;
> +
> + VM_BUG_ON(!PageLocked(page));
> +
> + vrange_lock(vroot);
> + pte = vpage_check_address(page, mm, addr, &ptl);
> + if (!pte)
> + goto out;
> +
> + if (vma->vm_flags & VM_LOCKED) {
> + pte_unmap_unlock(pte, ptl);
> + goto out;
> + }
> +
> + present = pte_present(*pte);
> + flush_cache_page(vma, address, page_to_pfn(page));
Compilation error during porting to ARM:
s/address/addr
Best regards,
Krzysztof
--
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>
next prev parent reply other threads:[~2013-10-01 14:05 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 4:22 [PATCH 0/8] Volatile Ranges (v8?) John Stultz
2013-06-12 4:22 ` John Stultz
2013-06-12 4:22 ` [PATCH 1/8] vrange: Add basic data structure and functions John Stultz
2013-06-12 4:22 ` John Stultz
2013-06-12 4:22 ` [PATCH 2/8] vrange: Add vrange support for file address_spaces John Stultz
2013-06-12 4:22 ` John Stultz
2013-06-12 4:22 ` [PATCH 3/8] vrange: Add vrange support to mm_structs John Stultz
2013-06-12 4:22 ` John Stultz
2013-06-12 4:22 ` [PATCH 4/8] vrange: Clear volatility on new mmaps John Stultz
2013-06-12 4:22 ` John Stultz
2013-06-13 6:28 ` Minchan Kim
2013-06-13 6:28 ` Minchan Kim
2013-06-13 23:43 ` John Stultz
2013-06-13 23:43 ` John Stultz
2013-06-14 0:21 ` Minchan Kim
2013-06-14 0:21 ` Minchan Kim
2013-06-12 4:22 ` [PATCH 5/8] vrange: Add new vrange(2) system call John Stultz
2013-06-12 4:22 ` John Stultz
2013-06-12 6:48 ` NeilBrown
2013-06-12 18:47 ` John Stultz
2013-06-12 18:47 ` John Stultz
2013-06-20 21:05 ` Dhaval Giani
2013-06-20 21:05 ` Dhaval Giani
2013-06-12 4:22 ` [PATCH 6/8] vrange: Add GFP_NO_VRANGE allocation flag John Stultz
2013-06-12 4:22 ` John Stultz
2013-06-12 4:22 ` [PATCH 7/8] vrange: Add method to purge volatile ranges John Stultz
2013-06-12 4:22 ` John Stultz
2013-06-17 7:13 ` Minchan Kim
2013-06-17 7:13 ` Minchan Kim
2013-06-17 7:24 ` Minchan Kim
2013-06-17 7:24 ` Minchan Kim
2013-06-19 4:34 ` Minchan Kim
2013-06-19 4:34 ` Minchan Kim
2013-10-01 14:00 ` Krzysztof Kozlowski [this message]
2013-10-02 1:32 ` Minchan Kim
2013-06-12 4:22 ` [PATCH 8/8] vrange: Send SIGBUS when user try to access purged page John Stultz
2013-06-12 4:22 ` John Stultz
2013-06-19 4:36 ` Minchan Kim
2013-06-19 4:36 ` Minchan Kim
2013-06-17 16:24 ` [PATCH 0/8] Volatile Ranges (v8?) Dhaval Giani
2013-06-18 4:11 ` Minchan Kim
2013-06-18 4:11 ` Minchan Kim
2013-06-18 16:59 ` Dhaval Giani
2013-06-18 16:59 ` Dhaval Giani
2013-06-19 4:41 ` Minchan Kim
2013-06-19 4:41 ` Minchan Kim
2013-06-19 18:36 ` Dhaval Giani
2013-06-19 18:36 ` Dhaval Giani
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=1380636027.30613.1.camel@AMDC1943 \
--to=k.kozlowski@samsung.com \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.