Linux-Next discussions
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Miller <davem@davemloft.net>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	bob picco <bpicco@meloft.net>
Subject: linux-next: manual merge of the sparc-next tree with the sparc tree
Date: Wed, 6 Aug 2014 09:58:45 +1000	[thread overview]
Message-ID: <20140806095845.25491f00@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 3147 bytes --]

Hi David,

Today's linux-next merge of the sparc-next tree got a conflict in
arch/sparc/mm/init_64.c between commit 4ca9a23765da ("sparc64: Guard
against flushing openfirmware mappings") from the sparc tree and commit
f6d4fb5cc047 ("sparc64 - add mem to iomem resource") from the
sparc-next tree.

I fixed it up (see below) and can carry the fix as necessary (no action
is required).

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

diff --cc arch/sparc/mm/init_64.c
index 2cfb0f25e0ed,9f4f532e2627..000000000000
--- a/arch/sparc/mm/init_64.c
+++ b/arch/sparc/mm/init_64.c
@@@ -2708,25 -2701,66 +2709,89 @@@ void hugetlb_setup(struct pt_regs *regs
  }
  #endif
  
 +#ifdef CONFIG_SMP
 +#define do_flush_tlb_kernel_range	smp_flush_tlb_kernel_range
 +#else
 +#define do_flush_tlb_kernel_range	__flush_tlb_kernel_range
 +#endif
 +
 +void flush_tlb_kernel_range(unsigned long start, unsigned long end)
 +{
 +	if (start < HI_OBP_ADDRESS && end > LOW_OBP_ADDRESS) {
 +		if (start < LOW_OBP_ADDRESS) {
 +			flush_tsb_kernel_range(start, LOW_OBP_ADDRESS);
 +			do_flush_tlb_kernel_range(start, LOW_OBP_ADDRESS);
 +		}
 +		if (end > HI_OBP_ADDRESS) {
 +			flush_tsb_kernel_range(end, HI_OBP_ADDRESS);
 +			do_flush_tlb_kernel_range(end, HI_OBP_ADDRESS);
 +		}
 +	} else {
 +		flush_tsb_kernel_range(start, end);
 +		do_flush_tlb_kernel_range(start, end);
 +	}
 +}
++
+ static struct resource code_resource = {
+ 	.name	= "Kernel code",
+ 	.flags	= IORESOURCE_BUSY | IORESOURCE_MEM
+ };
+ 
+ static struct resource data_resource = {
+ 	.name	= "Kernel data",
+ 	.flags	= IORESOURCE_BUSY | IORESOURCE_MEM
+ };
+ 
+ static struct resource bss_resource = {
+ 	.name	= "Kernel bss",
+ 	.flags	= IORESOURCE_BUSY | IORESOURCE_MEM
+ };
+ 
+ static inline resource_size_t compute_kern_paddr(void *addr)
+ {
+ 	return (resource_size_t) (addr - KERNBASE + kern_base);
+ }
+ 
+ static void __init kernel_lds_init(void)
+ {
+ 	code_resource.start = compute_kern_paddr(_text);
+ 	code_resource.end   = compute_kern_paddr(_etext - 1);
+ 	data_resource.start = compute_kern_paddr(_etext);
+ 	data_resource.end   = compute_kern_paddr(_edata - 1);
+ 	bss_resource.start  = compute_kern_paddr(__bss_start);
+ 	bss_resource.end    = compute_kern_paddr(_end - 1);
+ }
+ 
+ static int __init report_memory(void)
+ {
+ 	int i;
+ 	struct resource *res;
+ 
+ 	kernel_lds_init();
+ 
+ 	for (i = 0; i < pavail_ents; i++) {
+ 		res = kzalloc(sizeof(struct resource), GFP_KERNEL);
+ 
+ 		if (!res) {
+ 			pr_warn("Failed to allocate source.\n");
+ 			break;
+ 		}
+ 
+ 		res->name = "System RAM";
+ 		res->start = pavail[i].phys_addr;
+ 		res->end = pavail[i].phys_addr + pavail[i].reg_size - 1;
+ 		res->flags = IORESOURCE_BUSY | IORESOURCE_MEM;
+ 
+ 		if (insert_resource(&iomem_resource, res) < 0) {
+ 			pr_warn("Resource insertion failed.\n");
+ 			break;
+ 		}
+ 
+ 		insert_resource(res, &code_resource);
+ 		insert_resource(res, &data_resource);
+ 		insert_resource(res, &bss_resource);
+ 	}
+ 
+ 	return 0;
+ }
+ device_initcall(report_memory);

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2014-08-05 23:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05 23:58 Stephen Rothwell [this message]
2014-08-06  1:58 ` linux-next: manual merge of the sparc-next tree with the sparc tree David Miller

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=20140806095845.25491f00@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=bpicco@meloft.net \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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