public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed

From: qiuxishi@huawei•com (Xishi Qiu)
To: linux-arm-kernel@lists•infradead.org
Subject: Have any influence on set_memory_** about below patch ??
Date: Tue, 12 Jan 2016 09:20:54 +0800	[thread overview]
Message-ID: <569454F6.1060207@huawei.com> (raw)
In-Reply-To: <20160111133145.GM6499@leverpostej>

On 2016/1/11 21:31, Mark Rutland wrote:

> Hi,
> 
> On Mon, Jan 11, 2016 at 08:59:44PM +0800, zhong jiang wrote:
>>
>> http://www.spinics.net/lists/arm-kernel/msg472090.html
>>
>> Hi, Can I ask you a question? Say, This patch tells that the section spilting
>> and merging wiil produce confilct in the liner mapping area. Based on the
>> situation, Assume that set up page table in 4kb page table way in the liner
>> mapping area, Does the set_memroy_** will work without any conplict??
> 
> I'm not sure I understand the question.
> 
> I'm also not a fan of responding to off-list queries as information gets
> lost.
> 
> Please ask your question on the mailing list. I am more than happy to
> respond there.
> 
> Thanks,
> Mark.
> 

Hi Mark,

In your patch it said "The presence of conflicting TLB entries may result in
a variety of behaviours detrimental to the system " and "but this(break-before-make
approach) cannot work for modifications to the swapper page tables that cover the
kernel text and data."

I'm not quite understand this, why the direct mapping can't work?
flush tlb can't resolve it?

I find x86 does not have this limit. e.g. set_memory_r*.

Thanks,
Xishi Qiu

> .
> 

next      parent reply	other threads:[~2016-01-12  1:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5693A740.7070408@huawei.com>
     [not found] ` <20160111133145.GM6499@leverpostej>
2016-01-12  1:20   ` Xishi Qiu [this message]
2016-01-12 11:15     ` Have any influence on set_memory_** about below patch ?? Mark Rutland
2016-01-13  4:10       ` Xishi Qiu
2016-01-13 11:22         ` Mark Rutland
2016-01-13  5:02       ` Xishi Qiu
2016-01-13  6:35         ` Xishi Qiu
2016-01-13 11:28         ` Mark Rutland
2016-01-27  1:18           ` Xishi Qiu
2016-01-27 11:25             ` Mark Rutland
2016-01-26 14:05         ` zhong jiang
2016-01-26 16:07           ` Mark Rutland
2016-01-13 10:30       ` Xishi Qiu
2016-01-13 11:18         ` Mark Rutland
2016-01-14 12:35           ` Xishi Qiu
2016-01-14 13:06             ` Xishi Qiu
2016-01-14 13:44               ` Mark Rutland

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=569454F6.1060207@huawei.com \
    --to=qiuxishi@huawei$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox