linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: minchan.kim@gmail.com (Minchan Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: Question of kmap_atomic
Date: Fri, 16 Jul 2010 11:52:20 +0900	[thread overview]
Message-ID: <AANLkTinphjSG89dQLadFZbJ9eVh7rJtm2N5-KT505ZzT@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1007152241110.10598@xanadu.home>

On Fri, Jul 16, 2010 at 11:46 AM, Nicolas Pitre <nico@fluxnic.net> wrote:
> On Fri, 16 Jul 2010, Minchan Kim wrote:
>
>> >> But the patch made it to not call kmap_high_get when VIPT-aliasing
>> >> model in CONFIG_DEBUG_HIGHMEM.
>> >> Doesn't it cause aliasing problem as 7929eb9cf64 says, again?
>> >
>> > No because with VIPT, the cache is tagged with physical addresses, and
>> > therefore the same cache data will be used for the same memory
>> > regardless of the virtual address used to reach it. ?On VIVT this is not
>> > the case and the comment in 7929eb9cf64 applies to VIVT only.
>>
>> Thanks for quick reply, Nicolas.
>>
>> My concern is following as.
>>
>> In VIPT alising model,
> [...]
>
> Highmem is not supported with VIPT alising and probably will never be.
> See commit 3f973e22.

It's clear.
Thanks, Nicolas.


-- 
Kind regards,
Minchan Kim

  reply	other threads:[~2010-07-16  2:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTilFvE0eyQS7jNQ77OYkJovJugjKRO-fPHjX8CB9@mail.gmail.com>
2010-07-16  0:44 ` Question of kmap_atomic Minchan Kim
2010-07-16  2:10 ` Nicolas Pitre
2010-07-16  2:31   ` Minchan Kim
2010-07-16  2:46     ` Nicolas Pitre
2010-07-16  2:52       ` Minchan Kim [this message]
2010-07-16  7:46 ` Russell King - ARM Linux

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=AANLkTinphjSG89dQLadFZbJ9eVh7rJtm2N5-KT505ZzT@mail.gmail.com \
    --to=minchan.kim@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).