From: Vasant Hegde <hegdevasant@linux.vnet.ibm.com>
To: Jeremy Kerr <jk@ozlabs.org>, linuxppc-dev@ozlabs.org
Cc: Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>,
"Aneesh Kumar K . V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: [PATCH] powerpc/powernv/prd: Validate whether address to be mapped is part of system RAM
Date: Thu, 3 Oct 2019 11:01:02 +0530 [thread overview]
Message-ID: <9b9b529d-cad7-0ace-acf6-e07d0dea5670@linux.vnet.ibm.com> (raw)
In-Reply-To: <049794f6a16f548bcb418d31fecf268cb4a335e5.camel@ozlabs.org>
On 10/3/19 10:26 AM, Jeremy Kerr wrote:
> Hi Vasant,
>
>> Correct. We will have `ibm,prd-label` property. That's not the issue.
>
> It sure sounds like the issue - someone has represented a range that
> should be mapped by HBRT, but isn't appropriate for mapping by HBRT.
>
>> Here issueis HBRT is loaded into NVDIMM memory.
>
> OK. How about we just don't do that?
Yes. Hostboot will fix that. It will make sure that HBRT is loaded into regular
memory.
>
> It sounds like we're just trying to work around an invalid
> representation of the mappings.
Its not workaround. Its additional check. So that we don't mmap() if HBRT is not
in system RAM
and throw proper error.. So that debugging becomes easy.
-Vasant
next prev parent reply other threads:[~2019-10-03 5:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 7:48 [PATCH] powerpc/powernv/prd: Validate whether address to be mapped is part of system RAM Vasant Hegde
2019-10-02 8:48 ` Vaidyanathan Srinivasan
2019-10-03 1:47 ` Jeremy Kerr
2019-10-03 4:51 ` Vasant Hegde
2019-10-03 4:56 ` Jeremy Kerr
2019-10-03 5:31 ` Vasant Hegde [this message]
2019-10-03 7:07 ` Jeremy Kerr
2019-10-03 10:29 ` Vaidyanathan Srinivasan
2019-10-04 3:27 ` Jeremy Kerr
2019-10-05 5:08 ` Vaidyanathan Srinivasan
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=9b9b529d-cad7-0ace-acf6-e07d0dea5670@linux.vnet.ibm.com \
--to=hegdevasant@linux.vnet.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=jk@ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=svaidy@linux.vnet.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 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).