From: Ingo Molnar <mingo@elte.hu>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Brian Gerst <brgerst@gmail.com>,
Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 2/3] xen: make direct versions of irq_enable/disable/save/restore to common code
Date: Thu, 5 Feb 2009 16:00:28 +0100 [thread overview]
Message-ID: <20090205150028.GD23903@elte.hu> (raw)
In-Reply-To: <498A87B5.3020808@gmail.com>
* Tejun Heo <htejun@gmail.com> wrote:
> Hello,
>
> Jeremy Fitzhardinge wrote:
> > Now that x86-64 has directly accessible percpu variables, it can also
> > implement the direct versions of these operations, which operate on a
> > vcpu_info structure directly embedded in the percpu area.
> >
> > In fact, the 64-bit versions are more or less identical, and so can be
> > shared. The only two differences are:
> > 1. xen_restore_fl_direct takes its argument in eax on 32-bit, and rdi on
> > 64-bit.
> > Unfortunately it isn't possible to directly refer to the 2nd lsb of
> > rdi directly
> > (as you can with %ah), so the code isn't quite as dense.
> > 2. check_events needs to variants to save different registers.
> >
> > Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
> > ---
> > arch/x86/xen/Makefile | 3 arch/x86/xen/xen-asm.S | 140
> > +++++++++++++++++++++++++++++++++++++++++++++
> > arch/x86/xen/xen-asm.h | 12 +++
> > arch/x86/xen/xen-asm_32.S | 113 ++++--------------------------------
> > arch/x86/xen/xen-asm_64.S | 136
> > +------------------------------------------
> > 5 files changed, 171 insertions(+), 233 deletions(-)
> ...
> > ===================================================================
> > --- a/arch/x86/xen/xen-asm_32.S
> > +++ b/arch/x86/xen/xen-asm_32.S
> > @@ -11,101 +11,28 @@
> > generally too large to inline anyway.
> > */
> >
> > -#include <linux/linkage.h>
> > -
> > -#include <asm/asm-offsets.h>
> > +//#include <asm/asm-offsets.h>
>
> Applied without the above addition of //
btw., that's still worth fixing, plus the comments styles could be
standardized. And this should grow an extra space after the comma:
lea 4(%edi),%esp /* point esp to new frame */
(there's 5-6 similar instructions in that file with this problem - the rest
is fine.)
Ingo
next prev parent reply other threads:[~2009-02-05 15:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-31 1:42 [PATCH 2/3] xen: make direct versions of irq_enable/disable/save/restore to common code Jeremy Fitzhardinge
2009-02-05 6:31 ` Tejun Heo
2009-02-05 15:00 ` Ingo Molnar [this message]
2009-02-05 16:04 ` [PATCH] x86: style fascism for xen assemblies Tejun Heo
2009-02-05 16:57 ` Ingo Molnar
2009-02-05 17:31 ` Jeremy Fitzhardinge
2009-02-05 17:34 ` Ingo Molnar
2009-02-05 17:42 ` Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2009-02-02 21:55 [PATCH 2/3] xen: make direct versions of irq_enable/disable/save/restore to common code 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=20090205150028.GD23903@elte.hu \
--to=mingo@elte.hu \
--cc=brgerst@gmail.com \
--cc=htejun@gmail.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.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