All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Fleming <matt@console-pimps.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Laszlo Ersek <lersek@redhat.com>, Ingo Molnar <mingo@kernel.org>,
	"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
	Matt Fleming <matt.fleming@intel.com>,
	Mark Salter <msalter@redhat.com>
Subject: Re: [PATCH v2 0/5] beautify EFI memmap logs
Date: Wed, 3 Sep 2014 14:18:18 +0100	[thread overview]
Message-ID: <20140903131818.GE3001@console-pimps.org> (raw)
In-Reply-To: <CAKv+Gu_Yk-q0gf+EHc3EYQ=obLT2nj6Kj6qPTk678ASFEW+ZFQ@mail.gmail.com>

On Wed, 03 Sep, at 03:01:31PM, Ard Biesheuvel wrote:
> 
> Tested-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> (on arm64 only)
> 
> +1 for aligning between architectures
> +1 for cleaning up the output to make it more readable
 
Thanks Ard.

> The only thing I am not entirely convinced about is printing all those
> memory attributes: is it really so interesting to know that region X
> /can/ be configured as writeback, write through, write combining etc
> etc, as most regions seem to support most attributes, yet it tells you
> nothing about what the kernel ends up doing with that information. In
> the arm64 case, for instance, all MEMORY_WB ranges are mapped
> writeback cached, and everything else is mapped uncached.

Personally, I think it's good to get an unadulterated version of the
firmware memory map (for vicarious debugging) before the kernel has a
chance to mess with it.

-- 
Matt Fleming, Intel Open Source Technology Center

WARNING: multiple messages have this Message-ID (diff)
From: Matt Fleming <matt@console-pimps.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Laszlo Ersek <lersek@redhat.com>, Ingo Molnar <mingo@kernel.org>,
	"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
	Matt Fleming <matt.fleming@intel.com>,
	Mark Salter <msalter@redhat.com>
Subject: Re: [PATCH v2 0/5] beautify EFI memmap logs
Date: Wed, 03 Sep 2014 13:18:18 +0000	[thread overview]
Message-ID: <20140903131818.GE3001@console-pimps.org> (raw)
In-Reply-To: <CAKv+Gu_Yk-q0gf+EHc3EYQ=obLT2nj6Kj6qPTk678ASFEW+ZFQ@mail.gmail.com>

On Wed, 03 Sep, at 03:01:31PM, Ard Biesheuvel wrote:
> 
> Tested-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> (on arm64 only)
> 
> +1 for aligning between architectures
> +1 for cleaning up the output to make it more readable
 
Thanks Ard.

> The only thing I am not entirely convinced about is printing all those
> memory attributes: is it really so interesting to know that region X
> /can/ be configured as writeback, write through, write combining etc
> etc, as most regions seem to support most attributes, yet it tells you
> nothing about what the kernel ends up doing with that information. In
> the arm64 case, for instance, all MEMORY_WB ranges are mapped
> writeback cached, and everything else is mapped uncached.

Personally, I think it's good to get an unadulterated version of the
firmware memory map (for vicarious debugging) before the kernel has a
chance to mess with it.

-- 
Matt Fleming, Intel Open Source Technology Center

WARNING: multiple messages have this Message-ID (diff)
From: matt@console-pimps.org (Matt Fleming)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] beautify EFI memmap logs
Date: Wed, 3 Sep 2014 14:18:18 +0100	[thread overview]
Message-ID: <20140903131818.GE3001@console-pimps.org> (raw)
In-Reply-To: <CAKv+Gu_Yk-q0gf+EHc3EYQ=obLT2nj6Kj6qPTk678ASFEW+ZFQ@mail.gmail.com>

On Wed, 03 Sep, at 03:01:31PM, Ard Biesheuvel wrote:
> 
> Tested-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> (on arm64 only)
> 
> +1 for aligning between architectures
> +1 for cleaning up the output to make it more readable
 
Thanks Ard.

