From: msalter@redhat.com (Mark Salter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM64: kernel: implement ACPI parking protocol
Date: Wed, 26 Aug 2015 15:13:22 -0400 [thread overview]
Message-ID: <1440616402.13044.16.camel@redhat.com> (raw)
In-Reply-To: <20150826160716.GB11863@red-moon>
On Wed, 2015-08-26 at 17:07 +0100, Lorenzo Pieralisi wrote:
> Mark,
>
> On Thu, Jul 16, 2015 at 06:40:49PM +0100, Mark Salter wrote:
>
> [...]
>
> > > > The kernel will only add cached memory regions to linear mapping
> > > > and
> > > > presumably, the FW will mark the mailboxes as uncached. Otherwise,
> > > > it
> > > > is a FW bug. But I suppose we could run into problems with kernels
> > > > using 64K pagesize since firmware assumes 4k.
> > >
> > > Nope, ioremap takes care of that, everything should be fine.
> >
> > The mailbox is 4K. If it is next to a cached UEFI region, the kernel
> > may
> > have to overlap the mailbox with a cached 64K mapping in order to
> > include
> > the adjoining UEFI region in the linear map. Then the ioremap would
> > fail
> > because the mailbox is included in the linear mapping.
>
> You have to acknowledge that what you describe is a bit of a corner
> case (and a silly FW set-up), are you aware of any existing FW set-up
> where we actually hit the corner case above ?
Oh sure. It could definitely be a corner case. I'm not aware of any
existing firmware supporting the protocol implemented by your patch.
So time will tell how well firmware vendors which do implement it
avoid the corner case problem. I am aware of some existing firmwares
which put the mailbox area in RAM which is also in the kernel linear
mapping as cached memory. But those wouldn't work with your patch for
more reasons than that.
>
> I think it is fine to leave code as-is, at least the mailbox
> mappings, I will check to see I can improve the MADT parsing,
> somehow.
I'm not strenuously opposed to leaving it as-is. But we need to
acknowledge that if the 64K pagesize issue isn't covered by the
protocol spec, we're relying on firmware vendors to be diligent
not to break 64K pagesize kernels.
next prev parent reply other threads:[~2015-08-26 19:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 11:33 [PATCH] ARM64: kernel: implement ACPI parking protocol Lorenzo Pieralisi
2015-07-16 16:17 ` Mark Salter
2015-07-16 17:12 ` Lorenzo Pieralisi
2015-07-16 17:40 ` Mark Salter
2015-07-17 10:35 ` Lorenzo Pieralisi
2015-08-26 16:07 ` Lorenzo Pieralisi
2015-08-26 19:13 ` Mark Salter [this message]
2015-08-27 9:50 ` Lorenzo Pieralisi
2015-08-27 13:27 ` Mark Salter
2015-08-28 10:23 ` Lorenzo Pieralisi
2015-08-28 14:29 ` Mark Salter
2015-08-28 15:32 ` Lorenzo Pieralisi
2015-08-28 15:56 ` Mark Salter
2015-08-28 16:10 ` Lorenzo Pieralisi
2015-08-28 16:11 ` Leif Lindholm
2015-07-16 18:05 ` Al Stone
2015-07-16 18:23 ` Mark Salter
2015-07-16 21:02 ` Al Stone
2015-07-17 9:16 ` Hanjun Guo
2015-08-24 17:13 ` Lorenzo Pieralisi
2015-08-25 14:01 ` Mark Salter
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=1440616402.13044.16.camel@redhat.com \
--to=msalter@redhat.com \
--cc=linux-arm-kernel@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).