All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andi Kleen <ak@muc.de>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
	Chuck Ebbert <76306.1226@compuserve.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 5/6] Begin abstraction of sensitive instructions: asm files
Date: Mon, 24 Jul 2006 13:54:37 -0700	[thread overview]
Message-ID: <44C5338D.4060805@goop.org> (raw)
In-Reply-To: <20060724173629.GB50320@muc.de>

Andi Kleen wrote:
> I would rather pass the register to the macro? If you start to
> clobber registers you would need to pass in the tmp registers
> too I guess.
The intent is that these code sequences can be patched in place, so they 
need to have a specific abi at the machine-code level.  Some of the 
operations whose Xen implementation clobbers a register have that in 
their definition, on the assumption that 1 temp is enough, and that 
another interface which needs more can organize save/restoring registers 
for itself.

    J

  reply	other threads:[~2006-07-24 20:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-22  3:23 [PATCH 5/6] Begin abstraction of sensitive instructions: asm files Chuck Ebbert
2006-07-22 13:34 ` Rusty Russell
2006-07-24 17:36   ` Andi Kleen
2006-07-24 20:54     ` Jeremy Fitzhardinge [this message]
2006-07-25 23:52   ` Peter Chubb
2006-07-26  3:25     ` Rusty Russell
  -- strict thread matches above, loose matches on Subject: below --
2006-07-22  0:14 Rusty Russell
2006-07-30 10:52 ` Pavel Machek
2006-07-30 10:56   ` Pavel Machek

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=44C5338D.4060805@goop.org \
    --to=jeremy@goop.org \
    --cc=76306.1226@compuserve.com \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.