linux-um archives
 help / color / mirror / Atom feed
From: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
	Jeff Dike <jdike@addtoit.com>
Subject: Re: [uml-devel] Recent patches of note
Date: Thu, 16 Jun 2005 20:40:07 +0200	[thread overview]
Message-ID: <42B1C787.6010402@fujitsu-siemens.com> (raw)
In-Reply-To: <200506162041.27013.blaisorblade@yahoo.it>

Blaisorblade wrote:
> On Thursday 16 June 2005 20:31, Bodo Stroesser wrote:
> 
>>Blaisorblade wrote:
>>
>>>arch_switch already exists (wasn't used for SKAS). About improving it and
>>>making it more "general-purpose" (I've written this for the TLS code
>>>needs), could you have a look to the attached patches? do_fork-* is
>>>another thing (a cleanup discussed some time ago with Jeff) but may be
>>>needed to apply the second.
>>
>>Wouldn't it be better to have separate arch_switch_tt and arch_switch_skas?
>>I think, arch_switch has to do different things for tt and skas (and maybe
>>even for skas0 and skas3)
> 
> Let's not go creating too many layers. switch_to_* calls arch_switch, then it 
> can use CHOOSE_MODE if it needs (see the TLS patch I'm working on, it's in 
> the -devel tarball here:
Then swtich_to_tt should call arch_switch_tt and switch_to_skas should call
arch_switch_skas. This avoids a CHOOSE_MODE and a function call.
And also it makes tt a bit more removable, if Jeff decides to.

	Bodo
> 
> http://www.user-mode-linux.org/~blaisorblade/patches/devel-guest/
> 
> (pick the latest)
> ).


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&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

  reply	other threads:[~2005-06-16 18:40 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-16 16:07 [uml-devel] Recent patches of note Jeff Dike
2005-06-16 17:36 ` Bodo Stroesser
2005-06-16 17:47   ` Jeff Dike
2005-06-16 17:55     ` Bodo Stroesser
2005-06-16 18:02       ` Bodo Stroesser
2005-06-16 18:09       ` Blaisorblade
2005-06-16 18:31         ` Bodo Stroesser
2005-06-16 18:41           ` Blaisorblade
2005-06-16 18:40             ` Bodo Stroesser [this message]
2005-06-16 18:51               ` Blaisorblade
2005-06-16 22:23                 ` Jeff Dike
2005-06-17  9:09                   ` Bodo Stroesser
2005-06-17 18:36                   ` Blaisorblade
2005-06-17  0:35         ` Jeff Dike
2005-06-17 18:40           ` Blaisorblade
     [not found] <s2b18c1b.063@ORANGE.OUS.EDU>
2005-06-16 22:13 ` Jeff Dike
  -- strict thread matches above, loose matches on Subject: below --
2005-06-16 22:59 Anthony Brock
     [not found] <s2b1a1ed.010@ORANGE.OUS.EDU>
2005-06-20 14:47 ` Jeff Dike
     [not found] <s2b19c99.097@ORANGE.OUS.EDU>
2005-06-20 14:53 ` Jeff Dike
2005-06-20 17:59   ` William Stearns
2005-06-20 21:31     ` Blaisorblade
     [not found] <s2b6982e.048@ORANGE.OUS.EDU>
2005-06-20 20:11 ` Jeff Dike

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=42B1C787.6010402@fujitsu-siemens.com \
    --to=bstroesser@fujitsu-siemens.com \
    --cc=blaisorblade@yahoo.it \
    --cc=jdike@addtoit.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