From: Rusty Russell <rusty@rustcorp.com.au>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
virtualization@lists.linux-foundation.org
Subject: Re: [kvm-devel] [PATCH 3/3] Eliminate read_cr3 on TLB flush
Date: Thu, 31 May 2007 11:12:13 +1000 [thread overview]
Message-ID: <1180573933.30202.145.camel@localhost.localdomain> (raw)
In-Reply-To: <465DCED8.4080506@us.ibm.com>
On Wed, 2007-05-30 at 14:22 -0500, Anthony Liguori wrote:
> I was actually thinking about adding a hypercall to set/clear a bit in a
> control register. The thought here is that it would be useful not just
> for the global bit but also for CR0.TS although we would need another
> paravirt_op hook for stts.
We don't really need one, because Linux (i386) only cares about the TS
bit of cr0. From lguest (you'd want this per-cpu of course):
static unsigned long current_cr0, current_cr3;
static void lguest_write_cr0(unsigned long val)
{
lazy_hcall(LHCALL_TS, val & 8, 0, 0);
current_cr0 = val;
}
static unsigned long lguest_read_cr0(void)
{
return current_cr0;
}
Cheers,
Rusty.
next prev parent reply other threads:[~2007-05-31 1:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <97D612E30E1F88419025B06CB4CF1BE10259AD95@scsmsx412.amr.corp.intel.com>
2007-05-30 19:22 ` [kvm-devel] [PATCH 3/3] Eliminate read_cr3 on TLB flush Anthony Liguori
2007-05-30 20:40 ` Nakajima, Jun
2007-05-30 21:49 ` Zachary Amsden
2007-05-31 1:12 ` Rusty Russell [this message]
2007-05-31 7:50 ` Avi Kivity
[not found] ` <465E7E4F.8050208@qumranet.com>
2007-05-31 17:30 ` Anthony Liguori
[not found] <97D612E30E1F88419025B06CB4CF1BE10259AE6D@scsmsx412.amr.corp.intel.com>
2007-05-30 22:03 ` Anthony Liguori
[not found] <465DBB49.5030503@vmware.com>
2007-05-30 19:12 ` Nakajima, Jun
[not found] <97D612E30E1F88419025B06CB4CF1BE10259AB81@scsmsx412.amr.corp.intel.com>
2007-05-30 17:58 ` Zachary Amsden
2007-05-30 15:38 Jeremy Fitzhardinge
2007-05-30 17:11 ` [kvm-devel] " Nakajima, Jun
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=1180573933.30202.145.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=aliguori@us.ibm.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=virtualization@lists.linux-foundation.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).