linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
Cc: user-mode-linux-devel@lists.sourceforge.net,
	Jeff Dike <jdike@addtoit.com>,
	linux-kernel@vger.kernel.org,
	Allan Graves <allan.graves@oracle.com>
Subject: Re: [uml-devel] [PATCH 8/10] UML - Maintain own LDT entries
Date: Mon, 7 Nov 2005 20:28:22 +0100	[thread overview]
Message-ID: <200511072028.23111.blaisorblade@yahoo.it> (raw)
In-Reply-To: <436F469B.3080607@fujitsu-siemens.com>

On Monday 07 November 2005 13:20, Bodo Stroesser wrote:
> Blaisorblade wrote:
> > On Monday 31 October 2005 05:39, Jeff Dike wrote:
> >>From: Bodo Stroesser <bstroesser@fujitsu-siemens.com>

> > Or at least so I think (I must still give a proper look afterwards, and
> > I'll post patches). Actually it seems that this is done on purpose, but I
> > don't agree too much on this. I will see.

>  From the beginning my new code for SKAS included the checks/buffering you
> later inserted for TT and SKAS. So this patch is a second version adapted
> to your changes. It shifts your improvements into TT path only (where I
> didn't do any changes in my old patch), while it uses my own stuff for
> SKAS. Thus the patch doesn't really revert your improvements, but restricts
> it to TT. As in SKAS0 UML now holds its own LDT data, there is no need for
> buffering in this case. So I think it makes sense to have separate code for
> SKAS.
Yep, ok - I'm undecided about the new code for SKAS3, but it may make sense 
(i.e. no opinion).

Instead, I have another question: is there a proper reason for using the 
processor format for storing the info and translating it back to (struct 
user_desc)? I am planning to avoid this double translation because I don't 
like it. Any opinion?
-- 
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade

	

	
		
___________________________________ 
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB 
http://mail.yahoo.it



-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
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-11-07 19:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-31  4:39 [uml-devel] [PATCH 8/10] UML - Maintain own LDT entries Jeff Dike
2005-11-01  7:53 ` Rob Landley
2005-11-02 19:51 ` Blaisorblade
2005-11-07 12:20   ` Bodo Stroesser
2005-11-07 19:28     ` Blaisorblade [this message]
2005-11-08 15:25       ` Bodo Stroesser
2005-11-08 16:02         ` 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=200511072028.23111.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=allan.graves@oracle.com \
    --cc=bstroesser@fujitsu-siemens.com \
    --cc=jdike@addtoit.com \
    --cc=linux-kernel@vger.kernel.org \
    --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