On 03/23/2014 02:50 PM, KOSAKI Motohiro wrote:
> On Sun, Mar 23, 2014 at 1:26 PM, John Stultz wrote:
>> On Sun, Mar 23, 2014 at 10:50 AM, KOSAKI Motohiro
>> wrote:
+/**
+ * vrange_check_purged_pte - Checks ptes for purged pages
+ *
+ * Iterates over the ptes in the pmd
On 03/23/2014 02:50 PM, KOSAKI Motohiro wrote:
On Sun, Mar 23, 2014 at 1:26 PM, John Stultz john.stu...@linaro.org wrote:
On Sun, Mar 23, 2014 at 10:50 AM, KOSAKI Motohiro
kosaki.motoh...@gmail.com wrote:
+/**
+ * vrange_check_purged_pte - Checks ptes for purged pages
+ *
+ * Iterates over
On 04/07/2014 03:14 PM, KOSAKI Motohiro wrote:
>>> This change hwpoison and migration tag number. maybe ok, maybe not.
>> Though depending on config can't these tag numbers change anyway?
> I don't think distro disable any of these.
Well, it still shouldn't break if the config options are turned
>> This change hwpoison and migration tag number. maybe ok, maybe not.
>
> Though depending on config can't these tag numbers change anyway?
I don't think distro disable any of these.
>> I'd suggest to use younger number than hwpoison.
>> (That's why hwpoison uses younger number than migration)
On 03/23/2014 10:42 AM, KOSAKI Motohiro wrote:
> On Fri, Mar 21, 2014 at 2:17 PM, John Stultz wrote:
>> Users of volatile ranges will need to know if memory was discarded.
>> This patch adds the purged state tracking required to inform userland
>> when it marks memory as non-volatile that some
On 03/23/2014 10:42 AM, KOSAKI Motohiro wrote:
On Fri, Mar 21, 2014 at 2:17 PM, John Stultz john.stu...@linaro.org wrote:
Users of volatile ranges will need to know if memory was discarded.
This patch adds the purged state tracking required to inform userland
when it marks memory as
This change hwpoison and migration tag number. maybe ok, maybe not.
Though depending on config can't these tag numbers change anyway?
I don't think distro disable any of these.
I'd suggest to use younger number than hwpoison.
(That's why hwpoison uses younger number than migration)
So I
On 04/07/2014 03:14 PM, KOSAKI Motohiro wrote:
This change hwpoison and migration tag number. maybe ok, maybe not.
Though depending on config can't these tag numbers change anyway?
I don't think distro disable any of these.
Well, it still shouldn't break if the config options are turned off.
On Sun, Mar 23, 2014 at 1:26 PM, John Stultz wrote:
> On Sun, Mar 23, 2014 at 10:50 AM, KOSAKI Motohiro
> wrote:
>>> +/**
>>> + * vrange_check_purged_pte - Checks ptes for purged pages
>>> + *
>>> + * Iterates over the ptes in the pmd checking if they have
>>> + * purged swap entries.
>>> + *
On Sun, Mar 23, 2014 at 10:50 AM, KOSAKI Motohiro
wrote:
>> +/**
>> + * vrange_check_purged_pte - Checks ptes for purged pages
>> + *
>> + * Iterates over the ptes in the pmd checking if they have
>> + * purged swap entries.
>> + *
>> + * Sets the vrange_walker.pages_purged to 1 if any were
On Sun, Mar 23, 2014 at 5:29 AM, Jan Kara wrote:
> On Fri 21-03-14 14:17:32, John Stultz wrote:
>> + *
>> + * Sets the vrange_walker.pages_purged to 1 if any were purged.
> ^^^ page_was_purged
Doh. Thanks for catching this! Fixed in my tree.
Thanks so much for the
> +/**
> + * vrange_check_purged_pte - Checks ptes for purged pages
> + *
> + * Iterates over the ptes in the pmd checking if they have
> + * purged swap entries.
> + *
> + * Sets the vrange_walker.pages_purged to 1 if any were purged.
> + */
> +static int vrange_check_purged_pte(pmd_t *pmd,
On Fri, Mar 21, 2014 at 2:17 PM, John Stultz wrote:
> Users of volatile ranges will need to know if memory was discarded.
> This patch adds the purged state tracking required to inform userland
> when it marks memory as non-volatile that some memory in that range
> was purged and needs to be
On Fri 21-03-14 14:17:32, John Stultz wrote:
> Users of volatile ranges will need to know if memory was discarded.
> This patch adds the purged state tracking required to inform userland
> when it marks memory as non-volatile that some memory in that range
> was purged and needs to be regenerated.
On Fri 21-03-14 14:17:32, John Stultz wrote:
Users of volatile ranges will need to know if memory was discarded.
This patch adds the purged state tracking required to inform userland
when it marks memory as non-volatile that some memory in that range
was purged and needs to be regenerated.
On Fri, Mar 21, 2014 at 2:17 PM, John Stultz john.stu...@linaro.org wrote:
Users of volatile ranges will need to know if memory was discarded.
This patch adds the purged state tracking required to inform userland
when it marks memory as non-volatile that some memory in that range
was purged
+/**
+ * vrange_check_purged_pte - Checks ptes for purged pages
+ *
+ * Iterates over the ptes in the pmd checking if they have
+ * purged swap entries.
+ *
+ * Sets the vrange_walker.pages_purged to 1 if any were purged.
+ */
+static int vrange_check_purged_pte(pmd_t *pmd, unsigned long
On Sun, Mar 23, 2014 at 5:29 AM, Jan Kara j...@suse.cz wrote:
On Fri 21-03-14 14:17:32, John Stultz wrote:
+ *
+ * Sets the vrange_walker.pages_purged to 1 if any were purged.
^^^ page_was_purged
Doh. Thanks for catching this! Fixed in my tree.
Thanks so much
On Sun, Mar 23, 2014 at 10:50 AM, KOSAKI Motohiro
kosaki.motoh...@gmail.com wrote:
+/**
+ * vrange_check_purged_pte - Checks ptes for purged pages
+ *
+ * Iterates over the ptes in the pmd checking if they have
+ * purged swap entries.
+ *
+ * Sets the vrange_walker.pages_purged to 1 if any
On Sun, Mar 23, 2014 at 1:26 PM, John Stultz john.stu...@linaro.org wrote:
On Sun, Mar 23, 2014 at 10:50 AM, KOSAKI Motohiro
kosaki.motoh...@gmail.com wrote:
+/**
+ * vrange_check_purged_pte - Checks ptes for purged pages
+ *
+ * Iterates over the ptes in the pmd checking if they have
+ *
Users of volatile ranges will need to know if memory was discarded.
This patch adds the purged state tracking required to inform userland
when it marks memory as non-volatile that some memory in that range
was purged and needs to be regenerated.
This simplified implementation which uses some of
Users of volatile ranges will need to know if memory was discarded.
This patch adds the purged state tracking required to inform userland
when it marks memory as non-volatile that some memory in that range
was purged and needs to be regenerated.
This simplified implementation which uses some of
22 matches
Mail list logo
