From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Mark Salter <msalter@redhat.com>,
catalin.marinas@arm.com,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
Chen Baozi <baozich@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64/xen: redefine xen_remap on arm64
Date: Fri, 3 Jan 2014 14:31:04 +0000 [thread overview]
Message-ID: <20140103143104.GN7383@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.02.1401031310100.8667@kaball.uk.xensource.com>
On Fri, Jan 03, 2014 at 01:13:57PM +0000, Stefano Stabellini wrote:
> On Mon, 30 Dec 2013, Mark Salter wrote:
> > On Mon, 2013-12-30 at 14:55 +0800, Chen Baozi wrote:
> > > xen_remap used to be defined as ioremap_cached on arm64. In commit
> > > c04e8e2fe, a new ioremap_cache was implemented, and ioremap_cached
> > > was deleted, while xen_remap stays the same. This would lead to
> > > the failure when building with CONFIG_HVC_XEN. Redefined xen_remap
> > > on arm64 as ioremap_cache on arm64 to fix it.
> > >
> >
> > I missed that include of arm header by arm64 when looking for users
> > of arm64's ioremap_cached() when working on commit c04e8e2fe. Anyway,
> > grepping the kernel tree, I see:
> >
> > ioremap_cached()
> > defined by: arm, metag, unicore32
> > used by: arch/arm/include/asm/xen/page.h
> > drivers/mtd/maps/pxa2xx-flash.c
> >
> > ioremap_cache()
> > defined by: arm64, sh, xtensa, ia64, x86
> > used by: drivers/video/vesafb.c
> > drivers/char/toshiba.c
> > drivers/acpi/apei
> > drivers/lguest/lguest_device.c
> > drivers/sfi/sfi_core.c
> > include/linux/acpi_io.h
> >
> > I think it would be better to just avoid the confusion and the ifdef in
> > asm/xen/page.h by globally changing ioremap_cached to ioremap_cache.
>
> While I welcome the suggestion, this is a critical fix for a regression
> that I think should go in as soon as possible, maybe 3.13-rc7, while I
> don't think that a global s/ioremap_cached/ioremap_cache would be
> acceptable at this stage.
Since it's just one driver, just make the change for ARM (provided the
grep is accurate.) pxa2xx-flash is only used on ARM and not the other
two listed there, so looks like metag and unicore just decided to copy
ARM.
My grep concurs with yours.
So... just change ioremap_cached -> ioremap_cache in
arch/arm/include/asm/io.h
arch/arm/include/asm/xen/page.h
drivers/mtd/maps/pxa2xx-flash.c
to fix the problem.
--
FTTC broadband for 0.8mile line: 5.8Mbps down 500kbps up. Estimation
in database were 13.1 to 19Mbit for a good line, about 7.5+ for a bad.
Estimate before purchase was "up to 13.2Mbit".
next prev parent reply other threads:[~2014-01-03 14:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-30 6:55 Chen Baozi
2013-12-30 9:43 ` [Xen-devel] " Wei Liu
2014-01-03 13:19 ` Stefano Stabellini
2013-12-30 19:20 ` Mark Salter
2014-01-03 13:13 ` Stefano Stabellini
2014-01-03 13:32 ` Stefano Stabellini
2014-01-03 14:31 ` Russell King - ARM Linux [this message]
2014-01-03 14:49 ` Stefano Stabellini
2014-01-03 14:59 ` Russell King - ARM Linux
2014-01-03 15:17 ` Stefano Stabellini
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=20140103143104.GN7383@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=baozich@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msalter@redhat.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xenproject.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
all inboxes | Powered by JetHome®