From: "Ong, Boon Leong" <boon.leong.ong@intel.com>
To: "Bryan O'Donoghue" <pure.logic@nexus-software.ie>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>,
"dvhart@infradead.org" <dvhart@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Ingo Molnar <mingo@kernel.org>
Subject: RE: [PATCH 1/2] x86: Add Isolated Memory Regions for Quark X1000
Date: Thu, 29 Jan 2015 15:15:58 +0000 [thread overview]
Message-ID: <AF233D1473C1364ABD51D28909A1B1B732715A94@PGSMSX105.gar.corp.intel.com> (raw)
In-Reply-To: 54CA0782.8000807@nexus-software.ie
Hi Bryan,
These two patches requires another patch "x86: Re-enable IO-APIC for non-SMP X86_32"
to be included to make sure we have the right build for Quark.
I tested v6 on Galileo Gen v2 just now. I am happy with it.
Many thanks.
Below are the logs:
root@quark:/proc# dmesg | grep imr
[ 3.727884] imr: protecting kernel .text - .rodata: 9240 KiB (c1000000 - c1906000)
[ 3.736421] imr_selftest: self_test pass zero sized IMR
[ 3.742413] imr_selftest: self_test pass overlapped IMR @ (0xc1000000 - 0xc1906000)
[ 3.751164] imr_selftest: self_test pass overlapped IMR @ (0xc1905c00 - 0xc220bc00)
[ 3.759916] imr_selftest: self_test pass overlapped IMR @ (0xc0fff400 - 0xc1905400)
[ 3.768566] imr_selftest: self_test pass 1KiB IMR @ 0x00000000 - access-all
[ 3.776542] imr_selftest: self_test pass 1KiB IMR @ 0x00000000 - cpu access
[ 3.784442] imr_selftest: self_test pass index-teardown - cpu access
[ 3.791690] imr_selftest: self_test pass 2KiB IMR @ 0x00000000
[ 3.798396] imr_selftest: self_test pass index-teardown 2KiB
[ 3.804957] imr_selftest: self_test pass 2KiB IMR @ 0x00000000
[ 3.811616] imr_selftest: self_test pass addr-teardown 2KiB
root@quark:/proc# cat /sys/kernel/debug/imr_state
imr00: base=0x00000000, end=0x00000000, size=0x00000000 rmask=0xbfffffff, wmask=0xffffffff, disabled, unlocked
imr01: base=0x00000000, end=0x00000000, size=0x00000000 rmask=0xbfffffff, wmask=0xffffffff, disabled, unlocked
imr02: base=0x00000000, end=0x00000000, size=0x00000000 rmask=0xbfffffff, wmask=0xffffffff, disabled, unlocked
imr03: base=0x00000000, end=0x00000000, size=0x00000000 rmask=0xbfffffff, wmask=0xffffffff, disabled, unlocked
imr04: base=0x00000000, end=0x00000000, size=0x00000000 rmask=0xbfffffff, wmask=0xffffffff, disabled, unlocked
imr05: base=0x00000000, end=0x00000000, size=0x00000000 rmask=0xbfffffff, wmask=0xffffffff, disabled, unlocked
imr06: base=0x00000000, end=0x00000000, size=0x00000000 rmask=0xbfffffff, wmask=0xffffffff, disabled, unlocked
imr07: base=0x01000000, end=0x01905fff, size=0x00905fff rmask=0x00000001, wmask=0x00000001, enabled , locked
>-----Original Message-----
>From: Ong, Boon Leong
>Sent: Thursday, January 29, 2015 9:47 PM
>To: 'Bryan O'Donoghue'
>Cc: Thomas Gleixner; Ingo Molnar; H. Peter Anvin; x86@kernel.org;
>dvhart@infradead.org; linux-kernel@vger.kernel.org; Andy Shevchenko; Ingo
>Molnar
>Subject: RE: [PATCH 1/2] x86: Add Isolated Memory Regions for Quark X1000
>
>Bryan,
>
>Once you have the next revision ready, I would like to test it on my end across
>both Galileo Gen v1 & v2.
>
>Cheers,
>BL
>
>>-----Original Message-----
>>From: Bryan O'Donoghue [mailto:pure.logic@nexus-software.ie]
>>Sent: Thursday, January 29, 2015 6:12 PM
>>To: Andy Shevchenko; Ingo Molnar
>>Cc: Thomas Gleixner; Ingo Molnar; H. Peter Anvin; x86@kernel.org;
>>dvhart@infradead.org; Ong, Boon Leong; linux-kernel@vger.kernel.org
>>Subject: Re: [PATCH 1/2] x86: Add Isolated Memory Regions for Quark
>>X1000
>>
>>On 29/01/15 10:08, Andy Shevchenko wrote:
>>> On Thu, Jan 29, 2015 at 9:44 AM, Ingo Molnar <mingo@kernel.org> wrote:
>>>> * Bryan O'Donoghue <pure.logic@nexus-software.ie> wrote:
>>>
>>> []
>>>
>>>> In any case, I don't see any major problems with this code, so if
>>>> it's fixed it could go into v3.20.
>>>
>>> Brian, it would be really nice to have it in 3.20 since we have
>>> several drivers already in upstream or be ready for 3.20.
>>> It would be then first upstream kernel with minimal Quark support.
>>
>>NP lads - I'll get a patch out today
next prev parent reply other threads:[~2015-01-29 15:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 18:36 [PATCH v6 0/2] x86: Add IMR support to Quark/Galileo Bryan O'Donoghue
2015-01-28 18:36 ` [PATCH 1/2] x86: Add Isolated Memory Regions for Quark X1000 Bryan O'Donoghue
2015-01-29 5:38 ` Darren Hart
2015-01-29 7:44 ` Ingo Molnar
2015-01-29 10:08 ` Andy Shevchenko
2015-01-29 10:12 ` Bryan O'Donoghue
2015-01-29 13:47 ` Ong, Boon Leong
2015-01-29 15:22 ` Bryan O'Donoghue
2015-01-29 15:32 ` Ong, Boon Leong
2015-01-29 15:40 ` Bryan O'Donoghue
2015-01-29 16:12 ` Bryan O'Donoghue
2015-01-29 16:26 ` Ong, Boon Leong
2015-01-29 15:15 ` Ong, Boon Leong [this message]
2015-01-29 13:27 ` Bryan O'Donoghue
2015-01-29 9:59 ` Ong, Boon Leong
2015-01-28 18:36 ` [PATCH 2/2] x86, quark: Add Intel Quark platform support Bryan O'Donoghue
-- strict thread matches above, loose matches on Subject: below --
2014-12-29 17:23 [PATCH 0/2] x86: Add IMR support to Quark/Galileo Bryan O'Donoghue
2014-12-29 17:23 ` [PATCH 1/2] x86: Add Isolated Memory Regions for Quark X1000 Bryan O'Donoghue
2014-12-31 15:05 ` Andy Shevchenko
2015-01-01 20:11 ` Bryan O'Donoghue
2015-01-06 7:36 ` Darren Hart
2015-01-06 13:43 ` Bryan O'Donoghue
2015-01-06 16:54 ` Darren Hart
2015-01-07 23:45 ` Ong, Boon Leong
2015-01-08 12:10 ` Bryan O'Donoghue
2015-01-08 14:52 ` Ong, Boon Leong
2015-01-08 0:04 ` Ong, Boon Leong
2015-01-08 13:08 ` Bryan O'Donoghue
2015-01-08 14:45 ` Ong, Boon Leong
2015-01-08 15:11 ` Bryan O'Donoghue
2015-01-09 3:44 ` Darren Hart
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=AF233D1473C1364ABD51D28909A1B1B732715A94@PGSMSX105.gar.corp.intel.com \
--to=boon.leong.ong@intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=dvhart@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=pure.logic@nexus-software.ie \
--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 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).