From: Linda Knippers <linda.knippers@hpe.com>
To: "Verma, Vishal L" <vishal.l.verma@intel.com>,
"Williams, Dan J" <dan.j.williams@intel.com>,
"toshi.kani@hpe.com" <toshi.kani@hpe.com>
Cc: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
"jmoyer@redhat.com" <jmoyer@redhat.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"elliott@hpe.com" <elliott@hpe.com>,
"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>
Subject: Re: [RFC PATCH] Fix _FIT vs. NFIT processing breakage
Date: Thu, 19 Nov 2015 15:16:37 -0500 [thread overview]
Message-ID: <564E2E25.2050705@hpe.com> (raw)
In-Reply-To: <1447960056.30346.28.camel@intel.com>
On 11/19/2015 2:07 PM, Verma, Vishal L wrote:
> On Thu, 2015-11-19 at 11:25 -0500, Linda Knippers wrote:
>
> <>
>> Yes, I will do that. I've only tested the boot path of the patch though.
>> Is there an easy way for me to trigger the notification so I can test the
>> other code path?
>>
>
> Hm, I don't believe there is an easy way yet. I believe KVM enabling for
> NVDIMMS using the NFIT is under way, and once they are ready we might have a
> way to test that path, but for now I just tested acpi_nfit_init onward using
> the test framework in tools/testing/nvdimm.
After looking around for some generic way to get an ACPI device
notify function called and failing miserably, I ended up just hacking the
nfit.c revision_show() function to call the notify function any time I look
at the /sys/.../nfit/revision file.
It's complaining that the new nfit deletes entries so I'm looking into that.
-- ljk
prev parent reply other threads:[~2015-11-19 20:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 17:54 [RFC PATCH] Fix _FIT vs. NFIT processing breakage Linda Knippers
2015-11-18 21:07 ` Verma, Vishal L
2015-11-18 21:28 ` Linda Knippers
2015-11-18 22:22 ` Toshi Kani
2015-11-18 23:43 ` Verma, Vishal L
2015-11-19 16:25 ` Linda Knippers
2015-11-19 19:07 ` Verma, Vishal L
2015-11-19 20:16 ` Linda Knippers [this message]
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=564E2E25.2050705@hpe.com \
--to=linda.knippers@hpe.com \
--cc=dan.j.williams@intel.com \
--cc=elliott@hpe.com \
--cc=jmoyer@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=rafael.j.wysocki@intel.com \
--cc=toshi.kani@hpe.com \
--cc=vishal.l.verma@intel.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.