virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Zachary Amsden <zach@vmware.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Chris Wright <chrisw@sous-sol.org>,
	Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: proposed interface change for setting the ldt
Date: Sun, 20 Aug 2006 22:01:49 -0700	[thread overview]
Message-ID: <44E93E3D.7060203@vmware.com> (raw)
In-Reply-To: <44E701B2.8050005@goop.org>

Jeremy Fitzhardinge wrote:
> Rusty Russell wrote:
>> It sounds fine to me, although I'd like to see the patch.  I don't have
>> anything against higher-level abstractions, if it helps any hypervisor,
>> as long as it doesn't warp the kernel code.  And if most hypervisors and
>> native break it down the same way, well, we can always create helpers.
>>   
>
> Doing it this way does save a lot of complexity in the Xen case, which 
> would otherwise have to:
>
>   1. unpack the descriptor
>   2. if it's an LDT, save it off in a per-cpu structure
>   3. when load_ldt_desc is called, look up the structure, extract the
>      base+size of the ldt, and make a hypercall to set the ldt
>
> vs
>
>   1. set the ldt

This way works for us as well, but my opinion is - Xen deliberately 
broke the x86 interface here, for no strong reason.  In an ideal world, 
we shouldn't have to change Linux to work around that, nor should other 
hypervisors have to live with the consequences of that decision.  So I 
believe the onus is on Xen to fix the problem in their layer, not the 
other way around.  But I have no problem adapting to this way of doing 
things for now, since this is not performance critical, and LDT is 
barely used in Linux anyway, even then, mostly by unsupported 
applications in a paravirtualized world.

Zach

      reply	other threads:[~2006-08-21  5:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-18 10:42 proposed interface change for setting the ldt Jeremy Fitzhardinge
2006-08-18 12:46 ` Jeremy Fitzhardinge
2006-08-18 13:03   ` Jeremy Fitzhardinge
2006-08-18 20:23 ` Zachary Amsden
2006-08-19  2:39   ` Jeremy Fitzhardinge
2006-08-19  3:12     ` Zachary Amsden
2006-08-19  3:18       ` Jeremy Fitzhardinge
2006-08-19  3:22       ` Chris Wright
2006-08-19  3:41         ` Zachary Amsden
2006-08-19  4:32           ` Rusty Russell
2006-08-19 12:18             ` Jeremy Fitzhardinge
2006-08-21  5:01               ` Zachary Amsden [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=44E93E3D.7060203@vmware.com \
    --to=zach@vmware.com \
    --cc=chrisw@sous-sol.org \
    --cc=jeremy@goop.org \
    --cc=virtualization@lists.osdl.org \
    /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;
as well as URLs for NNTP newsgroup(s).