All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bryan O'Donoghue" <pure.logic@nexus-software.ie>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, dvhart@infradead.org, boon.leong.ong@intel.com,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/1] x86: Add Isolated Memory Regions for Quark X1000
Date: Mon, 26 Jan 2015 16:59:19 +0000	[thread overview]
Message-ID: <54C67267.3060406@nexus-software.ie> (raw)
In-Reply-To: <CAHp75VfAPjermaPYu2FwoRCycKsU48m=uXq=JqwQ6Bi31kV0hg@mail.gmail.com>

On 26/01/15 16:37, Andy Shevchenko wrote:

>> +config X86_INTEL_QUARK
>> +       bool "Intel Quark platform support"
>> +       depends on X86_32
>> +       depends on X86_EXTENDED_PLATFORM
>> +       depends on X86_PLATFORM_DEVICES
>> +       depends on PCI
>> +       depends on PCI_GOANY
>> +       depends on X86_IO_APIC
>> +       select IOSF_MBI
>> +       select INTEL_IMR
>> +       ---help---
>> +         Select to include support for Quark X1000 SoC.
>> +         Say Y here if you have a Quark based system such as the Arduino
>> +         compatible Intel Galileo.
>> +
>
> Does it mean we introduce a minimal support for the platform.

I'd call it minimal support yes since the IMR memory map needs to be 
sanitized before you run DMA.

All shipping versions of Galileo will need to have IMRs sanitized to 
reliably run Linux - or any other kernel for that matter - with DMA.

> So, I mean if user enables this in the kernel config and runs rebuilt
> kernel on the Quark it will work, will it?

Yes. Do you mean to add a stronger comment indicating IMR is mandatory ?
No issue with that.

> If so, IMR is mandatory stuff or not? What else is mandatory?

IMR is the only mandatory addition.

> So, I'm not sure the above is a part of the patch. Would it be a prepend?

Hmm - what do you mean by that ?

<snip>

No issue with the rest of the review - thanks for the time.

--
BOD

  parent reply	other threads:[~2015-01-26 16:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-26 14:15 [PATCH v3 0/1] x86: Add IMR support to Quark/Galileo Bryan O'Donoghue
2015-01-26 14:15 ` [PATCH v3 1/1] x86: Add Isolated Memory Regions for Quark X1000 Bryan O'Donoghue
2015-01-26 16:37   ` Andy Shevchenko
2015-01-26 16:43     ` Andy Shevchenko
2015-01-26 16:59     ` Bryan O'Donoghue [this message]
2015-01-26 17:23       ` Andy Shevchenko
2015-01-26 18:02         ` Bryan O'Donoghue
2015-01-26 18:04         ` Bryan O'Donoghue
2015-02-23 22:18   ` Pavel Machek
2015-02-24 22:40     ` Bryan O'Donoghue
2015-03-02 12:19       ` Pavel Machek
2015-01-26 14:37 ` [PATCH v3 0/1] x86: Add IMR support to Quark/Galileo Bryan O'Donoghue

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=54C67267.3060406@nexus-software.ie \
    --to=pure.logic@nexus-software.ie \
    --cc=andy.shevchenko@gmail.com \
    --cc=boon.leong.ong@intel.com \
    --cc=dvhart@infradead.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --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.