[RESEND PATCH v7 0/5] powerpc/papr_scm: Add support for reporting nvdimm health
by Vaibhav Jain
The PAPR standard[1][3] provides mechanisms to query the health and
performance stats of an NVDIMM via various hcalls as described in
Ref[2]. Until now these stats were never available nor exposed to the
user-space tools like 'ndctl'. This is partly due to PAPR platform not
having support for ACPI and NFIT. Hence 'ndctl' is unable to query and
report the dimm health status and a user had no way to determine the
current health status of a NDVIMM.
To overcome this limitation, this patch-set updates papr_scm kernel
module to query and fetch NVDIMM health stats using hcalls described
in Ref[2]. This health and performance stats are then exposed to
userspace via sysfs and PAPR-NVDIMM-Specific-Methods(PDSM) issued by
libndctl.
These changes coupled with proposed ndtcl changes located at Ref[4]
should provide a way for the user to retrieve NVDIMM health status
using ndtcl.
Below is a sample output using proposed kernel + ndctl for PAPR NVDIMM
in a emulation environment:
# ndctl list -DH
[
{
"dev":"nmem0",
"health":{
"health_state":"fatal",
"shutdown_state":"dirty"
}
}
]
Dimm health report output on a pseries guest lpar with vPMEM or HMS
based NVDIMMs that are in perfectly healthy conditions:
# ndctl list -d nmem0 -H
[
{
"dev":"nmem0",
"health":{
"health_state":"ok",
"shutdown_state":"clean"
}
}
]
PAPR NVDIMM-Specific-Methods(PDSM)
==================================
PDSM requests are issued by vendor specific code in libndctl to
execute certain operations or fetch information from NVDIMMS. PDSMs
requests can be sent to papr_scm module via libndctl(userspace) and
libnvdimm (kernel) using the ND_CMD_CALL ioctl command which can be
handled in the dimm control function papr_scm_ndctl(). Current
patchset proposes a single PDSM to retrieve NVDIMM health, defined in
the newly introduced uapi header named 'papr_scm_pdsm.h'. Support for
more PDSMs will be added in future.
Structure of the patch-set
==========================
The patch-set starts with a doc patch documenting details of hcall
H_SCM_HEALTH. Second patch exports kernel symbol seq_buf_printf()
thats used in subsequent patches to generate sysfs attribute content.
Third patch implements support for fetching NVDIMM health information
from PHYP and partially exposing it to user-space via a NVDIMM sysfs
flag.
Fourth patches deal with implementing support for servicing PDSM
commands in papr_scm module.
Finally the last patch implements support for servicing PDSM
'PAPR_SCM_PDSM_HEALTH' that returns the NVDIMM health information to
libndctl.
Changelog:
==========
Resend:
* Added ack from Steven Rostedt on Patch-2 that exports kernel symbol
seq_buf_printf()
v6..v7:
* Incorporate various review comments from Mpe. Removed papr_scm.h
* Added a patch to export seq_buf_printf() [Mpe, Steven Rostedt]
* header file and moved its contents to papr_scm.c.
* Split function drc_pmem_query_health() into two functions, one that takes
care of caching and concurrency and other one that doesn't.
* Fixed a possible incorrect way to make local copy of nvdimm health data.
* Some variable renames changed as suggested in previous review.
* Removed unused macros/defines from papr_scm_pdsm.h
* Updated papr_scm_pdsm.h to remove usage of __KERNEL__ define.
* Updated papr_scm_pdsm.h to remove redefinition of __packed macro.
v5..v6:
* Incorporate review comments from Mpe and Dan Williams.
* Changed the usage of term DSM to PDSM as former conflicted with
usage in ACPI context.
* UAPI updates to remove usage of bool and marking the structs
defined as 'packed'.
* Simplified the health-bitmap handling in papr_scm to use u64
instead of __be64 integers.
* Caching of the health information so reading the dimm-flag file
doesn't result in costly hcalls everytime.
* Changed dimm-flag 'save_fail' to 'flush_fail'
* Moved the dimm flag file from 'papr_flags' to 'papr/flags'.
* Added a patch to document H_SCM_HEALTH hcall return values.
* Added sysfs ABI documentation for newly introduce dimm-flag
sysfs file 'papr/flags'
v4..v5:
* Fixed a bug in new implementation of papr_scm_ndctl() that was triggering
a false error condition.
v3..v4:
* Restructured papr_scm_ndctl() to dispatch ND_CMD_CALL commands to a new
function named papr_scm_service_dsm() to serivice DSM requests. [Aneesh]
v2..v3:
* Updated the papr_scm_dsm.h header to be more confimant general kernel
guidelines for UAPI headers. [Aneesh]
* Changed the definition of macro PAPR_SCM_DIMM_UNARMED_MASK to not
include case when the NVDIMM is unarmed because its a vPMEM
NVDIMM. [Aneesh]
v1..v2:
* Restructured the patch-set based on review comments on V1 patch-set to
simplify the patch review. Multiple small patches have been combined into
single patches to reduce cross referencing that was needed in earlier
patch-set. Hence most of the patches in this patch-set as now new. [Aneesh]
* Removed the initial work done for fetch NVDIMM performance statistics.
These changes will be re-proposed in a separate patch-set. [Aneesh]
* Simplified handling of versioning of 'struct
nd_papr_scm_dimm_health_stat_v1' as only one version of the structure is
currently in existence.
References:
[1] "Power Architecture Platform Reference"
https://en.wikipedia.org/wiki/Power_Architecture_Platform_Reference
[2] commit 58b278f568f0
("powerpc: Provide initial documentation for PAPR hcalls")
[3] "Linux on Power Architecture Platform Reference"
https://members.openpowerfoundation.org/document/dl/469
[4] https://github.com/vaibhav92/ndctl/tree/papr_scm_health_v7
Vaibhav Jain (5):
powerpc: Document details on H_SCM_HEALTH hcall
seq_buf: Export seq_buf_printf() to external modules
powerpc/papr_scm: Fetch nvdimm health information from PHYP
ndctl/papr_scm,uapi: Add support for PAPR nvdimm specific methods
powerpc/papr_scm: Implement support for PAPR_SCM_PDSM_HEALTH
Documentation/ABI/testing/sysfs-bus-papr-scm | 27 ++
Documentation/powerpc/papr_hcalls.rst | 43 ++-
arch/powerpc/include/uapi/asm/papr_scm_pdsm.h | 173 +++++++++
arch/powerpc/platforms/pseries/papr_scm.c | 363 +++++++++++++++++-
include/uapi/linux/ndctl.h | 1 +
lib/seq_buf.c | 1 +
6 files changed, 595 insertions(+), 13 deletions(-)
create mode 100644 Documentation/ABI/testing/sysfs-bus-papr-scm
create mode 100644 arch/powerpc/include/uapi/asm/papr_scm_pdsm.h
--
2.26.2
6 months
Good day,
by Caroline Edward
Good day,
Am Caroline Edward, a staff Sergeant in the US Army presently serving in Syria as a combat instructor, I sincerely apologize for intruding into your privacy, this might come as a surprise to you, but nothing is more distressing to me at this time as i find myself forced by events beyond my control, i have summoned courage to contact you. Am 45 years old lady, am a widow and I had a son who is now 16 years of age.
Some money in various currencies where discovered in barrels at a farm house in the middle East during a rescue operation in Iraq War,and it was agreed by Staff Sergeant Kenneth Buff and myself that some part of these money be shared between both of us, I was given a total of ($5 Million US Dollars) as my own share , I kept this money in a consignment for a long while with a security Company which i declared and deposit as my personal effects and it has been secured and protected for years now with the diplomatic Delivery Service.
Now, the WAR in Iraq is over, and all possible problems that could have emanated from the shared money has been totally cleaned up and all file closed, all what was discovered in the Middle East is no more discussed, am now ready to retire from active services, but, i need a trustworthy person that can help me take possession of this funds and keep it safe while i work on my relief letters to join you so that we could discuss possible business partnership together with the money.
But I tell you what! No compensation can make up for the risk we are taken with our lives.You can confirm the genuineness of the findings by clicking on this web site: http://news.bbc.co.uk/2/hi/middle_east/2988455.stm
I’m seeking your kind assistance to move the sum of US$5 Million Dollars to you as far as I can be assured that the money will be safe in your care until I complete my service here in (SYRIA) before the end of the month. The most important thing is; “Can I Trust you”?,As an officers on ACTIVE DUTY am not allowed access to money, therefore, i have declared the content of the consignment as personal effect that i would like to be delivered to a friend. You will be rewarded with 30% of this funds for your help, all that i required is your trust between us till the money get to you.
Sincerely,
Sgt. Caroline Edward.
Email: mrs.carolineedward(a)gmail.com
6 months
[PATCH] nvdimm: fixes to maintainter-entry-profile
by Randy Dunlap
From: Randy Dunlap <rdunlap(a)infradead.org>
Fix punctuation and wording in a few places.
Signed-off-by: Randy Dunlap <rdunlap(a)infradead.org>
Cc: Dan Williams <dan.j.williams(a)intel.com>
Cc: Vishal Verma <vishal.l.verma(a)intel.com>
Cc: Dave Jiang <dave.jiang(a)intel.com>
Cc: Ira Weiny <ira.weiny(a)intel.com>
Cc: linux-nvdimm(a)lists.01.org
Cc: Jonathan Corbet <corbet(a)lwn.net>
Cc: linux-doc(a)vger.kernel.org
---
Documentation/nvdimm/maintainer-entry-profile.rst | 14 ++++++------
1 file changed, 7 insertions(+), 7 deletions(-)
--- linux-next-20200521.orig/Documentation/nvdimm/maintainer-entry-profile.rst
+++ linux-next-20200521/Documentation/nvdimm/maintainer-entry-profile.rst
@@ -4,15 +4,15 @@ LIBNVDIMM Maintainer Entry Profile
Overview
--------
The libnvdimm subsystem manages persistent memory across multiple
-architectures. The mailing list, is tracked by patchwork here:
+architectures. The mailing list is tracked by patchwork here:
https://patchwork.kernel.org/project/linux-nvdimm/list/
...and that instance is configured to give feedback to submitters on
patch acceptance and upstream merge. Patches are merged to either the
-'libnvdimm-fixes', or 'libnvdimm-for-next' branch. Those branches are
+'libnvdimm-fixes' or 'libnvdimm-for-next' branch. Those branches are
available here:
https://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm.git/
-In general patches can be submitted against the latest -rc, however if
+In general patches can be submitted against the latest -rc; however, if
the incoming code change is dependent on other pending changes then the
patch should be based on the libnvdimm-for-next branch. However, since
persistent memory sits at the intersection of storage and memory there
@@ -35,12 +35,12 @@ getting the test environment set up.
ACPI Device Specific Methods (_DSM)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Before patches enabling for a new _DSM family will be considered it must
+Before patches enabling a new _DSM family will be considered, it must
be assigned a format-interface-code from the NVDIMM Sub-team of the ACPI
Specification Working Group. In general, the stance of the subsystem is
-to push back on the proliferation of NVDIMM command sets, do strongly
+to push back on the proliferation of NVDIMM command sets, so do strongly
consider implementing support for an existing command set. See
-drivers/acpi/nfit/nfit.h for the set of support command sets.
+drivers/acpi/nfit/nfit.h for the set of supported command sets.
Key Cycle Dates
@@ -48,7 +48,7 @@ Key Cycle Dates
New submissions can be sent at any time, but if they intend to hit the
next merge window they should be sent before -rc4, and ideally
stabilized in the libnvdimm-for-next branch by -rc6. Of course if a
-patch set requires more than 2 weeks of review -rc4 is already too late
+patch set requires more than 2 weeks of review, -rc4 is already too late
and some patches may require multiple development cycles to review.
6 months
block I/O accounting improvements
by Christoph Hellwig
Hi Jens,
they series contains various improvement for block I/O accounting. The
first bunch of patches switch the bio based drivers to better accounting
helpers compared to the current mess. The end contains a fix and various
performanc improvements. Most of this comes from a series Konstantin
sent a few weeks ago, rebased on changes that landed in your tree since
and my change to always use the percpu version of the disk stats.
6 months
Invitation to Bid
by RFQ Bid
Good day,
The municipality would like to extend an invitation to your company to supply the attached product(s). Some of the product(s) that we may request may fall out of your scope of work,
Therefore we would like you to outsource for the product(s) and supply the Municipality as we are urgently looking for a reliable supplier to supply us.
Warm regards
Mark Sumner
Global Supply Chain Manager
Tel: +44 2037 409718
Fax:+44 2037 409728
ADDRESS: UNILEVER HOUSE SPRINGFIELD
DRIVE LEATHER HEAD KT22 7GR
E-mail: quote(a)unileverchainsupply.co.uk
6 months
Your opérating systém has béen hackéd by cybércriminals. Changé thé authorization méthod.
by kwilken＠cooperativeplus.com
Héllo!
I'm a programmér who crackéd your émail account and dévicé about half yéar ago.
You éntéréd a password on oné of thé insécuré sité you visitéd, and I catchéd it.
Of coursé you can will changé your password, or alréady madé it.
But it doésn't mattér, my rat softwaré updaté it évéry timé.
Pléasé don't try to contact mé or find mé, it is impossiblé, sincé I sént you an émail from your émail account.
Through your é-mail, I uploadéd malicious codé to your Opération Systém.
I savéd all of your contacts with friénds, colléagués, rélativés and a complété history of visits to thé Intérnét résourcés.
Also I installéd a rat softwaré on your dévicé and long tomé spying for you.
You aré not my only victim, I usually lock dévicés and ask for a ransom.
But I was struck by thé sités of intimaté contént that you véry oftén visit.
I am in shock of your réach fantasiés! Wow! I'vé névér séén anything liké this!
I did not évén know that SUCH contént could bé so éxciting!
So, whén you had marturbate on intimé sités (you know what I méan!)
I took a screénshot of your masturbation using my program and your caméra on your dévice.
Aftér that, I jointéd thém to thé contént of thé curréntly viéwéd sité.
Will bé funny whén I sénd thésé photos to your contacts! And if your rélativés séé it?
BUT I'm suré you don't want it. I définitély would not want to ...
I will not do this if you pay mé a littlé amount.
I think $972 is a nicé pricé for it!
I accépt only Bitcoins.
My BTC wallét: 16KfJgmrHrKWS54EjTzgYa3cTmHM8QGHyw
If you havé difficulty with this - Ask Googlé "how to maké a paymént on a bitcoin wallét". It's éasy.
Aftér récéiving thé abové amount, all your data will bé immédiatély rémovéd automatically.
My virus will also will bé déstroy itsélf from your opérating systém.
My Trojan havé auto alért, aftér this émail is lookéd, I will bé know it!
You havé 2 days (48 hours) for maké a paymént.
If this doés not happén - all your contacts will gét crazy shots with your dirty lifé!
And so that you do not obstruct mé, your dévicé will bé lockéd (also aftér 48 hours)
Do not také this frivolously! This is thé last warning!
Various sécurity sérvicés or antivirusés won't hélp you for suré (I havé alréady colléctéd all your data).
Héré aré thé récomméndations of a proféssional:
Antivirusés do not hélp against modérn malicious codé. Just do not éntér your passwords on unsafé sités!
I hopé you will bé prudént.
Byé.
6 months
linux-nvdimm@lists.01.org Covid/Pay/2020/ Covid Relief Fund
by Covid Relief Fund
linux-nvdimm(a)lists.01.org Covid/Pay/2020/ Covid Relief Fund
The world banks is making available $400,000 via the
International Monetary fund as financial support aid for
individuals globally.This is due to the current global corona
virus pandemic.
Your email is selected in a category ''A'' beneficiary program.To
claim the funds ,provide your full name with this code
Covid/Pay/2020/ to the email address provided below..
Stay safe.
Andrew Tweedie
Finance Department Director
International Monetary Fund(IMF)
CORONA RELIEF FUND.
TEL:+1 917 382 1952
covidofficeincc(a)barid.com
6 months
jjCompliment
by mrs chantal
Compliment of the day to you. I am Mrs.CHANTAL I am sending this brief
letter to solicit your partnership to transfer $13.5 Million US
Dollars.I shall send you more information and procedures when I receive
positive response From you. Please send me a message in My private
email address is ( mrschantal066(a)gmail.com )
Best Regards
MrS.Chantal
6 months
