From: Ingo Molnar <mingo@elte.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/5] x86/paravirt: clean up paravirt.h and optimise FPU context switch
Date: Fri, 12 Jun 2009 14:37:53 +0200 [thread overview]
Message-ID: <20090612123753.GG31845@elte.hu> (raw)
In-Reply-To: <1244748040-27185-1-git-send-email-jeremy@goop.org>
* Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> Hi Ingo,
>
> This series:
> - splits asm/paravirt.h into paravirt.h and paravirt_types.h
> - splits out the context switch core of math_state_restore into __math_state_restore
> - rearranges 32 and 64 bit context switch to be the same and to properly
> batch FPU context switches when running paravirtualized
>
> There should be no performance side-effects of these changes. They amount
> to a small rearrangement of the existing code (and bringing the 64-bit
> code a bit closer to 32-bit, countering some genetic drift).
>
> I think these are probably safe to go into this merge window, but I
> don't think I've posted these before, so I understand if you're hesitant
> (I've had them applied locally for some time with no ill-effects).
> The paravirt cleanup is pure movement between headers, so I don't think
> there's much risk there at all.
>
> 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 | 33 +-
> arch/x86/kernel/traps.c | 33 +-
> 6 files changed, 782 insertions(+), 743 deletions(-)
hm, no Git pull coordinates - but you have this in a Git tree,
right?
Ingo
next prev parent reply other threads:[~2009-06-12 12:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 19:20 [PATCH 0/5] x86/paravirt: clean up paravirt.h and optimise FPU context switch Jeremy Fitzhardinge
2009-06-11 19:20 ` [PATCH 1/5] x86/paravirt: split paravirt definitions into paravirt_types.h Jeremy Fitzhardinge
2009-06-11 19:20 ` [PATCH 2/5] x86: split out core __math_state_restore Jeremy Fitzhardinge
2009-06-11 19:20 ` [PATCH 3/5] x86-32: make sure clts is batched during context switch Jeremy Fitzhardinge
2009-06-11 19:20 ` [PATCH 4/5] x86-64: move unlazy_fpu() into lazy cpu state part of " Jeremy Fitzhardinge
2009-06-11 19:20 ` [PATCH 5/5] x86-64: move clts into batch cpu state updates when preloading fpu Jeremy Fitzhardinge
2009-06-12 11:29 ` [PATCH 0/5] x86/paravirt: clean up paravirt.h and optimise FPU context switch Ingo Molnar
2009-06-12 16:55 ` Jeremy Fitzhardinge
2009-06-12 12:37 ` Ingo Molnar [this message]
2009-06-12 16:08 ` Jeremy Fitzhardinge
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=20090612123753.GG31845@elte.hu \
--to=mingo@elte.hu \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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