From: Borislav Petkov <bp@alien8.de>
To: "Zhang, Jonathan Zhixiong" <zjzhang@codeaurora.org>
Cc: Matt Fleming <matt@codeblueprint.co.uk>,
rjw@rjwysocki.net, lenb@kernel.org, ying.huang@intel.com,
leif.lindholm@linaro.org, al.stone@linaro.org, fu.wei@linaro.org,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linaro-acpi@lists.linaro.org,
vgandhi@codeaurora.org, Tony Luck <tony.luck@gmail.com>
Subject: Re: [PATCH V2 3/3] acpi, apei: use EFI memmap to map GHES memory
Date: Fri, 5 Jun 2015 19:12:10 +0200 [thread overview]
Message-ID: <20150605171210.GM3679@pd.tnic> (raw)
In-Reply-To: <5571D6C9.10903@codeaurora.org>
On Fri, Jun 05, 2015 at 10:05:13AM -0700, Zhang, Jonathan Zhixiong wrote:
> >What is DDR?
> >
> >I think this needs to be clarified first before we go any further.
> I thought the word "memory" might be confusing, because there are
So you mean normal RAM here?
> memories on the system that is not accessible by Linux. In this
> context, the APEI error data is accessed (read and write) by both Linux
> and platform firmware; hence both sides should access the memory using
> same cache attribute. I wanted to emphasize the idea that even though
> normally DDR is cachable, but in this case when platform access it with
> un-cached attribute, Linux should do the same.
Makes sense.
Btw, do we need synchronization between firmware and Linux then? Does
Linux need to know when it is ok to touch that memory?
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2015-06-05 17:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 19:12 [PATCH V2 0/3] map GHES memory region with EFI memory map Jonathan (Zhixiong) Zhang
2015-06-01 19:12 ` [PATCH V2 1/3] efi: arch, x86: arch, ia64: move efi_mem_attributes() Jonathan (Zhixiong) Zhang
2015-06-02 13:36 ` Matt Fleming
2015-06-03 0:09 ` Zhang, Jonathan Zhixiong
2015-06-05 9:23 ` Matt Fleming
2015-06-05 16:44 ` Zhang, Jonathan Zhixiong
2015-06-01 19:12 ` [PATCH V2 2/3] efi: add efi_remap() Jonathan (Zhixiong) Zhang
2015-06-01 19:12 ` [PATCH V2 3/3] acpi, apei: use EFI memmap to map GHES memory Jonathan (Zhixiong) Zhang
2015-06-05 9:57 ` Matt Fleming
2015-06-05 10:25 ` Borislav Petkov
2015-06-05 17:05 ` Zhang, Jonathan Zhixiong
2015-06-05 17:12 ` Borislav Petkov [this message]
2015-06-05 21:43 ` Zhang, Jonathan Zhixiong
2015-06-05 16:43 ` Zhang, Jonathan Zhixiong
2015-06-05 16:50 ` Borislav Petkov
2015-06-05 17:06 ` Zhang, Jonathan Zhixiong
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=20150605171210.GM3679@pd.tnic \
--to=bp@alien8.de \
--cc=al.stone@linaro.org \
--cc=fu.wei@linaro.org \
--cc=leif.lindholm@linaro.org \
--cc=lenb@kernel.org \
--cc=linaro-acpi@lists.linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=rjw@rjwysocki.net \
--cc=tony.luck@gmail.com \
--cc=vgandhi@codeaurora.org \
--cc=ying.huang@intel.com \
--cc=zjzhang@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox