From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Mikael Pettersson <mikpe@csd.uu.se>, Pavel Machek <pavel@suse.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] restore sysenter MSRs at resume
Date: 11 May 2003 22:04:37 +0100 [thread overview]
Message-ID: <1052687076.30359.2.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0305111158500.12955-100000@home.transmeta.com>
On Sul, 2003-05-11 at 20:01, Linus Torvalds wrote:
> However, the fact that the SYSENTER MSR needs to be restored makes me
> suspect that the other MSR/MTRR also will need restoring. I don't see
> where we'd be doing that, but it sounds to me like it should be done here
> too..
Some laptops certainly require the MTRR restore to happen. MSRs are
mostly less of a problem because the profiling stuff is broken on PIII
unless you disable/re-enable it across power save anyway.
Some laptops also lose all the AGP settings in the chipset.
next prev parent reply other threads:[~2003-05-11 21:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 16:41 mikpe
2003-05-11 19:01 ` Linus Torvalds
2003-05-11 19:08 ` Pavel Machek
2003-05-11 19:28 ` Nigel Cunningham
2003-05-12 11:30 ` Pavel Machek
2003-05-12 19:33 ` Nigel Cunningham
2003-05-12 19:54 ` Pavel Machek
2003-05-11 21:04 ` Alan Cox [this message]
2003-05-12 0:07 ` Linus Torvalds
2003-05-12 11:13 ` Alan Cox
2003-05-12 20:15 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2003-05-06 19:52 [BUG] 2.5.69 oops at sysenter_past_esp mikpe
2003-05-06 22:35 ` Dave Jones
2003-05-07 9:33 ` [PATCH] restore sysenter MSRs at resume mikpe
2003-05-07 14:41 ` Linus Torvalds
2003-05-07 17:23 ` mikpe
2003-05-07 17:39 ` Linus Torvalds
2003-05-08 21:47 ` 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=1052687076.30359.2.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
--cc=pavel@suse.cz \
--cc=torvalds@transmeta.com \
/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®