From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Xen-devel <xen-devel@lists.xensource.com>,
the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [GIT PULL] x86: paravirt_ops updates
Date: Mon, 11 May 2009 17:25:29 -0700 [thread overview]
Message-ID: <4A08C1F9.1020308@goop.org> (raw)
In-Reply-To: <1241728373-3537-1-git-send-email-jeremy@goop.org>
Jeremy Fitzhardinge wrote:
> Hi Ingo,
>
> This series has a some changes to x86 paravirt_ops:
>
Ping? Did you overlook these changes, or have you just not had a chance
to look at them?
Thanks,
J
> x86/paravirt: split paravirt definitions into paravirt_types.h
>
> Move all the type-like definitions into asm/paravirt_types.h
>
> x86: split out core __math_state_restore
>
> Split out the core of math_state_restore() into __math_state_restore(),
> which just does what's needed for a context switch (ie, assumes
> TS is already clear, and that the fpu context exists).
>
> x86-32: make sure clts is batched during context switch
> x86-64: move unlazy_fpu() into lazy cpu state part of context switch
> x86-64: move clts into batch cpu state updates when preloading fpu
>
> Make sure the TS state updates during context switch are performed in
> the lazy CPU update region so that they can be batched when running
> paravirtualized.
>
> The following changes since commit 9ce5424d75e56891905b77d1589924765e62059a:
> Ingo Molnar (1):
> Merge branch 'x86/urgent'
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git x86/paravirt
>
> Jeremy Fitzhardinge (5):
> x86/paravirt: split paravirt definitions into paravirt_types.h
> x86: split out core __math_state_restore
> x86-32: make sure clts is batched during context switch
> x86-64: move unlazy_fpu() into lazy cpu state part of context switch
> x86-64: move clts into batch cpu state updates when preloading fpu
>
> arch/x86/include/asm/i387.h | 1 +
> arch/x86/include/asm/paravirt.h | 711 +--------------------------------
> arch/x86/include/asm/paravirt_types.h | 720 +++++++++++++++++++++++++++++++++
> arch/x86/kernel/process_32.c | 27 +-
> arch/x86/kernel/process_64.c | 34 +-
> arch/x86/kernel/traps.c | 33 +-
> 6 files changed, 783 insertions(+), 743 deletions(-)
> create mode 100644 arch/x86/include/asm/paravirt_types.h
>
> Thanks,
> J
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
prev parent reply other threads:[~2009-05-12 0:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 20:32 [GIT PULL] x86: paravirt_ops updates Jeremy Fitzhardinge
2009-05-07 20:32 ` [PATCH 1/5] x86/paravirt: split paravirt definitions into paravirt_types.h Jeremy Fitzhardinge
2009-05-07 20:32 ` [PATCH 2/5] x86: split out core __math_state_restore Jeremy Fitzhardinge
2009-05-07 20:32 ` [PATCH 3/5] x86-32: make sure clts is batched during context switch Jeremy Fitzhardinge
2009-05-07 20:32 ` [PATCH 4/5] x86-64: move unlazy_fpu() into lazy cpu state part of " Jeremy Fitzhardinge
2009-05-07 20:32 ` [PATCH 5/5] x86-64: move clts into batch cpu state updates when preloading fpu Jeremy Fitzhardinge
2009-05-12 0:25 ` Jeremy Fitzhardinge [this message]
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=4A08C1F9.1020308@goop.org \
--to=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.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