mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Kees Cook <keescook@chromium.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-parisc <linux-parisc@vger.kernel.org>,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	John David Anglin <dave.anglin@bell.net>,
	Richard Henderson <rth@twiddle.net>,
	Laura Abbott <labbott@redhat.com>
Subject: Re: [GIT PULL] parisc architecture fixes for 4.15-rc7
Date: Wed, 10 Jan 2018 14:44:23 +0100	[thread overview]
Message-ID: <6ed747e2-d037-b37d-51fb-39e0e2c3f2f4@gmx.de> (raw)
In-Reply-To: <CAGXu5jJ=s8NBBpd9fxr37T+HV8SNunq71AgGwu+Cy7WogPH=xA@mail.gmail.com>

On 10.01.2018 00:03, Kees Cook wrote:
> On Sun, Jan 7, 2018 at 8:21 AM, Helge Deller <deller@gmx.de> wrote:
>> Hi Linus,
>>
>> please pull a few fixes for the parisc architecture from:
>>
>>   git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git parisc-4.15-3
>>
>> The fixes are:
>> - Many small fixes to show the real physical addresses of devices instead of
>>   hashed addresses.
>>
>> - One important fix to unbreak 32-bit SMP support: We forgot to 16-byte align
>>   the spinlocks in the assembler code.
>>
>> - Qemu support: The host will get a chance to sleep when the parisc guest is
>>   idle. We use the same mechanism as the power architecture by overlaying the
>>   "or %r10,%r10,%r10" instruction which is simply a nop on real hardware.
>>
>> Thanks,
>> Helge
>>
>> ----------------------------------------------------------------
>> Helge Deller (6):
>>       parisc: Show unhashed hardware inventory
>>       parisc: Show unhashed EISA EEPROM address
> 
> These looks like a physical addresses, yes.
> 
>>       parisc: Show initial kernel memory layout unhashed
>>       parisc: Show unhashed HPA of Dino chip
> 
> But these are virtual addresses and should be just removed, not
> switched to %px. They're not physical addresses that I can see, e.g.
> "dino_dev" is clearly being used as an in-memory structure, and the
> kernel layout literally says "virtual kernel memory layout".

Agreed, some of those should go.
I'll clean that up in upcoming patches.

Thanks!
Helge

      reply	other threads:[~2018-01-10 13:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-07 16:21 Helge Deller
2018-01-09 23:03 ` Kees Cook
2018-01-10 13:44   ` Helge Deller [this message]

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=6ed747e2-d037-b37d-51fb-39e0e2c3f2f4@gmx.de \
    --to=deller@gmx.de \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=dave.anglin@bell.net \
    --cc=keescook@chromium.org \
    --cc=labbott@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=rth@twiddle.net \
    --cc=torvalds@linux-foundation.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®