From: Glauber de Oliveira Costa <gcosta@redhat.com>
To: akpm@linux-foundation.org, andi@firstfloor.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] Remove duplicated code for reading control registers
Date: Tue, 13 Mar 2007 09:30:11 -0300 [thread overview]
Message-ID: <20070313123011.GG10126@redhat.com> (raw)
Tiny cleanup:
In x86_64, the same functions for reading cr3 and writing cr{3,4} are
defined in tlbflush.h and system.h, whith just a name change.
The only difference is the clobbering of memory, which seems a safe, and
even needed change for the write_cr4. This patch removes the duplicate.
write_cr3() is moved to system.h for consistency.
Signed-off-by: Glauber de Oliveira Costa <gcosta@redhat.com>
--
Glauber de Oliveira Costa
Red Hat Inc.
"Free as in Freedom"
next reply other threads:[~2007-03-13 12:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 12:30 Glauber de Oliveira Costa [this message]
[not found] ` <Pine.LNX.4.58.0703130532510.13997@shark.he.net>
2007-03-13 12:52 ` [PATCH] Remove duplicated code for reading control registers Glauber de Oliveira Costa
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=20070313123011.GG10126@redhat.com \
--to=gcosta@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).