From: "Zhang, Lei" <zhang.lei@jp.fujitsu.com>
To: 'Mark Rutland' <mark.rutland@arm.com>,
"'james.morse@arm.com'" <james.morse@arm.com>
Cc: "'catalin.marinas@arm.com'" <catalin.marinas@arm.com>,
"'will.deacon@arm.com'" <will.deacon@arm.com>,
"'linux-arm-kernel@lists.infradead.org'"
<linux-arm-kernel@lists.infradead.org>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"Zhang, Lei" <zhang.lei@jp.fujitsu.com>
Subject: RE: [PATCH] arm64 memory accesses may cause undefined fault on Fujitsu-A64FX
Date: Wed, 23 Jan 2019 12:51:08 +0000 [thread overview]
Message-ID: <8898674D84E3B24BA3A2D289B872026A6A2A3BED@G01JPEXMBKW03> (raw)
In-Reply-To: <20190122152339.GD52887@lakrids.cambridge.arm.com>
Hi, Mark, James
> -----Original Message-----
> From: Mark Rutland [mailto:mark.rutland@arm.com]
> Sent: Wednesday, January 23, 2019 12:24 AM
> To: Zhang, Lei/張 雷
> Cc: 'catalin.marinas@arm.com'; 'will.deacon@arm.com';
> 'linux-arm-kernel@lists.infradead.org';
> 'linux-kernel@vger.kernel.org'
> Subject: Re: [PATCH] arm64 memory accesses may cause undefined fault on
> Fujitsu-A64FX
>
> As above, I'm very concerned that this could be taken from kernel
> context. There are a number of cases where we cannot handle such faults:
At first thanks for your comments.
I thinks James's comments is quite similar with above comment.
I am reviewing this point now.
I will respond to your questions after I check this.
Thanks
Lei Zhang
next prev parent reply other threads:[~2019-01-23 12:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 12:52 [PATCH] arm64 memory accesses may cause undefined fault on Fujitsu-A64FX Zhang, Lei
2019-01-18 14:17 ` Mark Rutland
2019-01-22 2:05 ` Zhang, Lei
2019-01-22 14:42 ` James Morse
2019-01-22 15:23 ` Mark Rutland
2019-01-23 12:51 ` Zhang, Lei [this message]
2019-01-25 6:51 ` Zhang, Lei
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=8898674D84E3B24BA3A2D289B872026A6A2A3BED@G01JPEXMBKW03 \
--to=zhang.lei@jp.fujitsu.com \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=will.deacon@arm.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).