linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: kill flush_cache_all()
Date: Mon, 20 Apr 2015 20:22:44 +0100	[thread overview]
Message-ID: <20150420192243.GA8040@leverpostej> (raw)
In-Reply-To: <CAKv+Gu_6u6wZrd=3z94Wqrab=G=bxm30=zWK0Rry3w+F92Wn9w@mail.gmail.com>

> > Does that address your concerns? Or pose new questions? ;)
> >
> 
> Crystal clear. Lately I have been dealing with some dodgy Tianocore
> code that 'promoted' VA operations to set/way operations if the VA
> range exceeded a certain size threshold (and nuked the whole cache
> instead), so by now I am well aware of the differences. I was just
> vaguely under the impression that clearing the C bit could result in
> the caches to lose state, but apparently not.

To the best of my knowledge, that is not permitted.

> So that means the EFI stub entry code is sound, and I have no
> objections whatsoever to removing flush_cache_all() et al

Great! Can I consider that an Acked-by?

Thanks,
Mark.

  reply	other threads:[~2015-04-20 19:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20  9:24 [PATCH] arm64: kill flush_cache_all() Mark Rutland
2015-04-20  9:42 ` Marc Zyngier
2015-04-20  9:46   ` Mark Rutland
2015-04-20 10:03     ` Marc Zyngier
2015-04-20  9:59 ` Will Deacon
2015-04-20 10:06 ` Catalin Marinas
2015-04-20 10:21 ` Lorenzo Pieralisi
2015-04-20 17:23 ` Ard Biesheuvel
2015-04-20 18:02   ` Mark Rutland
2015-04-20 18:42     ` Ard Biesheuvel
2015-04-20 19:22       ` Mark Rutland [this message]
2015-04-20 19:29         ` Ard Biesheuvel

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=20150420192243.GA8040@leverpostej \
    --to=mark.rutland@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).