From: Jeff Dike <jdike@addtoit.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Bodo Stroesser <bstroesser@fujitsu-siemens.com>
Subject: Re: [uml-devel] Removing call to function pointer in inner loop of copy_from_user()
Date: Mon, 16 May 2005 14:48:57 -0400 [thread overview]
Message-ID: <20050516184857.GA8171@ccure.user-mode-linux.org> (raw)
In-Reply-To: <200505161904.14197.blaisorblade@yahoo.it>
On Mon, May 16, 2005 at 07:04:13PM +0200, Blaisorblade wrote:
> I could move maybe move sigsetjmp to kernelspace code;
How are you going to get a definition of jmp_buf in there?
> however, another
> possibility would be to use the exception handler tables we've always
> supported without using them (only drawback is that the code *must* be
> inlined, and possibly the need for some assembler code, which however is
> probably avoidable).
Maybe. That's worth looking in to. I've used the setjmp scheme in preference
to that because it's portable, but maybe we should switch back in some places.
Jeff
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-05-16 18:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-15 18:44 [uml-devel] Removing call to function pointer in inner loop of copy_from_user() Blaisorblade
2005-05-16 15:00 ` Jeff Dike
2005-05-16 17:04 ` Blaisorblade
2005-05-16 18:48 ` Jeff Dike [this message]
2005-05-16 21:27 ` Blaisorblade
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=20050516184857.GA8171@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=blaisorblade@yahoo.it \
--cc=bstroesser@fujitsu-siemens.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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