From: "Bryan O'Donoghue" <pure.logic@nexus-software.ie>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org, corbet@lwn.net, tglx@linutronix.de,
mingo@redhat.com, hpa@zytor.com, x86@kernel.org,
andriy.shevchenko@linux.intel.com, boon.leong.ong@intel.com,
fengguang.wu@intel.com, linux-doc@vger.kernel.org
Subject: Re: [PATCH] x86/intel/quark: Parameterize the kernel's IMR lock logic
Date: Fri, 19 Feb 2016 01:07:58 +0000 [thread overview]
Message-ID: <1455844078.31619.297.camel@nexus-software.ie> (raw)
In-Reply-To: <20160218185322.GC16753@gmail.com>
On Thu, 2016-02-18 at 19:53 +0100, Ingo Molnar wrote:
> * Bryan O'Donoghue <pure.logic@nexus-software.ie> wrote:
>
> > On Thu, 2016-02-18 at 08:58 +0100, Ingo Molnar wrote:
> > > So why not simply do the patch below? Very few people use boot
> > > parameters, and the
> > > complexity does not seem to be worth it.
> > >
> > > Furthermore I think an IMR range in itself is safe enough - it's
> > > not
> > > like such
> > > register state is going to be randomly corrupted, even with the
> > > 'lock' bit unset.
> >
> >
> > Hi Ingo.
> >
> > I agree - to flip the lock bit you need to be in ring-0 anyway.
> >
> > > So it's a perfectly fine protective measure against accidental
> > > memory
> > > corruption
> > > from the DMA space. It should not try to be more than that.
> > >
> > > And once we do this, I suggest we get rid of the 'lock' parameter
> > > altogether -
> > > that will further simplify the code.
> > >
> > > Thanks,
> > >
> > > Ingo
> >
> > That was the V1 of this patch
> >
> > https://groups.google.com/forum/#!topic/linux.kernel/6ZuVOF3TJow
>
> heh ;-)
:)
> > Andriy asked for the boot parameter to control the state of the IMR
> > lock bit, I'm just as happy to go back to that version TBH
>
> I really think it's over-engineered - especially considering that
> with the kernel
> lock-down removed there's no other IMR area that is really locked
> down - so we
> could get rid of the whole 'locked' logic that would simplify the
> code throughout.
I'm in favour of that too. Charitably I think locking a register like
this makes sense only when you talk about it in a meeting room
somewhere; as soon as you go to try to use it in a real situation you
find its far more trouble than its really worth.
So, I'm going to trim that out of this code unless I hear some pushback
from elsewhere in the 1/2 day or so.
>
> Yeah, it's a nice looking hardware feature - but I don't think it's
> particularly
> useful in terms of extra protection.
>
> Thanks,
>
> Ingo
prev parent reply other threads:[~2016-02-19 1:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 3:29 [PATCH] x86/intel/quark: Parameterize the kernel's IMR lock logic Bryan O'Donoghue
2016-02-18 7:58 ` Ingo Molnar
2016-02-18 10:31 ` Bryan O'Donoghue
2016-02-18 18:53 ` Ingo Molnar
2016-02-19 1:07 ` Bryan O'Donoghue [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=1455844078.31619.297.camel@nexus-software.ie \
--to=pure.logic@nexus-software.ie \
--cc=andriy.shevchenko@linux.intel.com \
--cc=boon.leong.ong@intel.com \
--cc=corbet@lwn.net \
--cc=fengguang.wu@intel.com \
--cc=hpa@zytor.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox