From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Alexander Graf <agraf@suse.com>,
Liu ping fan <kernelfans@gmail.com>,
Alexander Graf <agraf@suse.de>
Cc: linuxppc-dev@lists.ozlabs.org, kvm-ppc <kvm-ppc@vger.kernel.org>,
kvm-devel <kvm@vger.kernel.org>,
Ben Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH v2] powernv: kvm: make _PAGE_NUMA take effect
Date: Mon, 07 Apr 2014 07:54:29 +0000 [thread overview]
Message-ID: <87bnwdshzu.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <533D47CD.906@suse.com>
Alexander Graf <agraf@suse.com> writes:
> On 03.04.14 04:36, Liu ping fan wrote:
>> Hi Alex, could you help to pick up this patch? since v3.14 kernel can
>> enable numa fault for powerpc.
>
> What bad happens without this patch? We map a page even though it was
> declared to get NUMA migrated? What happens next?
Nothing much, we won't be properly accounting the numa access in the
host. What we want to achieve is to convert a guest access of the page to
a host fault so that we can do proper numa access accounting in the
host. This would enable us to migrate the page to the correct numa
node.
>
> I'm trying to figure out whether I need to mark this with a stable tag
> for 3.14.
>
>
-aneesh
WARNING: multiple messages have this Message-ID (diff)
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Alexander Graf <agraf@suse.com>,
Liu ping fan <kernelfans@gmail.com>,
Alexander Graf <agraf@suse.de>
Cc: Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org, kvm-devel <kvm@vger.kernel.org>,
kvm-ppc <kvm-ppc@vger.kernel.org>
Subject: Re: [PATCH v2] powernv: kvm: make _PAGE_NUMA take effect
Date: Mon, 07 Apr 2014 13:12:29 +0530 [thread overview]
Message-ID: <87bnwdshzu.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <533D47CD.906@suse.com>
Alexander Graf <agraf@suse.com> writes:
> On 03.04.14 04:36, Liu ping fan wrote:
>> Hi Alex, could you help to pick up this patch? since v3.14 kernel can
>> enable numa fault for powerpc.
>
> What bad happens without this patch? We map a page even though it was
> declared to get NUMA migrated? What happens next?
Nothing much, we won't be properly accounting the numa access in the
host. What we want to achieve is to convert a guest access of the page to
a host fault so that we can do proper numa access accounting in the
host. This would enable us to migrate the page to the correct numa
node.
>
> I'm trying to figure out whether I need to mark this with a stable tag
> for 3.14.
>
>
-aneesh
WARNING: multiple messages have this Message-ID (diff)
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Alexander Graf <agraf@suse.com>,
Liu ping fan <kernelfans@gmail.com>,
Alexander Graf <agraf@suse.de>
Cc: linuxppc-dev@lists.ozlabs.org, kvm-ppc <kvm-ppc@vger.kernel.org>,
kvm-devel <kvm@vger.kernel.org>,
Ben Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH v2] powernv: kvm: make _PAGE_NUMA take effect
Date: Mon, 07 Apr 2014 13:12:29 +0530 [thread overview]
Message-ID: <87bnwdshzu.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <533D47CD.906@suse.com>
Alexander Graf <agraf@suse.com> writes:
> On 03.04.14 04:36, Liu ping fan wrote:
>> Hi Alex, could you help to pick up this patch? since v3.14 kernel can
>> enable numa fault for powerpc.
>
> What bad happens without this patch? We map a page even though it was
> declared to get NUMA migrated? What happens next?
Nothing much, we won't be properly accounting the numa access in the
host. What we want to achieve is to convert a guest access of the page to
a host fault so that we can do proper numa access accounting in the
host. This would enable us to migrate the page to the correct numa
node.
>
> I'm trying to figure out whether I need to mark this with a stable tag
> for 3.14.
>
>
-aneesh
next prev parent reply other threads:[~2014-04-07 7:54 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 8:15 [PATCH v2] powernv: kvm: make _PAGE_NUMA take effect Liu Ping Fan
2014-01-21 8:15 ` Liu Ping Fan
2014-01-21 8:15 ` Liu Ping Fan
2014-01-21 9:42 ` Aneesh Kumar K.V
2014-01-21 9:54 ` Aneesh Kumar K.V
2014-01-21 9:42 ` Aneesh Kumar K.V
2014-01-27 9:11 ` Alexander Graf
2014-01-27 9:11 ` Alexander Graf
2014-01-27 9:11 ` Alexander Graf
2014-01-27 10:28 ` Aneesh Kumar K.V
2014-01-27 10:40 ` Aneesh Kumar K.V
2014-01-27 10:28 ` Aneesh Kumar K.V
2014-01-27 10:42 ` Alexander Graf
2014-01-27 10:42 ` Alexander Graf
2014-01-27 10:42 ` Alexander Graf
2014-01-27 15:57 ` Aneesh Kumar K.V
2014-01-27 15:57 ` Aneesh Kumar K.V
2014-01-27 15:57 ` Aneesh Kumar K.V
2014-01-27 10:41 ` Paul Mackerras
2014-01-27 10:41 ` Paul Mackerras
2014-01-27 10:41 ` Paul Mackerras
2014-04-03 2:36 ` Liu ping fan
2014-04-03 2:36 ` Liu ping fan
2014-04-03 2:36 ` Liu ping fan
2014-04-03 11:36 ` Alexander Graf
2014-04-03 11:36 ` Alexander Graf
2014-04-03 11:36 ` Alexander Graf
2014-04-03 11:38 ` Alexander Graf
2014-04-03 11:38 ` Alexander Graf
2014-04-03 11:38 ` Alexander Graf
2014-04-03 11:43 ` Alexander Graf
2014-04-03 11:43 ` Alexander Graf
2014-04-03 11:43 ` Alexander Graf
2014-04-07 7:42 ` Aneesh Kumar K.V [this message]
2014-04-07 7:54 ` Aneesh Kumar K.V
2014-04-07 7:42 ` Aneesh Kumar K.V
2014-04-07 8:36 ` Alexander Graf
2014-04-07 8:36 ` Alexander Graf
2014-04-07 8:36 ` Alexander Graf
2014-04-10 3:28 ` Liu ping fan
2014-04-10 3:28 ` Liu ping fan
2014-04-10 3:28 ` Liu ping fan
2014-04-10 10:02 ` Alexander Graf
2014-04-10 10:02 ` Alexander Graf
2014-04-10 10:02 ` Alexander Graf
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=87bnwdshzu.fsf@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=agraf@suse.com \
--cc=agraf@suse.de \
--cc=benh@kernel.crashing.org \
--cc=kernelfans@gmail.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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.