linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] arm64: TLB maintainance: Implement flush_kern_tlb_page
Date: Mon, 19 May 2014 12:01:13 +0100	[thread overview]
Message-ID: <20140519110113.GL5113@arm.com> (raw)
In-Reply-To: <CAD15agbbyEPbM5rw9gfAC5qMUxi-0rWp58J40j2XYYyf27rozQ@mail.gmail.com>

On Mon, May 19, 2014 at 11:54:31AM +0100, Ritesh Harjani wrote:
> On Mon, May 19, 2014 at 4:16 PM, Catalin Marinas
> <catalin.marinas@arm.com> wrote:
> > On Mon, May 19, 2014 at 11:34:25AM +0100, ritesh.harjani at gmail.com wrote:
> >> From: Ritesh Harjani <ritesh.harjani@gmail.com>
> >>
> >> Implement flush_kern_tlb_page mentioned in the header
> >> comment of arch/arm64/include/asm/tlbflush.h
> >
> > Alternatively, clean-up the comment.
> 
> You mean this function is of no use ? Or there are other plans which
> might require clean up of this file ?

Since we don't have it and the kernel builds fine, I guess we don't need
it.

> Also, could you please confirm whether the implementation of the
> function is correct ?
> 
> >> +       asm("tlbi       vae1is, %0" : : "r" (addr));
> 
> Should following instruction be more appropriate instead of above:
> asm("tlbi       vaae1is, %0" : : "r" (addr));

You should use the vaae1is variant for all ASIDs since it's a global
mapping (see flush_tlb_kernel_range()).

-- 
Catalin

  reply	other threads:[~2014-05-19 11:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-19 10:34 [PATCH 0/1] Implement flush_kern_tlb_page ritesh.harjani at gmail.com
2014-05-19 10:34 ` [PATCH 1/1] arm64: TLB maintainance: " ritesh.harjani at gmail.com
2014-05-19 10:46   ` Catalin Marinas
2014-05-19 10:54     ` Ritesh Harjani
2014-05-19 11:01       ` Catalin Marinas [this message]
2014-05-19 11:07         ` Ritesh Harjani

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=20140519110113.GL5113@arm.com \
    --to=catalin.marinas@arm.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).