linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
To: Toshi Kani <toshi.kani@hp.com>
Cc: "Jan Beulich" <JBeulich@suse.com>,
	"Andy Lutomirski" <luto@amacapital.net>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Jej B" <James.Bottomley@hansenpartnership.com>,
	"X86 ML" <x86@kernel.org>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
	"Julia Lawall" <julia.lawall@lip6.fr>,
	xen-devel@lists.xenproject.org,
	"Dave Airlie" <airlied@redhat.com>,
	"Ville Syrjälä" <syrjala@sci.fi>,
	"Juergen Gross" <JGross@suse.com>, "Borislav Petkov" <bp@suse.de>,
	"Tomi Valkeinen" <tomi.valkeinen@ti.com>,
	linux-fbdev <linux-fbdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-media@vger.kernel.org,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [Xen-devel] RIP MTRR - status update for upcoming v4.2
Date: Thu, 6 Aug 2015 12:55:48 -0700	[thread overview]
Message-ID: <CAB=NE6WvaY4p7O3=0MMjWO44AytNYFr6xRsvVmVWDns9qdYZ8Q@mail.gmail.com> (raw)
In-Reply-To: <CAB=NE6W3=SFTqabeD6gq7JCqFZ7+SBZh7Xa=RteO_8-3P7fbdw@mail.gmail.com>

On Thu, Aug 6, 2015 at 12:53 PM, Luis R. Rodriguez
<mcgrof@do-not-panic.com> wrote:
> For those type of OSes...
> could it be possible to negotiate or hint to the platform through an
> attribute somehow that the OS has such capability to not use MTRR?

And if that's not possible how about a new platform setting that would
need to be set at the platform level to enable disabling this junk?
Then only folks who know what they are doing would enable it, and if
the customer set it, the issue would not be on the platform.

 Luis

  reply	other threads:[~2015-08-06 19:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-11 20:36 RIP MTRR - status update for upcoming v4.2 Luis R. Rodriguez
2015-06-11 23:23 ` Toshi Kani
2015-06-12  0:52   ` Luis R. Rodriguez
2015-06-12 16:42     ` Toshi Kani
2015-06-12  7:59   ` [Xen-devel] " Jan Beulich
2015-06-12 16:58     ` Toshi Kani
2015-08-06 19:53       ` Luis R. Rodriguez
2015-08-06 19:55         ` Luis R. Rodriguez [this message]
2015-08-06 22:58         ` Toshi Kani
2015-08-07 20:25           ` Luis R. Rodriguez
2015-08-07 21:56             ` Toshi Kani
2015-08-07 22:23               ` Luis R. Rodriguez
2015-08-07 23:08                 ` Toshi Kani
2015-08-07 23:19                   ` Toshi Kani
2015-08-07 23:26                   ` Luis R. Rodriguez
2015-08-07 23:48                     ` Toshi Kani
2015-06-12 23:15     ` Andy Lutomirski
2015-06-12 23:29       ` James Bottomley
2015-06-13  6:37       ` Ingo Molnar
2015-06-15  6:20       ` Jan Beulich

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='CAB=NE6WvaY4p7O3=0MMjWO44AytNYFr6xRsvVmVWDns9qdYZ8Q@mail.gmail.com' \
    --to=mcgrof@do-not-panic.com \
    --cc=JBeulich@suse.com \
    --cc=JGross@suse.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=airlied@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=bhelgaas@google.com \
    --cc=bp@suse.de \
    --cc=julia.lawall@lip6.fr \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=syrjala@sci.fi \
    --cc=tomi.valkeinen@ti.com \
    --cc=toshi.kani@hp.com \
    --cc=ville.syrjala@linux.intel.com \
    --cc=x86@kernel.org \
    --cc=xen-devel@lists.xenproject.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).