All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antony Pavlov <antonynpavlov@gmail.com>
To: barebox@lists.infradead.org
Cc: Oleksij Rempel <o.rempel@pengutronix.de>
Subject: [RFC 0/2] MIPS: fix code relocation routine
Date: Tue, 18 Jun 2019 12:38:31 +0300	[thread overview]
Message-ID: <20190618093833.2005-1-antonynpavlov@gmail.com> (raw)

At the moment MIPS relocation code routine has at least two problems:

1. the first problem is fixed in the 'MIPS: relocate_code: fix barebox image size'
   patch from this patchseries.

2. relocate_code() calls flush_cache_all().
   flush_cache_all() uses 'struct cpuinfo_mips current_cpu_data' data fields.
   These data fields are initialized in r4k_cache_init().

   However in the current implementation the r4k_cache_init() function
   is called __AFTER__ relocate_code().

   This cache problem can't be discovered via qemu.

Antony Pavlov (2):
  MIPS: lib/Makefile: fix whitespaces
  MIPS: relocate_code: fix barebox image memcpy() size

 arch/mips/lib/Makefile |  4 ++--
 arch/mips/lib/reloc.c  | 11 +++++------
 2 files changed, 7 insertions(+), 8 deletions(-)

-- 
2.20.1


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2019-06-18  9:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-18  9:38 Antony Pavlov [this message]
2019-06-18  9:38 ` [RFC 1/2] MIPS: lib/Makefile: fix whitespaces Antony Pavlov
2019-06-18  9:38 ` [RFC 2/2] MIPS: relocate_code: fix barebox image memcpy() size Antony Pavlov
2019-06-18 11:05   ` Oleksij Rempel
2019-06-20 14:34 ` [RFC 0/2] MIPS: fix code relocation routine Sascha Hauer

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=20190618093833.2005-1-antonynpavlov@gmail.com \
    --to=antonynpavlov@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=o.rempel@pengutronix.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
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.