Re: [Xen-devel] RIP MTRR - status update for upcoming v4.2

From	"Jan Beulich" <JBeulich@suse.com>
Newsgroups	linux.kernel
Subject	Re: [Xen-devel] RIP MTRR - status update for upcoming v4.2
Date	2015-06-15 08:30 +0200
Message-ID	<pBw49-3Dt-7@gated-at.bofh.it> (permalink)
References	<pAhqy-8v7-27@gated-at.bofh.it> <pAk54-45h-5@gated-at.bofh.it> <pAsch-7Wu-1@gated-at.bofh.it> <pAGoV-3oF-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

>>> On 13.06.15 at 01:15, <luto@amacapital.net> wrote:
> On Jun 12, 2015 12:59 AM, "Jan Beulich" <JBeulich@suse.com> wrote:
>>
>> >>> On 12.06.15 at 01:23, <toshi.kani@hp.com> wrote:
>> > There are two usages on MTRRs:
>> >  1) MTRR entries set by firmware
>> >  2) MTRR entries set by OS drivers
>> >
>> > We can obsolete 2), but we have no control over 1).  As UEFI firmwares
>> > also set this up, this usage will continue to stay.  So, we should not
>> > get rid of the MTRR code that looks up the MTRR entries, while we have
>> > no need to modify them.
>> >
>> > Such MTRR entries provide safe guard to /dev/mem, which allows
>> > privileged user to access a range that may require UC mapping while
>> > the /dev/mem driver blindly maps it with WB.  MTRRs converts WB to UC in
>> > such a case.
>>
>> But it wouldn't be impossible to simply read the MTRRs upon boot,
>> store the information, disable MTRRs, and correctly use PAT to
>> achieve the same effect (i.e. the "blindly maps" part of course
>> would need fixing).
> 
> This may crash and burn badly when we call a UEFI function or an SMI
> happens.  I think we should just leave the MTRRs alone.

I buy the SMI part, but UEFI runtime calls are being done on
page tables we construct and control, so attributes could be kept
correct without relying on MTRRs.

Jan

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

RIP MTRR - status update for upcoming v4.2 "Luis R. Rodriguez" <mcgrof@do-not-panic.com> - 2015-06-11 22:40 +0200
  Re: RIP MTRR - status update for upcoming v4.2 "Luis R. Rodriguez" <mcgrof@suse.com> - 2015-06-12 03:00 +0200
  Re: [Xen-devel] RIP MTRR - status update for upcoming v4.2 James Bottomley <James.Bottomley@HansenPartnership.com> - 2015-06-13 01:30 +0200
  Re: [Xen-devel] RIP MTRR - status update for upcoming v4.2 "Jan Beulich" <JBeulich@suse.com> - 2015-06-15 08:30 +0200

csiph-web