From: Blaisorblade <blaisorblade@yahoo.it>
To: Ian Rogers <ian.rogers@manchester.ac.uk>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Jeff Dike <jdike@addtoit.com>
Subject: Re: [uml-devel] Using SKAS, any examples?
Date: Mon, 9 May 2005 17:08:30 +0200 [thread overview]
Message-ID: <200505091708.30730.blaisorblade@yahoo.it> (raw)
In-Reply-To: <427E55E6.2000503@manchester.ac.uk>
On Sunday 08 May 2005 20:09, Ian Rogers wrote:
> Blaisorblade wrote:
> Thanks. I will implment an emulator through this mechanism. My current
> mechanism performs:
>
> loadByte(addr) {
> pte = addr >> 12;
> offset = addr & 0xFFF;
> result = memory[ptr][offset]
> }
Ok, memory is a square array.
> you can imagine the store... mechanisms. Obviously the cost of the
> ptrace calls is going to be a slow down compared to this.
Well, if it's done only at setup, ok. However, can you please explain to me
why it isn't possible to do it without SKAS?
> I hope to look into creating a patch to allow multiple segments in a
> linux process. So an extension to skas on i386 and I can get my %fs wish
> :-)
Well, it should be already doable in SKAS, with PTRACE_LDT (which relates to
modify_ldt() the same way that writing DO_MMAP relates to mmap()). Then,
after *setting* an appropriate descriptor in %fs (with PTRACE_POKEUSR if you
need), you're done.
> btw: a similar thing should be possible on PowerPC given that
> segmentation can be disabled for either or both the instruction and data
> cache. It would be neat to wrap this up in a module for the performance
> improvement of emulators.
> Glad it was useful and thanks for your help - it's taught me what to do
> for my emulator code. I hope I can post some more things back in the
> future. Would the multi-segment stuff be useful for more people? Is
> there an obvious reason to avoid multi-segments?
Well, I've proposed some time ago to use segmentation for UML, but the
proposal was dropped "because an access through segmentation is a little
slower".
Quite frankly, I'm quite unconvinced (because any access passes through
segmentation, even if normally segments have a 0 base and a disabled limit);
beyond, Xen uses segmentation in the same way that I was proposing for UML,
IIRC.
--
Paolo Giarrusso, aka Blaisorblade
Skype user "PaoloGiarrusso"
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
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-09 15:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-04 9:28 [uml-devel] Using SKAS, any examples? Ian Rogers
2005-05-04 13:27 ` Jeff Dike
2005-05-04 14:49 ` Ian Rogers
2005-05-04 19:03 ` Blaisorblade
2005-05-05 17:03 ` Ian Rogers
2005-05-07 3:11 ` Jeff Dike
2005-05-07 20:31 ` Ian Rogers
2005-05-08 17:02 ` Blaisorblade
2005-05-08 18:09 ` Ian Rogers
2005-05-09 15:08 ` Blaisorblade [this message]
2005-05-09 18:09 ` Ian Rogers
2005-05-07 15:28 ` 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=200505091708.30730.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=ian.rogers@manchester.ac.uk \
--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