public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Zachary Amsden <zach@vmware.com>
Cc: Andi Kleen <ak@muc.de>, Andrew Morton <akpm@osdl.org>,
	Chris Wright <chrisw@sous-sol.org>,
	Chuck Ebbert <76306.1226@compuserve.com>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	Virtualization Mailing List <virtualization@lists.osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/5] Paravirt cpu batching.patch
Date: Tue, 12 Dec 2006 14:54:30 -0800	[thread overview]
Message-ID: <20061212225430.GC10475@sequoia.sous-sol.org> (raw)
In-Reply-To: <200612122234.kBCMYZD1023321@zach-dev.vmware.com>

* Zachary Amsden (zach@vmware.com) wrote:
> The VMI ROM has a mode where hypercalls can be queued and batched.  This turns
> out to be a significant win during context switch, but must be done at a
> specific point before side effects to CPU state are visible to subsequent
> instructions.  This is similar to the MMU batching hooks already provided.
> The same hooks could be used by the Xen backend to implement a context switch
> multicall.
> 
> To explain a bit more about lazy modes in the paravirt patches, basically, the
> idea is that only one of lazy CPU or MMU mode can be active at any given time.
> Lazy MMU mode is similar to this lazy CPU mode, and allows for batching of
> multiple PTE updates (say, inside a remap loop), but to avoid keeping some kind
> of state machine about when to flush cpu or mmu updates, we just allow one or
> the other to be active.  Although there is no real reason a more comprehensive
> scheme could not be implemented, there is also no demonstrated need for this
> extra complexity.
> 
> Signed-off-by: Zachary Amsden <zach@vmware.com>
> 
> --- a/arch/i386/kernel/process.c	Tue Dec 12 13:50:50 2006 -0800
> +++ b/arch/i386/kernel/process.c	Tue Dec 12 13:50:53 2006 -0800
> @@ -665,6 +665,37 @@ struct task_struct fastcall * __switch_t
>  	load_TLS(next, cpu);
>  
>  	/*
> +	 * Restore IOPL if needed.
> +	 */
> +	if (unlikely(prev->iopl != next->iopl))
> +		set_iopl_mask(next->iopl);

Small sidenote that this bit undoes a recent change from Chuck Ebbert, which
killed iopl_mask update via hypervisor.

thanks,
-chris

  reply	other threads:[~2006-12-12 22:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-12 22:34 [PATCH 2/5] Paravirt cpu batching.patch Zachary Amsden
2006-12-12 22:54 ` Chris Wright [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-12-12 23:49 Chuck Ebbert
2006-12-13  0:30 ` Jeremy Fitzhardinge
2006-12-13  0:38 ` Zachary Amsden

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=20061212225430.GC10475@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=76306.1226@compuserve.com \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.osdl.org \
    --cc=zach@vmware.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