From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: Pankaj Gupta <pankaj.gupta.linux@gmail.com>,
Shivaprasad G Bhat <sbhat@linux.ibm.com>
Cc: ellerman@au1.ibm.com, linux-nvdimm <linux-nvdimm@lists.01.org>,
linuxppc-dev@lists.ozlabs.org, kvm-ppc@vger.kernel.org
Subject: Re: [RFC PATCH] powerpc/papr_scm: Implement scm async flush
Date: Tue, 1 Dec 2020 18:27:36 +0530 [thread overview]
Message-ID: <20035bbc-a1e0-82fd-105d-999e1afff029@linux.ibm.com> (raw)
In-Reply-To: <CAM9Jb+iPV470063QYq145znYW8CmqjNgdL=q6=3JXUJJt+z5gw@mail.gmail.com>
On 12/1/20 6:17 PM, Pankaj Gupta wrote:
>> Tha patch implements SCM async-flush hcall and sets the
>> ND_REGION_ASYNC capability when the platform device tree
>> has "ibm,async-flush-required" set.
>
> So, you are reusing the existing ND_REGION_ASYNC flag for the
> hypercall based async flush with device tree discovery?
>
> Out of curiosity, does virtio based flush work in ppc? Was just thinking
> if we can reuse virtio based flush present in virtio-pmem? Or anything
> else we are trying to achieve here?
>
Not with PAPR based pmem driver papr_scm.ko. The devices there are
considered platform device and we use hypercalls to configure the
device. On similar fashion we are now using hypercall to flush the host
based caches.
-aneesh
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org
WARNING: multiple messages have this Message-ID (diff)
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: Pankaj Gupta <pankaj.gupta.linux@gmail.com>,
Shivaprasad G Bhat <sbhat@linux.ibm.com>
Cc: ellerman@au1.ibm.com, linuxppc-dev@lists.ozlabs.org,
kvm-ppc@vger.kernel.org, linux-nvdimm <linux-nvdimm@lists.01.org>
Subject: Re: [RFC PATCH] powerpc/papr_scm: Implement scm async flush
Date: Tue, 1 Dec 2020 18:27:36 +0530 [thread overview]
Message-ID: <20035bbc-a1e0-82fd-105d-999e1afff029@linux.ibm.com> (raw)
In-Reply-To: <CAM9Jb+iPV470063QYq145znYW8CmqjNgdL=q6=3JXUJJt+z5gw@mail.gmail.com>
On 12/1/20 6:17 PM, Pankaj Gupta wrote:
>> Tha patch implements SCM async-flush hcall and sets the
>> ND_REGION_ASYNC capability when the platform device tree
>> has "ibm,async-flush-required" set.
>
> So, you are reusing the existing ND_REGION_ASYNC flag for the
> hypercall based async flush with device tree discovery?
>
> Out of curiosity, does virtio based flush work in ppc? Was just thinking
> if we can reuse virtio based flush present in virtio-pmem? Or anything
> else we are trying to achieve here?
>
Not with PAPR based pmem driver papr_scm.ko. The devices there are
considered platform device and we use hypercalls to configure the
device. On similar fashion we are now using hypercall to flush the host
based caches.
-aneesh
WARNING: multiple messages have this Message-ID (diff)
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: Pankaj Gupta <pankaj.gupta.linux@gmail.com>,
Shivaprasad G Bhat <sbhat@linux.ibm.com>
Cc: ellerman@au1.ibm.com, linux-nvdimm <linux-nvdimm@lists.01.org>,
linuxppc-dev@lists.ozlabs.org, kvm-ppc@vger.kernel.org
Subject: Re: [RFC PATCH] powerpc/papr_scm: Implement scm async flush
Date: Tue, 01 Dec 2020 13:09:36 +0000 [thread overview]
Message-ID: <20035bbc-a1e0-82fd-105d-999e1afff029@linux.ibm.com> (raw)
In-Reply-To: <CAM9Jb+iPV470063QYq145znYW8CmqjNgdL=q6=3JXUJJt+z5gw@mail.gmail.com>
On 12/1/20 6:17 PM, Pankaj Gupta wrote:
>> Tha patch implements SCM async-flush hcall and sets the
>> ND_REGION_ASYNC capability when the platform device tree
>> has "ibm,async-flush-required" set.
>
> So, you are reusing the existing ND_REGION_ASYNC flag for the
> hypercall based async flush with device tree discovery?
>
> Out of curiosity, does virtio based flush work in ppc? Was just thinking
> if we can reuse virtio based flush present in virtio-pmem? Or anything
> else we are trying to achieve here?
>
Not with PAPR based pmem driver papr_scm.ko. The devices there are
considered platform device and we use hypercalls to configure the
device. On similar fashion we are now using hypercall to flush the host
based caches.
-aneesh
next prev parent reply other threads:[~2020-12-01 12:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 12:18 [RFC PATCH] powerpc/papr_scm: Implement scm async flush Shivaprasad G Bhat
2020-12-01 12:18 ` Shivaprasad G Bhat
2020-12-01 12:18 ` Shivaprasad G Bhat
2020-12-01 12:47 ` Pankaj Gupta
2020-12-01 12:47 ` Pankaj Gupta
2020-12-01 12:47 ` Pankaj Gupta
2020-12-01 12:57 ` Aneesh Kumar K.V [this message]
2020-12-01 13:09 ` Aneesh Kumar K.V
2020-12-01 12:57 ` Aneesh Kumar K.V
2020-12-01 13:02 ` Pankaj Gupta
2020-12-01 13:02 ` Pankaj Gupta
2020-12-01 13:02 ` Pankaj Gupta
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=20035bbc-a1e0-82fd-105d-999e1afff029@linux.ibm.com \
--to=aneesh.kumar@linux.ibm.com \
--cc=ellerman@au1.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=pankaj.gupta.linux@gmail.com \
--cc=sbhat@linux.ibm.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 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.