> The only thing I am not entirely convinced about is printing all those
> memory attributes: is it really so interesting to know that region X
> /can/ be configured as writeback, write through, write combining etc
> etc, as most regions seem to support most attributes, yet it tells you
> nothing about what the kernel ends up doing with that information. In
> the arm64 case, for instance, all MEMORY_WB ranges are mapped
> writeback cached, and everything else is mapped uncached.

Personally, I think it's good to get an unadulterated version of the
firmware memory map (for vicarious debugging) before the kernel has a
chance to mess with it.

-- 
Matt Fleming, Intel Open Source Technology Center

  reply	other threads:[~2014-09-03 13:18 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-03 11:32 [PATCH v2 0/5] beautify EFI memmap logs Laszlo Ersek
2014-09-03 11:32 ` Laszlo Ersek
2014-09-03 11:32 ` Laszlo Ersek
2014-09-03 11:32 ` [PATCH v2 1/5] efi: add macro for EFI_MEMORY_UCE memory attribute Laszlo Ersek
2014-09-03 11:32   ` Laszlo Ersek
2014-09-03 11:32   ` Laszlo Ersek
     [not found] ` <1409743943-16934-1-git-send-email-lersek-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-09-03 11:32   ` [PATCH v2 2/5] efi: introduce efi_md_typeattr_format() Laszlo Ersek
2014-09-03 11:32     ` Laszlo Ersek
2014-09-03 11:32     ` Laszlo Ersek
2014-09-03 11:32     ` Laszlo Ersek
2014-09-03 13:01   ` [PATCH v2 0/5] beautify EFI memmap logs Ard Biesheuvel
2014-09-03 13:01     ` Ard Biesheuvel
2014-09-03 13:01     ` Ard Biesheuvel
2014-09-03 13:01     ` Ard Biesheuvel
2014-09-03 13:18     ` Matt Fleming [this message]
2014-09-03 13:18       ` Matt Fleming
2014-09-03 13:18       ` Matt Fleming
2014-09-03 13:25       ` Laszlo Ersek
2014-09-03 13:25         ` Laszlo Ersek
2014-09-03 13:25         ` Laszlo Ersek
     [not found]     ` <CAKv+Gu_Yk-q0gf+EHc3EYQ=obLT2nj6Kj6qPTk678ASFEW+ZFQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-03 13:24       ` Laszlo Ersek
2014-09-03 13:24         ` Laszlo Ersek
2014-09-03 13:24         ` Laszlo Ersek
2014-09-03 13:24         ` Laszlo Ersek
     [not found]         ` <540716A1.7040905-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-09-03 13:27           ` Ard Biesheuvel
2014-09-03 13:27             ` Ard Biesheuvel
2014-09-03 13:27             ` Ard Biesheuvel
2014-09-03 13:27             ` Ard Biesheuvel
2014-09-03 11:32 ` [PATCH v2 3/5] x86: efi: format EFI memory type & attrs with efi_md_typeattr_format() Laszlo Ersek
2014-09-03 11:32   ` Laszlo Ersek
2014-09-03 11:32   ` Laszlo Ersek
2014-09-03 11:32 ` [PATCH v2 4/5] ia64: " Laszlo Ersek
2014-09-03 11:32   ` Laszlo Ersek
2014-09-03 11:32   ` Laszlo Ersek
2014-09-03 11:32 ` [PATCH v2 5/5] arm64: " Laszlo Ersek
2014-09-03 11:32   ` Laszlo Ersek
2014-09-03 11:32   ` Laszlo Ersek
2014-09-03 13:35 ` [PATCH v2 0/5] beautify EFI memmap logs Matt Fleming
2014-09-03 13:35   ` Matt Fleming
2014-09-03 13:35   ` Matt Fleming

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=20140903131818.GE3001@console-pimps.org \
    --to=matt@console-pimps.org \
    --cc=ard.biesheuvel@linaro.org \
    --cc=lersek@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt.fleming@intel.com \
    --cc=mingo@kernel.org \
    --cc=msalter@redhat.com \
    --cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.