Linux-MIPS Archive on lore.kernel.org
 help / color / Atom feed
From: Zhongwu Zhu <zzhu@wavecomp.com>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Tommy Jin <tjin@wavecomp.com>
Cc: "linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>
Subject: 答复: [EXTERNAL]Re: [PATCH] MIPS64: add KASAN support
Date: Thu, 5 Sep 2019 03:17:56 +0000
Message-ID: <CY4PR22MB0405AB0E7E26CFF4B3E9800FBCBB0@CY4PR22MB0405.namprd22.prod.outlook.com> (raw)
In-Reply-To: <20190829113320.GB9113@alpha.franken.de>

Hi Thomas,
	Tommy and me are responsible for mips KASAN issue. Thank you for your comments.
	We didn't consider cachable non coherent (0x98) and cachable exclusive (0xa0) mainly because we had not seen them be used. Do you know in which case this two segment address will be applied/accessed?
	but if these two segments are really needed, we can add it to our code. And correspondingly the KASAN address space need to be extend.(from 512G to 1024G, that is change the PGD_ORDER from 1 to 2).
BR
Zhongwu

-----ÓʼþÔ­¼þ-----
·¢¼þÈË: Thomas Bogendoerfer <tsbogend@alpha.franken.de> 
·¢ËÍʱ¼ä: 2019Äê8ÔÂ29ÈÕ 19:33
ÊÕ¼þÈË: Tommy Jin <tjin@wavecomp.com>
³­ËÍ: linux-mips@vger.kernel.org; Zhongwu Zhu <zzhu@wavecomp.com>
Ö÷Ìâ: [EXTERNAL]Re: [PATCH] MIPS64: add KASAN support

On Tue, Aug 27, 2019 at 08:28:38AM +0000, Tommy Jin wrote:
> +/* 64-bit segment value. */
> +#define XKPHYS_CACHE_SEG	(0xa8)

that's just cachable coherent exclusive on write, what about cachable non coherent (0x98) and cachable exclusive (0xa0) ?

Thomas.

--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

      reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-27  8:28 Tommy Jin
2019-08-29 11:33 ` Thomas Bogendoerfer
2019-09-05  3:17   ` Zhongwu Zhu [this message]

Reply instructions:

You may reply publically 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=CY4PR22MB0405AB0E7E26CFF4B3E9800FBCBB0@CY4PR22MB0405.namprd22.prod.outlook.com \
    --to=zzhu@wavecomp.com \
    --cc=linux-mips@vger.kernel.org \
    --cc=tjin@wavecomp.com \
    --cc=tsbogend@alpha.franken.de \
    /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

Linux-MIPS Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-mips/0 linux-mips/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-mips linux-mips/ https://lore.kernel.org/linux-mips \
		linux-mips@vger.kernel.org linux-mips@archiver.kernel.org
	public-inbox-index linux-mips

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-mips


AGPL code for this site: git clone https://public-inbox.org/ public-inbox