From: Jacob Gorm Hansen <jacobg@diku.dk>
To: Lars Roland <lroland@gmail.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Question about hyper-threading of domains
Date: Fri, 29 Apr 2005 13:10:36 -0700 [thread overview]
Message-ID: <427294BC.6000402@diku.dk> (raw)
In-Reply-To: <4ad99e05050429125764ad281b@mail.gmail.com>
Lars Roland wrote:
> Seans fair enough - Out of curiosity have you published these
> measurements anywere ?
No nothing yet, apart from the iperf numbers posted previously to this list.
>>I previously stated that using small address spaces means giving up
>>driver isolation, but I think that with the right use of segments that
>>should not be necessary, so there is no trade-off with regards to isolation.
>
>
> Could you explain a little further how excalty you plan to avoid this
> - I have been digging into this myslef and It is not obvious to me how
> this can be achived,
I have not implemented this, and perhaps I am not understanding the x86
docs correctly, but it seems I can set up and expands-down segment to
confine dom0 to its allowed range of addresses (0xf0000000 -
0xfc000000). If that does not work, I can move dom0 to the range 0x0 -
0x0c000000, and use the segment base to move it to 0xf0000000. The
latter approach will require that I fix up copy_from_user and friends
inside Xen to take this into account, but that seems doable.
> Yes please - I have the time (and hardware) to check this.
I will try to roll something up later today or tomorrow, before flying
to Boston for NSDI.
Jacob
next prev parent reply other threads:[~2005-04-29 20:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-29 19:42 Question about hyper-threading of domains Jacob Gorm Hansen
2005-04-29 19:57 ` Lars Roland
2005-04-29 20:10 ` Jacob Gorm Hansen [this message]
2005-04-29 22:58 ` Mark Williamson
2005-04-29 19:59 ` Keir Fraser
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=427294BC.6000402@diku.dk \
--to=jacobg@diku.dk \
--cc=lroland@gmail.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.