From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Heinrich Schuchardt <xypron.glpk@gmx.de>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 1/1] arm: mm: Export __sync_icache_dcache() for xen-privcmd
Date: Wed, 17 Apr 2019 10:41:37 +0100 [thread overview]
Message-ID: <20190417094137.2gkbtinldiwbkvwy@shell.armlinux.org.uk> (raw)
In-Reply-To: <20190415055109.GB9279@infradead.org>
On Sun, Apr 14, 2019 at 10:51:09PM -0700, Christoph Hellwig wrote:
> On Sat, Apr 13, 2019 at 06:30:52PM +0200, Heinrich Schuchardt wrote:
> > This patch avoids
> > ERROR: "__sync_icache_dcache" [drivers/xen/xen-privcmd.ko] undefined!
> > observed when compiling v4.19.34.
> >
> > The xen-privcmd driver, which can be modular, calls set_pte_at()
> > which in turn may call __sync_icache_dcache().
>
> Maybe that really is a sign that it should not be modular..
This issue has been discussed several times, and this URL gives a list
of all messages on linux-arm-kernel that mention __sync_icache_dcache:
https://archive.armlinux.org.uk/lurker/search/20380101.000000.00000000@ml:linux-arm-kernel,sb:__sync_icache_dcache.en.html
At the beginning of March, Boris Ostrovsky pointed that another solution
is available that does not need architecture private symbols to be
exported.
Since I've already said in a previous thread that I don't want this
function exported, it seems the way forward is pretty obvious.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
next prev parent reply other threads:[~2019-04-17 9:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-13 16:30 Heinrich Schuchardt
2019-04-15 5:51 ` Christoph Hellwig
2019-04-17 9:41 ` Russell King - ARM Linux admin [this message]
2019-04-17 10:03 ` Catalin Marinas
2019-04-17 10:31 ` Russell King - ARM Linux admin
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=20190417094137.2gkbtinldiwbkvwy@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=hch@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=xypron.glpk@gmx.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 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®