From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Bodo Stroesser <bstroesser@fujitsu-siemens.com>,
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: Tue, 8 Nov 2005 17:02:02 +0100 [thread overview]
Message-ID: <200511081702.02891.blaisorblade@yahoo.it> (raw)
In-Reply-To: <4370C36E.2040205@fujitsu-siemens.com>
On Tuesday 08 November 2005 16:25, Bodo Stroesser wrote:
> Blaisorblade wrote:
> > 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>
> In my opinion there is no reason to change the current implementation for
> SAKS3/0. Note: if someone reads LDT via [sys_]modify_ldt(), he will receive
> the requested data in "processor format", that is LDT-descriptors. He will
> receive a list of descriptors starting at the first descriptor of the LDT,
> thus no entry number is needed in the enties.
Ehrr... ACK! You're right, I really _did_ miss the read_ldt case.
> The only case that uses user_desc is when writing one desriptor via
> modify_ldt(). modify_ldt(WRITE) exactly writes one LDT-descriptor, so
> user_desc must contain the number of the entry to write. Thus user_desc is
> bigger than LDT descriptor. It also uses an other data layout resulting in
> double the size of LDT-descriptor. So I think it doesn't make sense to
> store user_desc. We save memory storing the resulting LDT-descriptors,
> which then are copied transparently on modify_ldt(READ). Conversion between
> user_desc and LDT-entry is done on modify_ldt(WRITE) in SKAS0 only. No
> other conversions are done in UML.
Ok, I now totally agree with your point. I had missed the read_ldt case. It's
perfectly fine to keep it as-is.
--
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
prev parent reply other threads:[~2005-11-08 16:08 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
2005-11-08 15:25 ` Bodo Stroesser
2005-11-08 16:02 ` Blaisorblade [this message]
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=200511081702.02891.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