From: Toshi Kani <toshi.kani@hpe.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux MM <linux-mm@kvack.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
Linux ACPI <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] ACPI/APEI/EINJ: Allow memory error injection to NVDIMM
Date: Fri, 23 Oct 2015 08:03:57 -0600 [thread overview]
Message-ID: <1445609037.20657.68.camel@hpe.com> (raw)
In-Reply-To: <CAPcyv4j9iDrUrS1Xt4sTV8KOg6wsb=stp=XzoOLFBtuqWf+0AQ@mail.gmail.com>
On Thu, 2015-10-22 at 17:14 -0700, Dan Williams wrote:
> On Thu, Oct 22, 2015 at 4:20 PM, Toshi Kani <toshi.kani@hpe.com> wrote:
> > In the case of memory error injection, einj_error_inject() checks
> > if a target address is regular RAM. Change this check to allow
> > injecting a memory error to both RAM and NVDIMM so that memory
> > errors can be tested on NVDIMM as well.
> >
> > Signed-off-by: Toshi Kani <toshi.kani@hpe.com>
> > ---
> > drivers/acpi/apei/einj.c | 12 ++++++++----
> > 1 file changed, 8 insertions(+), 4 deletions(-)
> >
> > diff --git a/drivers/acpi/apei/einj.c b/drivers/acpi/apei/einj.c
> > index 0431883..696f45a 100644
> > --- a/drivers/acpi/apei/einj.c
> > +++ b/drivers/acpi/apei/einj.c
> > @@ -519,7 +519,7 @@ static int
> (u32 type, u32 flags, u64 param1, u64 param2,
> > u64 param3, u64 param4)
> > {
> > int rc;
> > - unsigned long pfn;
> > + u64 base_addr, size;
> >
> > /* If user manually set "flags", make sure it is legal */
> > if (flags && (flags &
> > @@ -545,10 +545,14 @@ static int einj_error_inject(u32 type, u32 flags, u64
> > param1, u64 param2,
> > /*
> > * Disallow crazy address masks that give BIOS leeway to pick
> > * injection address almost anywhere. Insist on page or
> > - * better granularity and that target address is normal RAM.
> > + * better granularity and that target address is normal RAM or
> > + * NVDIMM.
> > */
> > - pfn = PFN_DOWN(param1 & param2);
> > - if (!page_is_ram(pfn) || ((param2 & PAGE_MASK) != PAGE_MASK))
> > + base_addr = param1 & param2;
> > + size = (~param2) + 1;
> > + if (((!page_is_ram(PFN_DOWN(base_addr))) &&
> > + (region_intersects_pmem(base_addr, size) != REGION_INTERSECTS))
> > ||
> > + ((param2 & PAGE_MASK) != PAGE_MASK))
>
> Hmm, should we also convert the page_is_ram() call to
> region_intersects_ram() so that we check the entire range from
> base_addr to base_addr + size?
Agreed. I will update to use region_intersects_ram().
Thanks,
-Toshi
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2015-10-23 14:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 23:20 [PATCH 0/3] Allow EINJ to inject memory error to NVDIMM Toshi Kani
2015-10-22 23:20 ` [PATCH 1/3] resource: Add @flags to region_intersects() Toshi Kani
2015-10-22 23:20 ` [PATCH 2/3] resource: Add region_intersects_pmem() Toshi Kani
2015-10-22 23:20 ` [PATCH 3/3] ACPI/APEI/EINJ: Allow memory error injection to NVDIMM Toshi Kani
2015-10-23 0:14 ` Dan Williams
2015-10-23 14:03 ` Toshi Kani [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=1445609037.20657.68.camel@hpe.com \
--to=toshi.kani@hpe.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.org \
--cc=rjw@rjwysocki.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).