mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Patrick Mochel <mochel@osdl.org>
Cc: Pavel Machek <pavel@ucw.cz>,
	Richard Gooch <rgooch@ras.ucalgary.ca>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Nigel Cunningham <ncunningham@clear.net.nz>
Subject: Re: PATCH: MTRR save and restore.
Date: 15 Apr 2003 21:28:41 +0100	[thread overview]
Message-ID: <1050438520.28591.4.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0304151313260.912-100000@cherise>

On Maw, 2003-04-15 at 21:18, Patrick Mochel wrote:
> MTRRs are one interface to an x86 CPU. CPUs are already represented in the
> device tree. The proper thing to do would be to have the CPU suspend/ 
> resume methods save and restore the MTRRs. It still requires an #ifdef in 
> the CPU code, but with a little work, could be massaged down a ways. 

Also it has to be done kernel side for SMP because having mismatched
MTRRs between processors is unsafe, yet lots of BIOSen get it wrong.



  reply	other threads:[~2003-04-15 21:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1049530866.2241.23.camel@laptop-linux.cunninghams>
     [not found] ` <200304062220.h36MKC35017233@vindaloo.ras.ucalgary.ca>
     [not found]   ` <1049680104.12790.46.camel@laptop-linux.cunninghams>
     [not found]     ` <20030407130507.GA16919@atrey.karlin.mff.cuni.cz>
     [not found]       ` <200304071646.h37GkBd6005985@vindaloo.ras.ucalgary.ca>
2003-04-07 20:13         ` Pavel Machek
2003-04-15 20:18           ` Patrick Mochel
2003-04-15 20:28             ` Alan Cox [this message]
2003-04-16 11:52             ` Pavel Machek

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=1050438520.28591.4.camel@dhcp22.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.org \
    --cc=ncunningham@clear.net.nz \
    --cc=pavel@ucw.cz \
    --cc=rgooch@ras.ucalgary.ca \
    /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

all inboxes | Powered by JetHome®