linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: linux-snps-arc@lists.infradead.org
Cc: linux-kernel@vger.kernel.org,
	Vineet Gupta <Vineet.Gupta1@synopsys.com>,
	Alexey Brodkin <Alexey.Brodkin@synopsys.com>
Subject: [PATCH 0/2] Minor fixes for CCMs
Date: Thu, 22 Dec 2016 17:09:08 +0300	[thread overview]
Message-ID: <1482415750-5471-1-git-send-email-abrodkin@synopsys.com> (raw)

It turned out current implementation of CCM support doesn't work at all.
There're 2 isseus:
 * Data/code which is supposed to be in DCCM or ICCM accordingly gets
   merged in common .data and .text sections so CCMs won't be used
 * Kerenl will panic on early boot because comparison of CCM sizes
   is implemented incorrectly

This short series fixes both issues above so CCMs are usable again.
And both patches indeed should be back-ported to stable kernels.

Alexey Brodkin (2):
  arc: rename xCCM sections so they are not merged in global .data/.text
  arc: Fix xCCM size check

 arch/arc/include/asm/linkage.h | 6 +++---
 arch/arc/kernel/setup.c        | 4 ++--
 arch/arc/kernel/vmlinux.lds.S  | 8 ++++----
 3 files changed, 9 insertions(+), 9 deletions(-)

-- 
2.7.4

             reply	other threads:[~2016-12-22 14:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-22 14:09 Alexey Brodkin [this message]
2016-12-22 14:09 ` [PATCH 1/2] arc: rename xCCM sections so they are not merged in global .data/.text Alexey Brodkin
2016-12-23  0:25   ` Vineet Gupta
2017-01-09 15:08     ` Alexey Brodkin
2016-12-22 14:09 ` [PATCH 2/2] arc: Fix xCCM size check Alexey Brodkin
2016-12-23  0:34   ` Vineet Gupta
2017-01-09 15:12     ` Alexey Brodkin
2016-12-23  0:26 ` [PATCH 0/2] Minor fixes for CCMs Vineet Gupta

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=1482415750-5471-1-git-send-email-abrodkin@synopsys.com \
    --to=alexey.brodkin@synopsys.com \
    --cc=Vineet.Gupta1@synopsys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-snps-arc@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).