All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yasunori Goto <y-goto@jp.fujitsu.com>
To: Linda Knippers <linda.knippers@hpe.com>
Cc: linux-nvdimm@lists.01.org
Subject: Re: Standardization of ACPI NVDIMM DSMs
Date: Mon, 10 Jul 2017 17:16:51 +0900	[thread overview]
Message-ID: <20170710171649.731E.E1E9C6FF@jp.fujitsu.com> (raw)
In-Reply-To: <d77f5643-7cd2-8f0f-02b7-118d0305e547@hpe.com>


> > 2) I suppose a notification daemon may be necessary to inform the over
> >     threshold event  (to syslog, to other servers, or logging management OSS, etc....)
> >
> >     Please correct me, if ndctl has this feature already...
> 
> That feature doesn't exist in ndctl.  Intel has developed some tools that are
> mostly specific to their NVDIMMs and those tools include a monitoring daemon as
> well as a CLI.
> https://github.com/01org/ixpdimm_sw

Though I tried to compile this tools, I could not comple it, and 
I gave up to solve too many dependency... 

> 
> One approach could be to contribute changes to make those tools more useful for non-Intel NVDIMMs.

Hmmm, ixpdimm_sw seems to be too large software.
In my first impression, I don't think this is good way..... :(

>   Another approach could be to integrate NVDIMM event
> monitoring into some other utility, like the rasdaemon.  I'm interested in
> your thoughts.

Though I'm not sure which (existing or new) utility is appropriate yet.
I prefer this way. So, I'll think about it.

> 
> >> If you're thinking of defining something new, I encourage you to get
> >> involved in the standards activities.
> >
> > If my idea is useful like the aboves, the standard activity looks quite interesting
> > for me. Please tell me how to join it.
> 
> If your company is part of the UEFI Forum then I think you can participate in
> the ACPI working group.  There is a sub-team focused on standardizing NVDIMM
> FW/SW interfaces.  My suggestion is that you find the person in your company
> who can hook you up with the right group.

Ok, I'll try to find the contact person in my company.

> 
> You'll also see conversation/debate about what ought to be a standard
> on this mailing list so input here is welcome too.

I see.
Thank you for your information.

Bye,
---
Yasunori Goto


_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

  reply	other threads:[~2017-07-10  8:15 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-28 15:40 Standardization of ACPI NVDIMM DSMs Rebecca Cran
2017-06-28 15:59 ` Linda Knippers
2017-06-28 18:46   ` Rebecca Cran
2017-06-30  1:18   ` Yasunori Goto
2017-06-30 15:19     ` Linda Knippers
2017-07-03  4:53       ` Yasunori Goto
2017-07-06 14:22         ` Linda Knippers
2017-07-10  8:16           ` Yasunori Goto [this message]
2017-07-24  5:50             ` Daemon of NVDIMM event notification/monitoring(Re: Standardization of ACPI NVDIMM DSMs) Yasunori Goto
2017-07-24 16:11               ` Dan Williams
2017-07-26 17:45                 ` Dan Williams
2017-07-27  1:52                   ` Yasunori Goto
2017-07-26 17:51                 ` Christoph Hellwig
2017-07-26 19:34                   ` Dan Williams
2017-08-09 14:19               ` Jeff Moyer
2017-08-09 18:30                 ` Dan Williams
2017-08-09 19:00                   ` Linda Knippers
2017-08-09 20:49                     ` Dan Williams
2017-08-16  2:25                       ` Yasunori Goto
2017-07-08  4:10         ` Standardization of ACPI NVDIMM DSMs Dan Williams
2017-07-10  8:51           ` Yasunori Goto

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=20170710171649.731E.E1E9C6FF@jp.fujitsu.com \
    --to=y-goto@jp.fujitsu.com \
    --cc=linda.knippers@hpe.com \
    --cc=linux-nvdimm@lists.01.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.